Mobile metadata cache for visit management
Key Takeaway
Field reps can manage visits in the mobile app only after you create an object metadata cache configuration for each object that Visit Management needs and then generate the metadata cache. Changes don't reach the app until you generate a new cache.
The Life Sciences Cloud mobile app doesn't automatically load every Salesforce object. Field reps can manage visits on the device, online or offline, only after an admin tells the app which objects and records to store locally. The admin does this in two steps. First, create an object metadata cache configuration for each object that Visit Management needs. Then generate a metadata cache that bundles those object schemas and metadata definitions for the app.
Configuration and cache
Think of the object metadata cache configuration as the packing list and the generated metadata cache as the packed bundle. For each object, the configuration defines these things:
- Whether the object is stored locally
- How its data syncs
- Which records are included
- Which profiles get it
Generating the cache packages the object schemas and metadata definitions that the mobile app stores locally for both online and offline modes.