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:
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.
{”id”:””,”op”:””,”subject”:””,”to”:””,”from”:””,”read”:,”priority”:””,”body”:””, “data”:{}
{”id”:””,”op”:”:upsert”,”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 retrieves details from the EIS.
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 argument to trigger MBO data refresh.