Caching

Aras ProAppDesigner gives very good performance while rendering Studio, Wizard, and Dashboards because of the caching implemented at various levels. For showing any item using Aras ProAppDesigner, it needs Template, ItemType definition, and Item data. Template is cached in Local Storage on the client, it can persist across browser sessions. It has logic implemented to update the cache if the template is modified on the server. ItemType definition is cached at Session level, it also has logic implemented to update the cache if ItemType definition has changed on server side.

Item data is cached at session level as long as is being used in the Wizard for the showing UI. In case, same item is being shown in two different Wizards, for example one in the table other one in the form, it will have only one entry in the cache. If the item is being updated in one place, updated values will be shown in other places where it is being referred. As soon as all the references for the item in the cache are cleared from the UI, item will be removed from the cache.