Pattern 21 (Environment to Case - Push)

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

Description

The ability of a case to accept data elements passed to it from services or resources in the operating environment.

Example

During execution, each case of the Evaluate Fitness workflow may receive additional fitness measurements data from the Biometry system .

Motivation

During the course of the execution of a case, new case-level data elements may become available or the values of existing items may change. A means of communicating these data updates to a nominated case is required.

Overview

There are two distinct mechanisms by which this pattern can be achieved:

Context

There are no specific context conditions associated with this pattern.

Implementation

Staffware supports the former approach allowing startup values to be specified for cases. Websphere MQ also allows values to be specified for data elements at case commencement. FLOWer provides direct support for update of data elements during case execution through the chp_dat_setval API call. Similarly iPlanet provides a variety of XML and HTTP-based API facilities that allow the value of process data elements to be updated.

Issues

None observed.

Solutions

N/A.

Evaluation Criteria

An offering achieves full support if it has a construct that satisfies the description for the pattern. It achieves a partial support rating if there are limitations on the times at which data can be passed to cases (e.g. only at start-up).

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.

Summary of Evaluation