Trigger
Operating on the trigger-action principle, rules require a defined trigger to initiate an action. Several fields must be specified to activate a rule: Trigger type, Trigger source, and Trigger on target change. Additionally, optional fields are Monitored properties, Search filters, and Dynamic search filters. Below are descriptions of all trigger-related fields and their respective values.
Trigger type #
Trigger type denotes the event that initiates rule execution. Choose from the following options:
- Object created: Choose this option to execute the rule upon creation of the source object.
- Object changed (default): Choose this option to execute the rule whenever any change is made to the source object. The Monitored properties field becomes available.
- Object metadata changed: Choose this option to execute the rule when the metadata of the source object is changed.
- Object changed state: Choose this option to execute the rule when the source object undergoes a workflow state change.
- Object entered state: Choose this option to execute the rule when the source object enters a specific workflow state.
- Object left state: Choose this option to execute the rule when the source object leaves a specific workflow state.
- On comment: Choose this option to execute the rule whenever a comment is added to the source object.
- Scheduled: Choose this option to execute the rule at a specific time and/or on specific days.
- RunOnce: Choose this option to execute the rule only once and on all matching objects in the vault.
- Orchestrated: In cases where multiple rules are connected to the same source and trigger, choose this option to execute the rules sequentially, according to a defined order.
Monitored properties #
Displayed only when Trigger Type is set to Object changed.
This field is optional and it allows users to specify one or more properties on the source object whose change will trigger rule execution. If no properties are specified, the rule will be triggered by any change to the source object. Within the Monitored Properties section, you’ll find the following fields: Property, Monitor Type, Value from, Operator, and Value (Mode).
- Expand the Monitored Properties section.
- Click on Add Monitored Property Condition.
- Expand Monitored Property Condition [1].
By default, the Property and Monitor Type fields are visible.
Property #
Displayed only when Monitored property condition is added.
Monitored property condition [1] > Property
Specifies which property will be monitored. Select from the list or start typing the desired property. The list contains 50 suggestions of the properties within the vault. The properties are referenced by a GUID, ID or alias.
Monitor Type #
Displayed only when Monitored property condition is added.
Monitored property condition [1] > Monitor Type
Determines how the property will be monitored.
- AnyChange (default): If selected, all changes will be monitored, triggering the rule on any property change.
- WithCondition: If selected, the rule will be triggered on property change only if a specified condition is satisfied. This option reveals additional fields: Value from, Operator, Value.
Value from #
Displayed only when Monitor type is WithCondition.
Monitored property condition [1] > Monitor Type: WithCondition > Value from
Specifies the object version in which a specific condition for the property value needs to be satisfied.
- CurrentVersion (default)
- PreviousVersion
Operator #
Displayed only when Monitor type is WithCondition.
Monitored property condition [1] > Monitor Type: WithCondition > Operator
The operator for the monitored property condition is used for comparing actual and expected property values. Choose one of the following options to specify the condition in more detail:
- = (default): Checks if the monitored property is equal to the selected value.
- != : Checks if the property values are not equal.
- : Checks if the first property value is greater than the second.
- < : Checks if the first property value is less than the second.
- >= : Checks if the first property value is greater than or equal to the second.
- <= : Checks if the first property value is less than or equal to the second.
- Contains: **Checks if the monitored property contains the specified value.
- Does not contain: Checks if the monitored property doesn’t contain the specified value.
- Starts with: Checks if the monitored property’s value starts with a particular prefix.
- Does not start with: Checks if the monitored property’s value doesn’t start with a particular prefix.
Value #
Displayed only when Monitor type is WithCondition.
Monitored property condition [1] > Monitor Type: WithCondition > Value
Specifies the property value to use in the condition. It can be static or dynamic (from the current object). When expanded, the Mode field becomes available.
Mode #
Displayed only when Monitor type is WithCondition and after Property is selected.
Monitored property condition [1] > Monitor Type: WithCondition > Value > Mode
Choose from the options to specify the value:
- Dynamic value: Select this option to dynamically create the target property value from the source property value.
- Static value: Select this option to statically create the target property value.
- Empty value: Select this option to make the target property value empty.
- No action: Select this option to perform no action. This state is invalid.
Trigger on target change #
This field specifies the object whose change will initiate rule execution. Choose one of the following options:
- Yes (default): The rule will be triggered on both source and target object changes.
- No: The rule will be triggered only on source object change.
Trigger source #
For event-based triggers, these filters define the source object whose change will trigger rule execution. For the Scheduled and RunOnce trigger types, these filters are used to find objects on which the rule will be executed. Populate all necessary fields to define the source object. The following fields are available under Trigger source: Object type, Class, Workflow, Workflow state, as well as optional Search filters and Dynamic search filters.
Object type #
Specify the object type of the source object by selecting from a list of available object types within a particular vault. The object types are referenced by a GUID, ID or alias.
Class #
Specify the class of the source object by selecting from a list of available classes within a particular vault. If an object type is specified, select from a list of classes within that object type. The classes are referenced by a GUID, ID, alias or external ID.
Workflow #
Optionally, specify the workflow of the source object. If Trigger type is related to the state (such as Object changed state, Object entered state, Object left state), this value must be specified. Select from a list of workflows within a particular vault. The workflows are referenced by a GUID, ID or alias.
Workflow state #
Specify the workflow state of the source object by selecting from a list of available workflow states within a particular workflow. NOTE! If you have entered a workflow state, you must also specify the workflow above.
Look in #
Determines whether the source object must meet the specified conditions in its current version or any version throughout its history. This additional option becomes available after specifying the conditions Workflow, Workflow state, Search conditions or Dynamic search conditions. If only Object type and Class of the source object are specified, the system defaults to searching for an object that currently satisfies the search criteria. Choose between two options:
- LatestObjVersion (default): Select this option to ensure that the current version of the object matches the specified conditions for it to be considered a source for this rule.
- AllObjVersions: Select this option to ensure that any version of the object matches the specified conditions for it to be considered a source for this rule.
Search filters #
These optional filters define the search conditions that the object must meet. NOTE! Multiple filters are combined with the OR operator, meaning that the rule will be triggered if any of the filters are active. Multiple conditions within a single filter are connected with the AND operator, meaning that all need to be conditioned to trigger the rule.
- Expand Search filters.
- Click on Add Filter.
- Expand Filter [1].
The Search conditions field becomes available.
Search conditions #
Trigger source > Search filters > Filter [1] > Search conditions
These are optional additional conditions that the source object needs to satisfy. Conditions within a single filter are combined with the AND operator, while multiple filters are combined using the OR operator. These conditions can be set only for properties with static values.
Dynamic search filters #
These optional dynamic search filters specify additional search conditions that the object must meet. Multiple filters are combined using the OR operator. Here, you can condition two properties, for example, specifying that the start date must be after the end date.
- Expand Dynamic search filters.
- Click on Add Dynamic search filter.
- Expand Dynamic search filter [1].
Additional fields will appear: Property, Operator, Value, and Mode.
Property #
Displayed only when Dynamic search filter is added.
Trigger source > Dynamic search filters > Dynamic search filter [1] > Property
Specifies the property whose value will be checked. Select from the list or start typing the desired property. The list contains 50 suggestions of the properties within the vault. The properties are referenced by a GUID, ID or alias.
Operator #
Displayed only when Dynamic search filter is added.
Trigger source > Dynamic search filters > Operator
The operator used for comparing actual and expected property values. Choose one of the following options to specify the condition in more detail:
- = (default): Checks if the monitored property is equal to the selected value.
- != : Checks if the property values are not equal.
- > : Checks if the first property value is greater than the second.
- < : Checks if the first property value is less than the second.
- >= : Checks if the first property value is greater than or equal to the second.
- <= : Checks if the first property value is less than or equal to the second.
- Contains: **Checks if the monitored property contains the specified value.
- Does not contain: Checks if the monitored property doesn’t contain the specified value.
- Starts with: Checks if the monitored property’s value starts with a particular prefix.
- Does not start with: Checks if the monitored property’s value doesn’t start with a particular prefix.
Value #
Displayed only when Dynamic search filter is added.
Trigger source > Dynamic search filters > Dynamic search filter [1] > Value
Specifies the property value to use in the condition. It can be static or dynamic (from the current object). When expanded, the Mode field becomes available.
Mode #
Displayed only when Dynamic search filter is added.
Trigger source > Dynamic search filters > Dynamic search filter [1] > Value > Mode
Choose from the options to specify the value:
- Dynamic value: Select this option to dynamically create the target property value from the source property value.
- Static value: Select this option to statically create the target property value.
- Empty value: Select this option to make the target property value empty.
- No action: Select this option to perform no action. This state is invalid.