The requirement is to make the signature pad a mandatory step in the mobile consent capture flow. This is a user interface and business process enforcement rule, not just a data validation rule. The Life Sciences Cloud application includes a dedicated "Admin Console" for configuring application-specific behavior. Within this console, the "Consent Administration" section allows administrators to define the consent capture process, including making the digital signature section required, which enforces the appearance and mandatory completion of the signature pad in the mobile app's UI flow.

A. Create a validation rule...: A validation rule only triggers upon saving the record, providing a poor user experience. It doesn't make the UI element mandatory during the capture flow itself.

C. Assign the Agentforce Enforce Electronic Signature custom permission...: A custom permission grants the ability to perform an action; it does not enforce that the action must be taken in a specific process.

1. Salesforce Health Cloud Developer Guide. "Consent Management Objects". The guide describes the CommunicationSubscriptionConsent object, which stores consent details, including a lookup to a signature record. The UI for capturing this is managed separately.

2. Salesforce Industries. "Intelligent Sales for Health". "Set Up Consent Management". The setup documentation for Consent Management in Industries applications details the administrative steps. This includes using a dedicated admin console or settings page to configure consent templates and capture flows, with options to make specific sections like signatures mandatory. This ensures compliance and a consistent user experience on mobile devices.