Try OpenEdge Now
skip to main content
BP Server Developer's Guide
Working with Monitoring process : Supported events
 

Supported events

Business Process Server supports external events described in Table 23 for a monitoring process.
Table 23. Event types supported for a monitoring process
Event
Description
CREATE_INSTANCE
This event triggers process instance creation in Business Process Server using the specified process name. The external process should pass EIId as part of this event, and this value must be unique across all process instances of a process. If the EIId is mapped to a process instance Id, then you should not pass the EIID. If you pass it, then BP Server ignores it, and logs a warning in the log file.
ACTIVATE_WORKSTEP
This event triggers workstep activation. The target workstep is identified using the EIId, process name, and workstep name values specified in this event. If this event contains any dataslot, then it is updated before activating the target workstep.
COMPLETE WORKSTEP
This event triggers workstep completion. The target workstep is identified using the EIId, process name, and workstep name values specified in this event. If this event contains any dataslot, then it is updated before completing the target workstep.
UPDATE_DATASLOT
This event updates the dataslot. The target process instance is identified using the EIId, and process name specified in this event. BP Server processes this event as and when it is received.
In Progress Developer Studio for OpenEdge, you can configure ACTIVATE_WORKSTEP as mandatory for a monitoring process. Refer to the "Configuring monitoring workstep" section in OpenEdge Getting Started: Developing BPM Applications with Developer Studio for more information.
*If ACTIVATE_WORKSTEP event is mandatory for a monitoring process, then it will wait for ACTIVATE_WORKSTEP event, before proceeding with the COMPLETE_WORKSTEP event, even if it has arrived.
*If ACTIVATE_WORKSTEP event is not mandatory, then the workflow will process the event which comes first. For example, if COMPLETE_WORKSTEP event comes before ACTIVATE_WORKSTEP event, then it is processed and the ACTIVATE_WORKSTEP event is moved to invalid event table.
Alternatively, you can use the ABL APIs to work with the monitoring process in the Business Process Server. These ABL methods: StartProcess( ), ActivateWorkstep( ), CompleteWorkstep( ), UpdateDataslots( ), and GetProcess( ) enable you to work with monitoring process in the Business Process Server. These methods are public methods of the Progress.BPM.UserSession class. For more information on these ABL methods of the Progress.BPM.UserSession class, see the OpenEdge Development: ABL Reference guide.
* JMS event gateway
* Connecting to a JMS event gateway