Designer 10.7 | webMethods BPM Process Development Help | BPMN Event Steps | Basic Event Properties
 
Basic Event Properties
Note:
Some events do not provide all of the property pages listed below, depending on the event behavior. For example, a terminate end event displays only the General and Documentation pages.
The following table describes the Basic Event properties.
Properties Page
Property
Description
General
Type
The event type. Make a selection in this drop-down to change the event type. Choices are limited to the secondary types of the current primary event type. To change the primary event type, use the speed buttons as described in Working with Speed Buttons.
Throw Event
Intermediate message and signal events (NOT including boundary events) only. Select this option to implement throwing (sending) behavior.
Catch Event
Intermediate message and signal events (NOT including boundary events) only. Select this option to indicate catching (receiving) behavior. Selected by default.
Allow [event type] to interrupt step
Intermediate boundary timer, message, and signal events only. Select the check box to enable interruption. Clear the check box to disable interruption.
Label
Step name. Default is [EventType]1.
Step ID
Automatically generated identifier, unique within the process. Not editable.
Font Style
Format of the Label text in the process editor and in the HTML Documentation Report. You can select the Font Name, Font Size, Bold, Italic, and Font Color. Default settings are Tahoma 8 point black, with no bold or italic.
Description
Descriptive information about the step, for documentation purposes only. Text in step descriptions is searchable.
Reset Default Size (button)
If the step has been manually resized, click this button to return the step to its default size.
Documentation
Documentation Fields
Local and default documentation fields that you define to document the process. Documentation fields are searchable. For more information, see About Process Documentation.
Documentation Field Value
The text you type that will appear within the Documentation Field.
KPIs
KPIs for <Step Name>
Step-level KPI (Key Performance Indicator) definitions. For more information about the fields on this page and how to work with them, see About KPIs.
KPI Properties
Information used to describe a KPI: Name, Description, Unit of Measure, Associated Field, Aggregation Type, and Dimensions.
Name
Name of the KPI.
Note:
KPI names must be unique on a given Optimize server. Designer cannot, at design time, detect all the KPI names on the target server. However, if you duplicate a KPI name in a process, generation of the process produces a warning.
Description
Description of the KPI.
Unit of Measure
How the KPI is measured.
Associated Field
Associate the KPI with actual fields in the process. Only fields that are available in the output of the step can be used.
Note:
When you associate an output field with a KPI or a dimension, Designer automatically adds the field to the Logged Fields page in the Properties view. Designer does not, however, automatically remove an output field from the Logged Fields page in the Properties view if you remove it from a KPI or dimension.
Aggregation Type
Aggregation type can be set to SUM, AVERAGE, or LAST VALUE
Dimensions
Use this area to add, delete, and manage data dimensions for a selected KPI. You can associate a field from the step output with one or more dimensions.
Note:
Dimension names must be unique on a given Optimize server. Designer cannot, at design time, detect all the dimension names on the target server. However, if you duplicate a dimension label in a process, generation of the process produces a warning.
For more information, see About KPIs.
Inputs / Outputs
Inputs
Data flowing into the step. You can add and remove inputs manually, as well as add or update from the service signature. For more information, see About Inputs and Outputs.
Outputs
Data flowing out of the step. You can add and remove outputs manually, as well as add or update from the service signature.
Edit Data Mapping (link)
Opens the Data Mapping editor for the input and output of the step. An Integration Server connection is required.
For more information about the fields on this page and how to work with them, see About Inputs and Outputs.
Transitions
Available only when the event has a transition line drawn to one or more steps.
Transition Type
For information about transitions in general, see About Transitions.
Defines the transition behavior. Options are If Condition, Default, Join Timeout, Iterations Exceeded, and Unsatisfied Join.
Note:
Some steps do not support certain transition types. A warning message appears if you select a transition type that is not supported by the step.
For more information about these transition types and their configuration fields, see:
Timer Condition
This page is available only for boundary intermediate timer events.
The timer duration value to apply to the intermediate timer event. The source of this value can be:
*A static value that you define.
*A value from a field in the process pipeline. The field value is interpreted in milliseconds.
*A value based on a business calendar in My webMethods Server. You can specify a static number of days, hours, and minutes, or specify a pipeline field to set the day, hours, or minutes value.
Related Topics