Cached Data

This pattern is efficient when access to cached data is sufficient to meet business needs. For example, it may be sufficient to refresh the cache once a day for noncritical MBO data that changes infrequently.



  1. EIS data is cached based on the MBO cache policy (Scheduled or On demand). Either policy lets you define the length of time for which cached data is valid.
  2. The Hybrid App requests data through an object query.
  3. Cached data is returned to the client if it is within the cache policy's specified cache interval.
Related tasks
Implementing the Cached Data Pattern for MBO-based Hybrid Apps
Generating JavaScript MBO Access API