[Rt-commit] rt branch, 4.4/automating-rt-multiple-actions, created. rt-4.4.2-1-g692d7eb

[Craig Kaiser]

The branch, 4.4/automating-rt-multiple-actions has been created
        at  692d7eb7d2d0bef17d11ada08c3b25655651141e (commit)

- Log -----------------------------------------------------------------
commit 692d7eb7d2d0bef17d11ada08c3b25655651141e
Author: Craig Kaiser <craig at bestpractical.com>
Date:   Wed Dec 13 08:36:10 2017 -0500

    Add doc for rt-crontool, multiple --actions
    
    Add section in the docs/automating_rt doc giving
    an example of passing multiple --action parameters
    for one condition. Current docs do not make it clear
    that rt-crontool supports multiple action paramters
    per condition.

diff --git a/docs/automating_rt.pod b/docs/automating_rt.pod
index 11960c3..4100a86 100644
--- a/docs/automating_rt.pod
+++ b/docs/automating_rt.pod
@@ -78,6 +78,22 @@ 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' \
+
+The rt-crontool can take more than one --action parameter to perform multiple actions based on one condition.
+In the example above two actions are completed if the condition of any ticket having a status of "stalled" is 
+met. First the tickets status is changed to "resolved" and then the second action is performed, where the 
+requestors on the ticket are notified.
+
 =head1 Auto-resolve Aged Tickets
 
 You can auto-set status based on any criteria you can define in

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