7.3

Table Of Contents
Table 110. Details Tab Options
Options Descriptions
Name By default, the displayed name is the name of the selected
workow.
This name is displayed in the subscription list. The name
must be unique in the tenant.
Priority The order in which the blocking subscriptions run.
Zero is the highest priority. If an event topic has multiple
blocking workow subscriptions with the same priority,
the subscriptions are then processed in alphabetical order
based on the subscription name.
This option is only available for blocking workow
subscriptions.
Timeout (min) Specify the number of minutes the workow has to nish
before it is considered failed.
If the workow fails to nish in the specied amount of
time, the workow is canceled and the message is sent to
the next subscription in the priority list.
If you do not provide a value, the timeout is unlimited.
Services that expect a reply, to blocking or replyable events,
might have their own default timeout values. For example,
IaaS provisioning and life cycle event topics time out at 30
minutes. This value is congured on the IaaS server.
Approval topics have a 24 hour default value. This value is
congured on the system.
Description By default, the displayed description is the workow
description.
Blocking Determines if the workow can block subsequent
workows for the same event topic from receiving an event
message while waiting for a reply.
Subscriptions with blocking enabled receive messages
before subscriptions that are not congured as blocking for
the same event topic, based on priority order. When the
workow is nished, a message is sent to the next
prioritized blocking subscription. After all blocking
subscriptions have processed, the message is sent to all
non-blocking subscriptions simultaneously.
The blocking option is available only if the event topic is
blockable. This information is provided on the Event Topic
tab.
The blocking eligibility is indicated on the Event Topic tab.
n
If you do not select the check box, the event broker
does not block subsequent workows.
n
If you select check box, the event broker calculates
which workow subscriptions are eligible for this
event based on the congured conditions and runs the
workows in priority order. The event broker waits for
a response from each workow before running the next
one. All the changed parameters from the running of
the current workow are passed to the next one in the
queue.
While waiting for a response, no other workows are
notied of the event until the consuming system
responds.
You cannot modify this option after the workow
subscription is published.
Life Cycle Extensibility
20 VMware, Inc.