A Subscription indicates that a subscriber is interested in being notified about an event by subscribing to an event topic and defining the criteria that triggers the notification.
Extensibility subscriptions allow you to extend vRealize Automation product site by triggering ABX extensibility actions or vRealize Orchestrator Workflows at specific life-cycle events also known as Event Topics .
// Run subscription for specific user. Use when testing blocking subscriptions.
event.userName == ‘email@example.com’
// Run subscription for specific blueprint. Take the blueprint ID from blueprint page URL. This can be done only for provisioning related topics.
For example, the event and workflow or action only triggers if the boolean expression is ‘true’. This is helpful for scenarios where you want to control when events, actions, or workflows are triggered.
Action/workflow, you can select ABX extensibility actions or vRealize Orchestrator Workflows to be executd whenever there is a match for the subscription.
Blockable, Event Topics allow Blocking Subscriptions. Marking a subscription as Blocking will block any other subscriptions of this Blockable Event Topic and Condition, until this Action/workflow has been finished.
Timeout, is the time in minutes to wait until the Action/workflow fails. From 0 to infinite, where 0 means no timeout. !!! Depends on the Subscription scope’s “Request Timeout” of each Project (if “Any Project” option is selected as Subscription scope, you may need to manually change all Projects' “Request Timeout” if this Blocking Subscription’s Timeout exceeds the Project’s default “Request Timeout”).
Priority, the order of execution of blocking subscription on the event topic, where 0 means highest priority, 10 means lowest (default).
Projects, define the scope where the subscription will be active. For events coming from projects not listed in the table below, this subscription will not be active.
Subscriptions can also be versioned and compared