WebSphere Lombardi Edition 7.2 > Modeling processes > Advanced modeling tasks
Modeling events
Lombardi enables you to model events that can occur at the beginning, during, or at the end of a run-time process (as opposed to activities that are performed by participants within the process). You can include the following events in your Lombardi Business Process Definitions (BPDs):
| Event | When to use... | For more information, see... |
|---|---|---|
| Use to model the start of a process if you
want to enable process participants to start a process manually from Lombardi
Process Portal. Also use to model the start of nested processes. Use the Start
Message Event if you want an incoming message or event to kick off a process.
A Start Event is automatically included each time you create a BPD. A BPD can include one Start Event and multiple Start Message Events if you need to be able to start the process more than one way. | Create a BPD |
| Use to model escalation paths or delays in your BPDs. Using a timer event, you can specify a time interval after or before which some activity is performed. | Modeling timer events |
| Use to indicate a point in a process at which you want Lombardi to capture the run-time data for reporting purposes. | Create a basic custom report and Create a more advanced custom report |
| Use to end process execution.
An end event is automatically included each time you create a BPD. | Create a BPD |
| Use to model the start of a process if you
want an incoming message event to start a new instance of the process. The
start is triggered by the completion of the Undercover Agent (UCA) that you
select.
A BPD can include more than one Start Message Event. | Modeling message events |
| Use when include ad-hoc actions that can be executed at any time during process execution. For example, you can include an ad-hoc event to enable end users to cancel a customer order at any time during the ordering process. | Use ad-hoc events |
| Use to model a message event received while a process is running. The event is triggered by the Undercover Agent (UCA) that you select. | Modeling message events |
| Use to close all running tasks associated with the process and to cancel all outstanding timers. The process shows a status of Terminated in the Inspector. | Modeling timer events and Modeling message events |
| Use to catch process execution exceptions and handle exceptions with an error handler activity or further process flow. | Handling exceptions |
| Use to throw an exception to parent processes. | Handling exceptions |
Intermediate events (Timer Events, Intermediate Message Events, and Intermediate Exception events) can be attached to activities within your BPDs or they can be included in the process flow, connected with sequence lines. Other events are simply included in the process flow.
Parent topic: Advanced modeling tasks