Selecting triggers for business rules
When you create a business rule, you can select triggers that run when certain events occur (such as after a ticket is saved) or run based on a specified frequency (for example, every 15 minutes). The available trigger options vary depending on the type of rule you select. You can use multiple triggers in a single rule, and they are all logically connected by OR operators. However, you should review Triggering sequence considerations to understand in what order rules are fired automatically.
Some triggers are available only for Rules created from a Workflow Process. For detailed information, see Configuring workflow processes.
Trigger options
The following table lists the options available for triggering business rules.
| Trigger Type | Trigger Name | Details | Used with Rule Types |
|---|---|---|---|
| Item-related (Server side) triggers | After Save | Select On Create, On Update By User Or Rule, or On Update by User. Notes: For Footprints version 12.1.02 and later,
|
|
| On Linked Item Create | Select link type. Note: The Work Target/Service Level Target : Service Level Target link type is no longer supported for the On Linked Item Update trigger for Work Target business rules. |
| |
| On Linked Item Delete | |||
| On Linked Item Update | |||
| On Create as part of a copy/move | No options. Rules with these triggers are applied to the Item where they are defined. |
| |
| Upon Item Copy | |||
| Upon Item Move | |||
| Time-Based | Select Frequency and time when the criteria of the rule is checked. |
| |
| On Screen triggers | On Screen | Select On Create, On Update, or both. This trigger is useful for assigning tickets based on category, setting field values based on other field values, giving the user informative messages based on selections they made, or changing field visibility as a user fills out a form. | Auto Assign |
| On Page Load | Select On Create, On Update, or both. This trigger is useful for defining default values, identifying assignees, or changing field visibility immediately when the page loads to hide fields that don't pertain to the situation or may be revealed later while the user fills out the form. When you apply a quick template to a record, the record page refreshes and the business rule is fired based on the selected trigger. | Default Assign | |
Workflow-related triggers | On enter | This trigger is useful when workflow state changes its value to the selected value. |
|
| On exit | This trigger is useful when workflow state changes its value from the selected value to any other value. | ||
| On transition | This trigger is useful when workflow state changes its value from a specified value to another specified value. | ||
| On any transition | This trigger is useful when workflow state changes its value from one value to another (any value change). | ||
| Update in State or Group | This trigger is useful when a record is updated in specified workflow state field value or group of values. | ||
| Updated in any Group | This trigger is useful when a record is updated in any group of grouped values of workflow state field. | ||
| Updated in any State | This trigger is useful when a record is updated with any value of workflow state field. | ||
| Approval-related trigger | On vote | No options. | General only |
Note
For a better and detailed understanding of Trigger Options, see Processing of Business Rules having After Save trigger.
Next step
Defining criteria for business rules
Comments
It would help to provide more details on some of these options. The lingo is a little confusing. For example, when it says, "On Update", does that mean when an issue is updated by the user clicking to save it, or does it mean when a user updates anything on the issue such as a field value?
What I want is when a value changes in "Impact" or "Urgency", the value in "Priority" should immediately update to reflect how the business rule is configured. In previous versions of FootPrints, it was only possible to do this using custom JavaScript.
Can you see how the terminology "On Update" isn't clearly defined here?
Other examples are "On Screen" and "On Page Load". I'm glad you gave examples of when each choice would be useful, but can you please describe exactly what the options mean and how they work technically?
Hello Randall. On screen triggers happen on screen in front of the user as they are viewing the form. This is what you would use to set the Priority based on Impact and Urgency. There is no java script required in version 12.
"On Update" is not a trigger, but a sub option of certain triggers that present themselves when those triggers are selected. It is really quite clear in the UI as On Screen Rules and After Save Rules are separate selections so you are initially deciding whether or not you want the rule to run in front of the user's eyes, or only after they have saved. After you select the trigger, you are then further deciding if you only want the rule to apply "On Create" when a ticket is being created, "On Update" when a ticket is being updated, or both.
Your explanation makes sense. I just didn't understand it based on the UI or the documentation. It would be helpful to have an explanation like yours within the documentation.
Thank you Randall for your comment. We will work with the team to update the required information.
Warm Regards,
Deval
I appreciate the explanation, Don. This helps to clear things up.
I'm sure it's all clear to you as a BMC employee, but it wasn't clear to me as a FootPrints system administrator for ten years (11.x and below). I still think it would help to make the terms more clear without requiring explanations like the one you gave me. Maybe wording like "On issue edit/update" and "On issue create" would help.