Mobile Workflow DCN Without Payload

Understand how to construct a workflow DCN without payload message.

This example illustrates data flow of a WF-DCN without payload using an SAP EIS:

  1. The WF-DCN pushes new messages (workitems) to Unwired Server, which are then delivered to the device, for example, a workflow notification.
  2. After the EIS sends a workitem id to Unwired Server, Unwired Server uses workitem MBO and workitem id to retrieve details of the workitem from the EIS.
  3. After Unwired Server receives the message, a matching workflow server starting point parses the message and extracts data fields from the message, including data into the parameter of an MBO object query operation.
  4. Since the MBO uses an online cache policy, the object query is mapped to a load operation, allowing the data to be passed into the load operation as a load parameter to trigger an MBO data refresh.
  5. The workflow engine converts MBO data and the WF-DCN message into a notification, and pushes it to the device's mobile inbox.

MBO cache group policy

The cache group policy of MBOs used in the WF-DCN without payload must be online. The online MBO contains the findByParameter object query with the same parameters defined in the load operation. The query is triggered by the workflow server-initiated starting point after extracting the parameter values from the WF-DCN message body.

Message format

The message format of the WF-DCN message without payload is:
{”id”:””,”op”:”:”,”subject”:””,”to”:””,”from”:””,”read”:,”priority”:,”body”:””,
“data{}}


For example:
{”id”:””,”op”:”:”,”subject”:”test”,”to”:”test”,”from”:”test”,”read”:,
”priority”:,”body”:” MATCH:SUP_MWF,TaskID:TS97200149, WIID:1470577, 
USER:PERF0111*#END#*”,“data”{}}

Unwired Server extracts information from the DCN message and retrives details from the EIS.

Processing the WF-DCN without payload message

After Unwired Server receives the message, a matching workflow server-initiated starting point parses the message and extracts data fields from the message. The server-initiated starting point sets extracted data into the parameter of an object query operation. Since the MBO used by the without payload message uses an online cache policy, the object query is mapped to a load operation. The data is passed into the load operation as a load parameter to trigger MBO data refresh.