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 2 Next »

Event listener module are used to wait for specific events or initiate new workflow instances when event occurs. Events are triggered on domain scope and may receive events from 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}}" )

Handle Script
Script to handle event and take action to continue workflow instance. If not set worfklow engine automatically selects the first action.

Attached event data can be accessed with $Input variable as XmlNode instance.

If task configured as start point a new workflow instance is initiated and event data copied to current workflow data model for name matching nodes. If handling script does not take any action workflow instance is reverted.

If task is not set as start point, workflow instance paused and waits until event is occurs. If handling script does not take any action then workflow instance continues to wait until next event occur.

Remarks

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

  • No labels