Workflow Initiation and Workflow Wake Up

Content

The 7.1.1.6 base services fix pack provides support for Workflow initiation and for Workflow 'wake up' by an external application. This functionality is enabled using a servlet. This functional enhancement will allow for the receipt of an XML message using HTTP that can identify a Workflow and an object which then will initiate an instance of that workflow against the identified object.

An integration servlet is now provided to invoke these services and as with other integration servlets, it can be secured via J2EE authentication. The Workflow service will be accessed via a URL in the following format:

http://<host>:<port>/meaweb/wf/APPROVEPO

where APPROVEPO is the Workflow name

The XML message format will for the Initiate Workflow will be:

<InitiateAPPROVEPO xmlns="http://www.ibm.com/maximo"&gt;
<POMboKey>
<PO>
<PONUM>1087</PONUM>
<SITEID>BEDFORD</SITEID>
</PO>
</POMboKey>
</InitiateAPPROVEPO>

where:
APPROVEPO is the Workflow name
PO is the object to be processed by the Workflow
PONUM and SITEID are the Primary Key fields* of Object.


The XML message format will for the Wake Up Workflow will be:

<WakeupAPPROVEPO xmlns="http://www.ibm.com/maximo"&gt;
<POMboKey>
<PO>
<PONUM>1087</PONUM>
<SITEID>BEDFORD</SITEID>
</PO>
</POMboKey>
</WakeupAPPROVEPO>

where:
APPROVEPO is the Workflow name
PO is the object to be processed by the Workflow
PONUM and SITEID are the Primary Key fields* of Object.

*If the object has a registered Alternate key (in Maxtable), it will be used (instead of Primary key) as it is for other integration transactions.

Integration for Workflow initiation should work in the same manner as the workflow initiation works from the applications and escalations in regard to the following:
1. Always initiates the activated revision of the work (there can only be one revision that is active and it might not be the most recent).
2. Never allow the start of a workflow process on an object when one is already in process (the workflow processing should enforce this – needs to be confirmed)
3. Allow the workflow to be initiated even if it is configured to start automatically on save of the MBO. (this is allowed through the applications as well as long as the workflow process that was started automatically has completed).

NOTE: Worklfow 'wakeup' functionality is supported by means of a Workflow Wait Node; workflow process should pause until a required condition is met.

Implementation considerations

For this fix pack, the functional scope of this enhancement is being limited to XML over HTTP and RMI support via an EJB. There is no support for Web Services or the support of a schema within this Fix Pack.

Additional MAximo Workflow Information can be found in Maximo's Knowledge Center