Creating a Personalization Key

Create a personalization key using the Personalization Key wizard.

1. Launch the Personalization Key wizard from either the:
   • WorkSpace Navigator – right-click the Mobile Application project, the Personalization Keys folder within the Mobile Application project, or an existing personalization key within the Personalization Keys folder and select New > Personalization Key.
   • Mobile Development perspective – select File > New > Personalization Key , or File > New > Other > Mobile Application Project > Personalization Key.
   The New Personalization Key wizard displays:
2. Follow the wizard instructions and click Finish to create the new personalization key:
   • Mobile Application project (available only if invoked from the Mobile Development perspective) – the project in which this personalization key is created. The newly created personalization key will be displayed under the Personalization Key folder of the selected Mobile Application project.
   • Name – the name of the personalization key
   • Type – select the supported data type of the personalization key value. If the type is an array, for example String[], then it supports a list of values.
   • Nullable – accepts null as a valid value.
   • Protected – obfuscates the personalization key value, making it more secure.
   • Default value(s) – supports multiple values. Select the ellipsis (...) to Add or Delete multiple default values in these situations:
     • The type is BINARY/DATE/DATETIME/TIME.
       Note: If you add a default value, for these data types, the default value is initially read only. To edit this value, click the elipsis (...) in the Edit Properties dialog of the wizard. For the DATETIME and TIME types, note that you can add or edit the millisecond value. The precision of millisecond is limited to three digits. For example, a value of .1 is rendered as .100.
     • The type is a primitive list. For example, STRING[], BINARY[], and so on.
     • The type is a structure or list of structures.
     All default values must be of the same data type as specified in the Type field.
   • Storage – determines where the key values are stored and maintained. Options include:
     • Server – on Unwired Server
     • Client – on the device client
     • Transient – only saved in memory of the current login session
   • Description – (optional) the description of this personalization key