Mobile metadata cache and device support for remote engagement
Key Takeaway
To make remote engagement records available offline, create object metadata cache configurations with the type Data for VideoCall, VideoCallParticipant, VideoCallPtcpSession, and VideoCallRecording. Then generate a metadata cache so the Life Sciences Cloud mobile app gets the latest definitions.
The Life Sciences Cloud mobile app doesn't automatically load all Salesforce objects and related data. An admin chooses the objects the app stores locally by creating object metadata cache configurations. The admin then generates a metadata cache, which packages the schema of those objects for online and offline use. For remote engagement, the objects to configure are the video call objects. Remote sessions themselves are supported only in the mobile app on iPad.
Device support for remote sessions
Remote sessions are supported only in the Life Sciences Cloud mobile app on iPad. The iPad requirement applies whether the service provider is Twilio or Microsoft Teams.
The provider changes how field users and HCPs take part in a session.
| Twilio | Microsoft Teams | |
|---|---|---|
| Field users | Run the whole session in the Life Sciences Cloud mobile app | Switch between the Life Sciences Cloud mobile app and Teams |
| HCPs | Join from a web browser through a secure link to an Experience Cloud portal, without installing an app | Join in the Teams app or a browser, and often download the Teams app on mobile devices |