Receiving event throws

Processes receive events to react to events when they are thrown. Event receives are activities that you add to the process diagram of long-lived processes. Event receives react to event throws during the process that they belong to is executing.
Note: Event receives cannot be added to short-lived processes.

Event receives appear as icons on the process diagram. Event receives can have routes that begin or terminate at the event in the same way that operations do. When a route is followed to the event receive, the event receive waits for an event to be thrown. The process continues only after the event is received and acted on according to the event filters that are configured on it. Event filters define the criteria to which your event receive responds. For example, you can configure your event to respond only when the event message data for field exceeds a value.

Event receives can receive event throws in another process or application, in the same process, or in an Adobe Flex application that uses the event framework.

Add and configure event receives

* New for 9.5 *

You can add an event receives to long-lived processes for timer, asynchronous, and exception event types.

  1. Drag the Event Picker from the Activity Toolbar to an unused part of the process diagram.

  2. (Optional) In the Name box, type a new name to replace the default name.

  3. (Optional) To search for a specific event, replace the default string in the Find box with a value.

  4. Select an event type from one of the event categories and click OK.

    Note: The Timer category appears only after you create and deploy at least one custom timer event. LiveCycle ES2.5 does not provide default system timer events. Custom timer events that are not deployed are listed in the current application category. (See Custom event types .)

  5. In the Event Behavior Configuration dialog box, select Event Receive.

  6. (Optional) Add event filters. (See Creating event filters .)

  7. (Optional) Store event data to process variables. (See Storing event data to process variables .)

  8. Click OK.

// Ethnio survey code removed