Event subscription properties (Configuration tab)
Identifies and lets you edit configuration settings for the event subscription.
State
- Enabled
- Select Enabled to enable the subscription.
Clear the check box to disable it.
- Include Subclasses
- Select if you want the subscription to apply to subclasses of the object.
- Synchronous
- Determines whether the event action assigned to the subscription runs as
a synchronous or asynchronous execution. A selected check box indicates the
event action runs in synchronous mode. A cleared check box indicates the event
action runs in asynchronous mode.
CAUTION Always
clear this option to run workflow subscriptions in asynchronous mode. Launching
a workflow takes more time than a synchronous event can handle. A Workflow
subscription must run in asynchronous mode to prevent the action from timing
out before launching the workflow successfully.
- In Synchronous execution, the call to execute the event action blocks
further processing by the subscription processor until the action completes
and returns. The action runs in the same transaction as the originating
activity on the target object. If the action fails, the transaction rolls
back.
- In Asynchronous execution, the action occurs on a separate execution
thread, allowing the subscription processor to continue without waiting
for the results of the action. The action cannot be in the same transaction
as the originating activity.
- Filter Expression (optional)
- This optionally holds an expression, in the same format as the WHERE clause
of a query but allowing only a subset of the operators, that is evaluated
against the source object or an object referenced by the source object for
an event, to determine whether the subscription should "fire".
- Filter Property Name (optional)
- Optionally specifies the symbolic name of a property, which must be a singleton
object-valued property of the source object. If set, the filter expression
is applied to the object referenced by that property, rather than to the source
itself. (An example of how this would be used is for an "element added"
event, where the source object is an RCR, but by specifying Head as the FilteredProperty,
a condition can be evaluated against the object filed).