All Mobile Workflow applications with a shared storage key assigned share the storage with other Mobile Workflows that have the same storage key assigned.
- When the last Mobile Workflow application with the shared storage key is removed from the device, the storage data is also removed.
- Since shared storage data is loaded into JavaScript, the same limitations apply to it as that which applies to the JavaScript size limitation as established for each platform. See the topic AttachmentViewer and Image Limitations. If a large amount of data is involved in the operation, the shared storage should be used only to store the reference or location of the data, not the data itself. This helps to ensure you stay within the JavaScript size limitations.
For example, if data for an image needs to be saved in shared storage for later use, the image data should be stored in the device file system or the persistent store, and then store only the file path to the shared storage.
- Shared storage items are removed when the last Workflow using the same shared storage key is removed from the device (it happens on unassignment
- On Windows Mobile devices, there is a 500K limitation for the length of the shared storage item. If the length of a shared item is more than 500K, the JavaScript does not accept anything.