Load Arguments & Personalization Keys in SUP

Load Arguments in SUP :

Load Arguments control the amount of data sent to SUP Server Cache DB. Each load argument creates its own partition in the Cache DB on the SUP Server based on the load argument key value which we can set through personalization keys or through synchronization parameters. Partitions are refreshed concurrently so there will be no chance of data inconsistency. In SUP we can create multiple cache groups(i.e. On-Demand, Scheduling) and can assign different cache policies for particular Mobile Business Objects so partition in the Cache DB will be refreshed as per the policies. There is a possibility to set default value for the Load Arguments or we can pass the value through dynamic queries from the client code. In a nutshell you can consider the load arguments like as “where” clause of SQL Query and results data will be sent to the SUP Server Cache DB.

Load Argument Filtering

Personalization Keys in SUP :

Personalization Keys allow to set(personalize) load arguments or synchronization parameters value from the client code(i.e. mobile user). Multiple personalization keys can be created in the mobile application project and we can set the data type and storage for the individual keys. As per the data type personalization keys will accept the values from the client and data storage for the key value can be server,client or transient.

Mobile development supports two types of personalization keys:
User-defined : You can create multiple keys while developing Mobile Business Objects and can set the key values from the client code.
System-defined : System defined keys refer to the user’s login credentials which are used to access enterprise information system (EIS) data.

Steps to create Personalization Keys :

a) Navigate to your mobile application project in the Unwired Workspace
b) Right click on Personalization Keys in Workspace Navigator
c) Select New > Personalization Key
d) Set Name and Type for the Personalization Key and then click finish.

How to map Personalization Keys to the Load Arguments ?

a) Select MBO Attribute from the Mobile Application Diagram Editor
b) Right click > Select Show Properties View
c) Select Attributes Tab > Load Arguments Tab
d) Apply Personalization Key for the Load Arguments in the key column

How to set the Personalization Keys values ?

Personalization Keys values we can set from the mobile application code. Cache DB on the SUP Server and device will be refreshed automatically once we do synchronization. Business logic (i.e. Generated code) will add getter and setter methods in PersonalizationParameters class and we can set the values to these methods from the controller.

How are the Personalization Keys useful for the client side performance ?

Load Arguments and Synchronization parameters values can be set by personalization keys from the client code.
Load Arguments limit the amount of data (i.e. no of records) filtered between the SUP Server Cache DB and EIS. Synchronization parameters limit the amount of data filtered between Server Cache DB and Mobile DB. Therefore selected records will be refreshed in Mobile DB and this results in better performance.