Designer 10.7 | webMethods BPM Process Development Help | BPMN Event Steps | About Intermediate Events | About None Intermediate Events | Advanced None Intermediate Event Properties
 
Advanced None Intermediate Event Properties
You must be working in Process Developer mode to configure the properties described in the table below.
Properties Page
Property
Description
Implementation
Integration Server Name
Assigned Integration Server Name
Receive Protocol
Type of receive protocol to use. Select Subscription (For Publishable Documents), JMS (for JMS Triggered Processes) (default), or EDA (For EDA Event Triggered Processes) from the list.
Protocol Properties
Available for JMS and EDA (deprecated) protocols only.
*Connection Alias. For the JMS protocol, accept the default PE_NONTRASACTIONAL_ALIAS or click Browse to select another alias (an Integration Server connection is required). For more information, see Configuring a JMS-Triggered Process.
For the EDA (deprecated) protocol, accept the default EventBus alias or click Browse to select another alias.
Allow Parallel Execution
Lock the step at run-time to allow it to be executed by multiple threads.
Joins
Join Type
A join type defines the logic the process follows when a step has multiple incoming transitions. Options: OR, AND, COMPLEX, or Unsynchronized OR.
Note:
The Joins page is displayed only when a step has more than one incoming transition.
Join Timeout
The timeout duration value, after which this join fails. This option is available for AND and COMPLEX joins only. 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.
Join Condition
Use the join condition editor to define a condition for the join. This option is available only for a complex join.
When the terms of this condition are met (that is, the condition is true), the join is considered satisfied.
For more information about using the condition editor, see About Complex Join Expressions and Defining a Complex Join Expression.
Deprecated properties (not recommended)
These deprecated properties are not available for unsynchronized OR joins.
Suppress Join Failure
This option is not recommended except in very isolated cases. For more information, see Migrating Process Models with Join Steps to Version 9.7 and Later.
Ignore dead path notification
This option is not recommended except in very isolated cases. For more information, see Migrating Process Models with Join Steps to Version 9.7 and Later.
Related Topics