Properties Page | Property | Description |
Implementation | Receive Protocol | Identifies the 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. Note: Dragging and dropping an EDA Event Type automatically configures the Receive Protocol to use EDA (For EDA Event Triggered Processes) |
Receive Document | Identifies the document type to receive.  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 boundary message intermediate step, this field is automatically populated with the IS document name. Note: Selecting an e-form as the step's Receive Document automatically selects the Enable content repository support check box and enables E-form properties. | |
Receive EDA Event | For the EDA protocol only. Identifies the document type to receive. The Integration Server document type associated with the EDA event type is displayed when using EDA (For EDA Event Triggered Processes) as the Receive 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). | |
E-form | Selecting an e-form as the step's Receive Document automatically selects the Enable content repository support check box and enables E-form properties. For more information on working with e-forms, see
Selecting an E-form Content Repository and the PDF publication Implementing E-form Support for BPM. Important: Incoming e-form instances must have the correct file name extension (for example, .xml for InfoPath forms, .xdp for LiveCycle forms). Otherwise, they will not trigger the receive task. | |
Content Repository | Select Browse... to specify a My webMethods Server content repository where e-form instances are monitored by the Process Engine listener. | |
Template Name | Selecting an e-form as the step's Receive Document automatically populates this field. For more information about using e-forms, see
Using E-forms in a Process and the PDF publication Implementing E-form Support for BPM. | |
Subscription Filter | The instances of a subscription document that can trigger the process. See
Working with Subscription Filters. | |
Correlation | Correlation |