The conditions you configure for the subscription determine whether the workflow is triggered to run based on the event data.

If you select Run based on conditions, the available options can include:

  • Data. Information in the event message that is specific to the selected event topic. For example, if you create a condition for the machine life cycle event topic, the data fields are related to blueprints and machines. If you select a pre-approval event topic, the data fields are related to approval policies.

    You can also add conditions for fields that are not included in the schema by entering the path in the text box above the tree. Use the format ${PATH}. PATH is the path in the schema. Separate the nodes using ~. For example, ${data~machine~properties~SomeCustomProperty}.

  • Core event message values. General information about the event message. For example, the event type, time stamp, or user name.

To select an event topic for your workflow subscriptions, select Administration > Events > Subscriptions. Click New.

Table 1. Conditions Tab Options

Option

Description

Run for all events

The selected workflow runs when the message for this event topic is received.

Run based on conditions

The selected workflow runs when the event message is detected and the event meets the configured conditions.

If you select this option, you must specify conditions based on the event data to trigger the selected workflow for this subscription.

  • Single condition. The workflow is triggered when the configured clause is true.

  • All of the following. The workflow is triggered when all the clauses are true and you provided at least two conditions.

  • Any of the following. The workflow is triggered when at least one of the clauses is true and you provided at least two conditions.

  • Not the following. The workflow is triggered when none of the clauses are true.

If you create a condition based on a constant value, the value is processed as case insensitive. For example, if your condition is Blueprint name contains UNIX, but your blueprints use Unix in the name, the condition still processes correctly.

To change the condition name to match the blueprint name, you must first change the value to something that does not contain the same string. For example, to edit the condition UNIX, change the value to xxxx, save it, then change xxxx to Unix and save it.