Pattern 25 (Environment to Workflow - Push)

FLASH animation of Data Interaction - Environment to Workflow - Push-Oriented pattern


The ability of services or resources in the operating environment to pass global data to a process.


All mining permits data currently available is passed to the Develop Mining Leases process.


The rationale for this pattern is to provide applications independent of the process environment with the ability to create or update global data elements in a process.


There are three ways in which this objective might be achieved, all of which require support from the process environment:

  1. Data elements are passed into the process environment (typically as part of the command line) at the time the process environment is started. (This assumes that the external application starts the process environment or the first instance of the process.)
  2. The external application initiates an import of global data elements by the process environment or the first instance of the process.
  3. The external application utilises an API call to set data elements in the process environment.


There are no specific context conditions associated with this pattern.


Staffware provides support for the first of the options described above to set workflow configuration data. It also supports the second of these options in a limited sense through the swutil option which allows workflow tables and lists to be populated from external data files in predefined formats. WebSphere MQ provides support for the third alternative and allows persistent lists and other runtime global data elements to be updated via API calls.


None observed.



Evaluation Criteria

An offering achieves full support if it has a construct that satisfies the description of the pattern.

Product Evaluation

To achieve a + rating (direct support) or a +/- rating (partial support) the product should satisfy the corresponding evaluation criterion of the pattern. Otherwise a - rating (no support) is assigned.





Staffware 9 - Not supported
Websphere MQ Workflow 3.4 +/- Indirect support for manipulation persistent lists via API calls
FLOWer 3.0 - Not supported
COSA 4.2 - Not supported
XPDL 1.0 - Not reported
BPEL4WS 1.1 - Not supported
BPMN 1.0 - As workflow data is not supported, any data interaction to and from a workflow is not applicable
UML 2.0 - Not supported
Oracle BPEL 10.1.2 - Not supported
jBPM 3.1.4 - jBPM does not support this pattern.
OpenWFE 1.7.3 - OpenWFE does not support this pattern.
Enhydra Shark 2 - Enhydra Shark does not support this pattern.

Summary of Evaluation

+ Rating

+/- Rating

  1. Direct support for the workflow engine to accept externally generated data during execution
  1. Achievable via programmatic extensions