Running an app on the real-time configuration in Anywhere Mobility Studio can be slow in a Tier 2 environment. In this case, you can choose to run an app on a cached configuration. This is faster, but the app can be outdated.
You can publish a menu or a process to cache.
In order for the cache to work optimally, you must set the cache limit to the required number of records. In the Anywhere mobility studio parameters, you can calculate the required cache size after you have published a menu or process to cache. The calculation gets the number of records that are created in the cache for the published menus and processes. You can use this number to set the cache limit.
To run an app from cache, for the applicable user accounts, set the Run time mode to Cache or Get from parameter. If set to Get from parameter, make sure the Run time mode field on the Anywhere mobility studio parameters is set to Cache.
You can check if a cached menu or process is still up-to-date.