To view or edit an event's properties, double-click its Browser or list entry. The property sheet tabs and fields listed here are those available by default, before any customization of the interface by you or an administrator.
The General tab contains the following properties:
|
Property
|
Description
|
|---|
Name/Code/Comment
|
Identify the object. The name should clearly convey the object's purpose to non-technical users, while the code, which is used for generating code or scripts, may be abbreviated, and should not normally include spaces. You can optionally add a comment to provide more detailed information about the object. By default the code is generated from the name by applying the naming conventions specified in the model options. To decouple name-code synchronization, click to release the = button to the right of the Code field.
|
|
Stereotype
|
Extends the semantics of the object. You can enter a stereotype directly in this field, or add stereotypes to the list by specifying them in an extension file.
An event has the following predefined stereotypes: -
Fault – specifies the occurrence of an error in the normal execution of the process.
-
Timer – specifies a time event and needs to specify a duration (for example, 1 hour) or a deadline (for example, each Sunday). You can specify a timer value in the Expression box.
-
Compensation – specifies the invocation of a process compensation that allows you to cancel the actions performed by an already terminated process.
|
Keywords
|
Provide a way of loosely grouping objects through tagging. To enter multiple keywords, separate them with commas.
|
Predefined Events
Whether it is used in association with flows or processes, the event type symbol displays on the flow or on the process as follows:
|
Event type
|
Symbol on flow
|
Symbol on process
|
|---|
|
Timer
|
|
|
|
Fault
|
|
|
|
Compensation
|
|
|
When used in association with a process with a Generate event
implementation type, a Timer event implements a Wait activity, a Fault event
implements a Throw activity, and a Compensation event implements a Compensate
activity (see Process Properties).