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.
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 for the first time or to update the cache.
You can publish to cache or update cache on the:
Mobility management workspace, on the Menus tab (explained in the steps).
Mobility design workspace, on the Processes tab.
Anywhere mobility studio parameters, on the Automatic updates tab, in the Cache section. Note: Cache is only published or updated for the menus for which the Update check box is selected.
Set up the users for the mobile apps that are built with Mobility studio.
For each user, define:
The main menu that is shown if the user logs on to the mobile device. Note: if no menu is available yet, you must define the user menu later on.
The login settings to log in to the mobile app on a mobile device.
The app run time mode. Does the app run from cache or on the configuration?
For each applicable company, the roles of the user in the company.
The roles define which processes are applicable to the user. If the user menu has processes that are not applicable to the user, these are not shown to the user on the mobile device.
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 for the first time or to update the cache.
You can publish to cache or update cache on the:
Mobility management workspace, on the Menus tab (explained in the steps).
Mobility design workspace, on the Processes tab.
Anywhere mobility studio parameters, on the Automatic updates tab, in the Cache section. Note: Cache is only published or updated for the menus for which the Update check box is selected.
Set up the users for the mobile apps that are built with Mobility studio.
For each user, define:
The main menu that is shown if the user logs on to the mobile device. Note: if no menu is available yet, you must define the user menu later on.
The login settings to log in to the mobile app on a mobile device.
The app run time mode. Does the app run from cache or on the configuration?
For each applicable company, the roles of the user in the company.
The roles define which processes are applicable to the user. If the user menu has processes that are not applicable to the user, these are not shown to the user on the mobile device.