Requiring Consent Capture for Channel Source Changes
- Windows Tablet
By default, end users can edit channel sources directly from the Consent Capture screen to easily update an account’s information, for example, email addresses. However, certain regulations require users to capture consent immediately after editing an HCP’s information.
For example, Sarah Jones is capturing Dr. Clinton Ackerman’s consent for email and Dr. Ackerman notices his email address is incorrect. Sarah updates the email address from the Consent Capture screen and requests Dr. Ackerman to grant consent so the changes are saved.
Configuring Required Consent for Channel Source Changes
- Grant the following FLS permissions to the Reject_Channel_Source_Edit_On_Cancel_vod field on the Consent_Header_vod object:
- Consent admin – FLS Edit
- End user – FLS Read
- Add the Reject_Channel_Source_Edit_On_Cancel_vod field to the Consent_Header_vod page layout.
If data change requests (DCRs) are enabled, ensure fields specified in the Channel_Source_vod field on the appropriate Consent_Type_vod record (for example, an account’s email addresses) are DCR Editable or DCR Editable Required. See DCR Controlled Fields for more information.
Requiring Consent Capture for Channel Source ChangesEnsure the Status_vod field on the Consent_Header_vod object for the consent header record is not Active.
Consent admins can select the Reject_Channel_Source_Edit_On_Cancel_vod check box on the appropriate consent header record.Set the Status_vod field on the Consent_Header_vod object for the consent header record to one of the following:
- Active – displays consent channels and lines on the Consent Capture screen and prevents further editing
- Staged – hides the consent records from end users while allowing consent admins to review how the Consent Capture screen displays
After editing the channel source value for an account, end users must capture consent from the HCP to confirm the update.
See Managing Channel Values for more information.