Considerations for creating a rule
Review some important considerations before creating a rule.
Consider the following before writing a rule:
- Determine the object type and the purpose of the rule. The object type determines the context of the data that is provided to the rule.
- Determine the ordered activities. If there are multiple activities, determine the order of those activities.
- Consider designing workflows especially if you have repeatable processes that can be used in various situations. For example, you want to schedule a task (A) to be created after the completion of a specific task (B) and depending on the outcome yet another task (C).
- Determine if the rule is to be invoked automatically or by a user from a menu item.
- Determine the conditions, if any, which must be satisfied before invoking the rule. If there are multiple conditions, determine whether any one or all conditions must be satisfied.
- Determine the order of the automatic rules. When invoking multiple rules, they are invoked in the assigned order.
- If you want to communicate information to other processes, make sure to choose one or more destinations.
- If you want to run a script, make sure to choose the appropriate script. You create and manage scripts in the Scripts tab.
Important: When developing and testing your rules, it is recommended to include a condition that prevents the activities from inadvertently being invoked against production incidents until you are sure they are ready.