The Agentforce Life Sciences mobile app relies on a pre-built metadata cache to render components and data efficiently, especially in offline mode. For the consent management functionality to be available and performant on the mobile app, the administrator must configure the relevant objects (like DataUsePurpose, CommSubscription, CommSubscriptionConsent) for caching. After configuration, the metadata cache must be generated. This step ensures that the mobile app has the necessary schema and configuration to display and interact with consent records.

A. Configuring Subscription Filtering Fields controls which subscriptions are displayed for consent capture, but it does not enable the core consent feature on the mobile app.

C. While the consent component must be on a Lightning page, this action alone is insufficient; the mobile app requires the metadata cache to be generated to function correctly.

1. Salesforce Help, "Configure Metadata Cache for the Life Sciences Cloud Mobile App," This document explicitly states, "To make sure that your users can access Life Sciences Cloud objects on the mobile app, configure object metadata cache." It lists Consent Management objects as requiring this configuration.

2. Salesforce Help, "Set Up the Life Sciences Cloud Mobile App," The implementation guide specifies generating the metadata cache as a mandatory post-installation step to ensure all configured features, including consent capture, are available to mobile users. Section: "Generate the Metadata Cache."