LiveCycle provides the
capability to create and receive business events that occur in processes.
It stores events and delivers them to the interested parties as defined
in the system through callbacks to event handlers.
LiveCycle supports several event types:
- Asynchronous events:
- A business analyst or developer can define asynchronous events
such as Cancel Order or New Order. These events can be linked to
processes either to enable the initiation of a process or to handle
a complex process flow within an existing process. A process can
be initiated based on a New Order event and, while it is running,
can receive a Cancel Order event that enables it to change its flow
of execution based on its state. If the order was not fulfilled,
the process could refund the customer. If the order was shipped,
the process could send an invoice to the customer.
- Exception events:
- Are usually defined by component developers and allow handling
of errors during process execution. For example, the server is unavailable
and triggers an alert to an administrator, or a transaction failure allows
the developer to define a compensating transaction.
- Timer events:
- Allow processes to wait a period of time or can be associated with
activities so that a different process flow is executed if they
are not completed on time.
|
|
|