You can map load arguments to either transient personalization keys or
propagate-to attributes to define load arguments used within a
Hybrid App, 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 argument always
comes from the 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.