Personalization APIs

Personalization keys allow the mobile user to define (personalize) certain input field values within the mobile application. The PersonalizationParameters class is generated automatically for managing personalization keys. Personalization parameters provide default values for synchronization parameters when the synchronization key of the object is mapped to the personalization key while developing a mobile business object.

• Type of Personalization Keys
  There are three types of personalization keys: client, server, and transient (or session). Client personalization keys are persisted in the local database. Server personalization keys are persisted on the Unwired Server. Session personalization keys are not persisted and are lost after the device application terminates.
• Getting and Setting Personalization Key Values
  Consider a personalization key "pkcity" that is associated with the synchronization parameter "cityname". When a personalization parameter value is changed, the call to save automatically propagates the change to the server; you need not call submitPending after the save.
• Passing Arrays of Values, Objects
  An operation can have a parameter that is one of the SUP list types (such as SUPIntList, SUPStringList, or SUPObjectList). For example, consider a method for an entity Customer with signature AnOperation: