Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 5 Current »

Event module is used to trigger an event to notify other listener type tasks about some specific event is occurs. Events are triggered on domain scope and may execute listeners in other processes.

In addition to common properties you can also configure the following properties for an automation task;

Event Name
Name of event. Event name can set to a plain text value (Ex: Customer.New) or may contain data template expressions to include data from data model. (Ex: "PaymentComplete.{{Id}}" )

You may also specify multiple event names with semicolon delimited format. (Ex: "Customer.New;Customer.Update.{{Id}}" )

Event Data XPath
XPath of event data to be passed to listeners. If set to empty value root element content is used. You can use $Input xml node variable to access related event data.

Handle Script
Script to handle event result and take action to continue workflow instance.

If no script defined first action is automatically selected.

Event results are stored in $Handlers named array of work item id numbers. If no listener exists array is empty.

Remarks

Events are processed in synchronous behavior and if any exception occurs transaction is rollbacked.

  • No labels