Print
Action Options
There are a number of actions that can be added to an automation rule based on the fields that are available on the case types in your eCase instance. The table below explains the different actions available.
| Action | Description | ||||||||||||||||||||||||
| Allocate the case to | Select the drop-down field to choose a team where the automation rule will allocate the case to. This list is managed via the Organogram screen. When allocating the case to a team, the default is to assign the case to the hub coordinators at that team level. If the team doesn't have any users with the Manage a hub privilege on their user account, the case will be allocated to the team, but will appear in the Awaiting Allocation tab. Any user with the Manage cases Awaiting Allocation privilege on their user account will then see these cases. |
||||||||||||||||||||||||
| Update the field | There are a number of actions where a field can be updated based on an automation rule. When adding an Update the field action, ensure that the relevant field is available on the case type/s the rule applies to.
|
||||||||||||||||||||||||
| Add a mandatory clearance | When adding a mandatory clearance you have three options to define which clearance type you require.
|
||||||||||||||||||||||||
| Send acknowledgement email | When an action is set to send an acknowledgement email by the automation rule, the email template that will be sent is the Case Acknowledgement - Webform Cases. When creating a new acknowledgement template for the webform submissions, ensure the mail merges used on the template can be pre-populated with the data collected on the webform. For more information on email templates: 1. Add a new email template 2. Modify an email template 3. Choose a default email template |