Examples of Automation Rules

Below are examples of automation rules, used for common scenarios. Review them to learn how to create your own automation rules. Clicking on a link opens a detailed description of each example.

• Example 1 – Adding a comment to the workflow request
• Example 2 – Adding information from the UI extension to the workflow request
• Example 3 – Canceling a task using data from the UI extension for the workflow request
• Example 4 – Creating a loop for reprocessing within the workflow
• Example 5 – Sending a reminder to initiate approval when it’s delayed by the approver
• Example 6 – Assigning the approval task to the appropriate person using an if-then-else operator
• Example 7 – Updating the task topic
• Example 8 – Assigning the task to the correct team using an if-then-else operator

Important: Automation rules are executed after the entire standard logic of the R-Service (RR Tech Service Management) system has been processed. For example, if a rule is executed after a task status is set to ‘Completed’, the R-Service (RR Tech Service Management) system will first update the status of related records to ‘Assigned’ and then execute the rule.

Please note: Automation rules do not have more permissions than the person for whom they are executed. For example, if rules are executed for a workflow manager, they will only perform the actions that the workflow manager could perform manually.