Understand how to construct a Hybrid App DCN without payload message.
This example illustrates data flow of a WF-DCN without payload using an SAP® EIS:
- The WF-DCN pushes new messages (workitems) to SAP Mobile Server, which are then delivered to the device, for example, a Hybrid App notification.
- After the EIS sends a workitem id to SAP Mobile Server, SAP Mobile Server uses workitem MBO and workitem id to retrieve details of the workitem from the EIS.
- After SAP Mobile Server receives the message, a matching Hybrid App server starting point parses the message and extracts data fields from the message, including data into the parameter of an MBO object query operation.
- 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 argument to trigger an MBO data refresh.
- The Hybrid App 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 Hybrid App server-initiated starting point after extracting the parameter values from the WF-DCN message body.
Message format
{”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”:{}
SAP Mobile Server extracts information from the DCN message and retrieves details from the EIS.
Processing the WF-DCN without payload message
After SAP Mobile Server receives the message, a matching Hybrid App 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.