Properties Page | Property | Description |
Implementation | Integration Server Name | Assigned Integration Server Name. |
Send Protocol | The messaging protocol used to send the document. Select Subscription (For Publishable Documents), JMS (For JMS Triggered Processes) (default), or EDA (For EDA Event Triggered Processes). | |
Send Document | The document type to send.  Click Browse... to open the Choose Document window and locate a service on an Integration Server or in CentraSite.Click New... to open the Create a New Document Type window and create a new document on a configured Integration Server.Click View... to open the selected document in a document editor. The View... button is available only when a document is specified in the Document field.Note: If you drop an IS document or event type onto an existing message end step, this field is automatically populated with the IS document name. | |
Send EDA Event | For the EDA protocol only. The Integration Server document type associated with the EDA event type is displayed when using EDA (For EDA Event Triggered Processes) as the Send Protocol. This field is not editable. | |
Protocol Properties | Available for JMS and EDA protocols only. Connection Alias. Accept the default PE_NONTRASACTIONAL_ALIAS for JMS or EventBus for EDA, or click Browse to select another alias (an Integration Server connection is required). For more information, see Configuring a JMS-Triggered
Process and Configuring an EDA-Triggered
Process.Destination Name. Required. Defined by default as: projectName_ProcessName_ SUBQUEUE. To specify another destination name, click Browse (an Integration Server connection is required). | |
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. See About Joins. 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.For more information, see About Join Timeouts. | |
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. |