Configuring Mobile Business Objects for Mobile Workflow Online Data Access

You can define load parameters that determines what data to return to a Mobile Workflow application.

You can map load parameters to either transient personalization keys or propagate-to attributes to define load parameters used within a Workflow application, the difference is:

personalization keys – the value is passed in as personalization key values. For example, a user name and password that returns a result set for that particular user.
propagate-to attribute – when this method is used, and the MBO uses an Online cache group policy, the value of the load parameter always comes from findByParameter object query parameter. And the data is real-time enterprise information system (EIS) data. That is, every call to the object query results in an immediate data refresh, and delivery of requested data to the client.

Defining Mobile Workflow Load Parameters From Mapped Transient personalization Keys
Map load parameters to transient personalization keys. Specify values for those personalization keys when you invoke an operation or object query from the mobile workflow form.
Defining Mobile Workflow Load Parameters from Mapped Propagate to Attributes
Create an MBO with at least one load parameter, map parameters as propagate to attributes, then assign the MBO to a cache group that uses an Online policy.

Parent topic: Load Parameters