Escalation rule fields
Field |
Description |
---|---|
Clone an existing rule |
The existing rule that the new rule is based on. |
Clone the actions associated with the rule |
Clones the actions of the existing rule selected in Cone an existing rule. |
Table or view |
Table: The table that's checked to see if the rule conditions are met. View: The table view that's checked to see if the rule conditions are met. Views let you customize the set of fields within the JavaScript condition. It's good practice to base escalation rules on views rather than tables to reduce the number of records that are checked. If you select View, ensure the correct entity is displayed in Table. |
Rule name |
The name of the new rule. |
Available for cloning |
Includes the new rule in the Available for cloning list so you can base other rules on this rule and its associated actions. |
Rule enabled |
Activates the rule. |
Type |
A read only field that's set to Escalation Rule. |
Alternative image for rule |
The image that's displayed in the UI if this rule is visible to the end user. The default image is a small green bullet (WORKFLOWDEFAULT.GIF) followed by the rule name.
To add a new GIF, ensure it's saved in ...WWWRoot\Themes\Img\[theme name]\Buttons in the Sage CRM install and select it from this drop-down. |
Restricted to team |
Restricts the rule to users who belong to this primary team. |
Order |
The order in which the field appears on screen when progressing a workflow rule. |
Interval
|
The interval (in minutes) at which the escalation rule runs. If a specific escalation rule takes longer to fire than other rules, it's a good idea to specify a value in this field. This value overwrites the value in Notify Interval in Workflow & Escalation Configuration. For more information, see Workflow and escalation settings. |
.NET |
Not applicable to escalation rules. |
Custom file name |
Not applicable to escalation rules. |
Method name |
Not applicable to escalation rules. |
Trigger SQL clause |
A condition in the form of an SQL WHERE clause. Rule actions occur only when the condition is met. The WHERE term is assumed so you don't need to add it to this field. You can use # codes within SQL trigger clauses conditions. For more information, see Using the ## and # symbols.
When you create a notification rule, the user must be able to dismiss and snooze the notification. The WHERE clause must include ‘ and xxxx_datetimefield < #T’, and the action must use the same ‘xxxx_datetimefield’ name. When the user dismisses the notification, the field specified in the action is set to null. When the user snoozes the notification, the field specified in the action is set to the current time plus the number of snooze minutes.
When you create an email rule, you must include a stop clause so the email is sent only once. Add a field to the table to flag if the email has been sent. The WHERE clause must include ‘and xxxx_emailsent = null’. In addition to the email action, add a field action to Set Column Value that sets xxxx_emailsent to Y.
For more information, see Trigger clause examples. |