Automation Execution and is_executed Flag
Background
The UCM automation uses an internal is_executed flag on item relationships to track when a change action starts. This flag helps control when you can edit effected items during a Change order and keeps all changes within the proper workflow boundaries.
Some automations run extra steps that are not part of the actual change action. When this happens, the automation needs to set the skip_is_executed attribute so it does not accidentally mark the relationship as executed.When to Use skip_is_executed:
Use skip_is_executed="1" when the automation performs supporting operations that do not represent the execution of the change action itself, such as:
- Setting tracking properties (e.g., has_change_pending).
- Sending notifications.
- Creating audit records.
- Updating metadata unrelated to the change action.
Note
Do NOT use skip_is_executed for automations that execute the actual change action, including any operation that represents the irreversible execution of the intended change (e.g. creating new revision).
Implementation Example
The “Set has_change_pending property” automation demonstrates proper use of skip_is_executed.