1. Manufacturing
  2. Anywhere Mobility Studio
  3. Setting up and designing Anywhere mobility studio
  4. Set up general configuration

Run app from cache

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.


Administrator Administrator Start Start Publish to cache Publish to cache 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. Procedure 1. Click Mobility management. 2. Click the Menus tab. 3. In the list, find and select the desired menus. 4. Click Publish cache. 5. In the Publish type field, select an option. 6. Expand the Run in the background section. 7. Select Yes in the Batch processing field and fill in the other batch fields as required. 8. Click OK. 9. Click OK. Set run time mode for user  (see step 6.1) Set run time mode for user  (see step 6.1) 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. Procedure 1. Click Mobility management. 2. Click the Users tab. 3. Click Add. 4. Sub-task: Define general settings. 5. In the User ID field, enter or select a value. Note: Only use users for which a worker is defined. 6. In the Password field, type a value. 7. In the Warehouse field, enter or select a value. 8. In the Warehouse field, enter or select a value. 9. In the Company accounts ID field, enter or select a value. Note: The default company account is the one as defined for the user. 10. In the Menu field, enter or select a value. 11. In the Language field, enter or select a value. Note: The default language is the one as defined for the user. 12. Select No in the Enabled field. 13. Select Yes in the Transaction logging field. 14. In the Email address field, type a value. 15. Sub-task: Define login settings. 16. Select No in the Reset password at first login field. 17. Click Send password via email. 18. Select Yes in the Password expires field. 19. Define the number of days the password is valid after it is changed. In the Password valid days field, enter a number. Note: As a result, the password expiration date is calculated and shown in the Expiration date field. 20. In the Notify after days field, enter a number. 21. Select Yes in the Locked field. 22. Sub-task: Define app run time mode. 23. In the Run time mode field, select an option. 24. Sub-task: Define user roles per company. 25. Click the Companies tab. 26. Click Add. 27. In the Company accounts ID field, enter or select a value. 28. On the Roles tab, click Add. 29. In the Role field, enter or select a value. 30. Click the Available processes tab. 31. Close the page. Set cache parameters  (see steps 12 and 13) Set cache parameters  (see steps 12 and 13) Set the general parameters that define the:Session behavior.Transaction logging during sessions.Document types to be used for notes and images.Run time mode, and if it is Cache, also the cache limits. Procedure 1. Click Mobility management. 2. Click Parameters. 3. Select No in the Display full infolog on error field. 4. By default, inactive sessions time out after a defined time. You can decide that inactive sessions never time out. Select No in the Enable session timeout field. Note: Only if session timeout is enabled, you can run the Delete expired sessions job. 5. If the Enable session timeout field is set to Yes, define the time after which the session times out. In the Session timeout field, enter a time. Note: This is used as the default value for the Delete expired sessions job. 6. Define the transaction threshold. Transactions that last longer than the defined number of seconds count as slow. In the Transaction threshold field, enter a number. Note: This is only applicable if transaction logging is set to 'Slow logging'. 7. In the Transaction logging field, select an option. 8. Select Yes in the Log actions field. 9. Select Yes in the Log queries field. 10. In Anywhere mobility studio, you can add an option to your application design to attach a note to a record in D365 FO. To attach notes, Document management is used. Define the document type for the notes that you want to attach to records in D365 FO. In the Document type for notes field, enter or select a value. Note: - You can only use document types of the Note group. - For more information on how to set up the note option in your application design, refer to the "TI Training Material Development Guide Anywhere Mobility Studio for D365FOee" document. 11. In Anywhere mobility studio, you can add an option to your application design to attach a video or image to a record in D365 FO. To attach videos or images, Document management is used. Define the document type for the videos or images that you want to attach to records in D365 FO. In the Document type for images and videos field, enter or select a value. Note: - You can only use document types of the Image group. - For more information on how to set up the video or image option in your application design, refer to the "TI Training Material Development Guide Anywhere Mobility Studio for D365FOee" document. 12. Define the app run time mode: - Configuration: The app runs on the real-time configuration in Anywhere mobility studio. This can be slow in a Tier 2 environment. - Cache: The app runs from a cached configuration. This is faster in a Tier 2 environment, but the app can be outdated. In the Run time mode field, select an option. Note: This parameter run time mode setting is only applicable if for a user the run time mode is 'Get from parameter'. 13. You can run an app from cache. For the cache to work optimally, you must set the cache limit to the required number of records. 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 on publishing. This number is stored in the Record cache elements for Framework table group field. You can use this number to set the cache limit. To set the cache limit, go to System administration > Setup > Server configuration. In the Settings for all AOS instances section, enter the cache limit in the Record cache elements for Framework table group. Click Cache calculator. Note: The menus and processes that you publish may change. As a result, a different cache limit may be required. Therefore, check regularly whether the cache limit is still optimal. 14. Click OK. 15. Close the page. Do you want to check if  the cached configuration  is up-to-date? Do you want to check if  the cached configuration  is up-to-date? Check cache Check cache To run an app from a cached configuration, you must publish a menu or a process to cache.You can check if a cached menu or process is still up-to-date.This topic explains how to check if a cached menu is up-to-date. Procedure 1. Click Mobility management. 2. Click the Menus tab. 3. In the list, find and select the desired menus. 4. Click Check cache. 5. Expand the Run in the background section. 6. Select Yes in the Batch processing field and fill in the other batch fields as required. 7. Click OK. End End Yes No

Activities

Name Responsible Description

Publish to cache

Administrator

 		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 run time mode for user  (see step 6.1)

Administrator

 		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.

Set cache parameters  (see steps 12 and 13)

Administrator

 		Set the general parameters that define the:
  • Session behavior.
  • Transaction logging during sessions.
  • Document types to be used for notes and images.
  • Run time mode, and if it is Cache, also the cache limits.

Check cache

Administrator

 		To run an app from a cached configuration, you must publish a menu or a process to cache.
You can check if a cached menu or process is still up-to-date.
This topic explains how to check if a cached menu is up-to-date.

Provide feedback