The SUP Storage API allows you to store structured data on the client side.
You can also use these functions as an arbitrary key or value storage mechanism. Keys are strings, and any string (including the empty string) is a valid key. Keys cannot be duplicated in the same Mobile Workflow package. Values are also strings and values can be duplicated in the same Mobile Workflow package. Keys and values can contain multi-byte characters.
SUP Storage can span multiple screens in the Mobile Workflow application, and lasts beyond the current session. This allows the storage of user data on the client, such as entire user-authored documents.
Using platform-specific mechanisms, the items stored using the SUP Storage API are encrypted according to the particular platform policies:
Platform | Encryption policy |
---|---|
BlackBerry | PersistentStore, which adheres to the Content Protection BES IT policy |
Android | Encrypted before storing into the SQLite database |
iOS | Stored in SQLite Encryption Extensions database |
Windows Mobile | Unencrypted SQLite—security is deferred to Afaria Security Manager |
The amount of data that can be stored on the client is limited only to the available storage space on the particular platform:
Platform | Data storage |
---|---|
BlackBerry | Amount of free PersistentStore |
iOS and Android | Amount of free file system for the SQLite database, and/or the SQLite database size limit |
Windows Mobile | Amount of free file system, and/or the SQLite database size limit. |
Limitations
The amount of data that can be retrieved using the SUP Storage API, and returned to the JavaScript space, is limited to the JavaScript size limitation as established for each platform. See the topic AttachmentViewer Limitations.