[Rt-commit] rt branch, automating-rt-docs, created. rt-4.2.14-8-gc229a92

[Craig Kaiser]

The branch, automating-rt-docs has been created
        at  c229a9233284345294abb4a96b39c843365bf3be (commit)

- Log -----------------------------------------------------------------
commit c229a9233284345294abb4a96b39c843365bf3be
Author: craig <craig at bestpractical.com>
Date:   Mon Oct 16 09:58:56 2017 -0400

    Adding documentatiion for automating-rt, using rt-crontool with multiple --action parameters.

diff --git a/docs/automating_rt.pod b/docs/automating_rt.pod
index 11960c3..b1a7e2d 100644
--- a/docs/automating_rt.pod
+++ b/docs/automating_rt.pod
@@ -78,6 +78,20 @@ The C<--action> argument is set to L<RT::Action> which is the base class
 for RT actions. Since this class doesn't perform any action itself, this
 command will just output the results of the TicketSQL search.
 
+=head2 Multiple --Action parameters
+
+    /opt/rt4/bin/rt-crontool \
+      --search RT::Search::FromSQL \
+      --search-arg "Status = 'stalled'" \
+      --action RT::Action::SetStatus  --action-arg resolved \
+      --action RT::Action::Notify \
+          --action-arg 'Requestor' \
+          --transaction last \
+          --template 'Stalled ticket resolved' \
+
+rt-crontool can also take more than one --action parameter to perform multiple steps are a time. In the example above
+two actions are completed first it checks for any tickets with a "stalled" status and then marks them as resolved.
+As well as notifies the Requestors on the ticket of the change.p
 =head1 Auto-resolve Aged Tickets
 
 You can auto-set status based on any criteria you can define in

-----------------------------------------------------------------------