SidebarSite navigation.

Cert++

Practice
Certle
Review
Tracks
Study Guide

More

About
Articles
Community
Support
Changes
Legal

Consent capture entry points on record pages and the mobile app

Key Takeaway

Users open the consent screen from record pages through the Capture Consent quick action or the Consent tab. After an admin changes a record page or page layout, they generate a new metadata cache so the change appears in the Life Sciences Cloud Mobile app.

Consent capture is how field users record which communication subscriptions and channels a healthcare professional (HCP) has agreed to, along with proof of that agreement. Admins set it up as part of consent and subscription management for data privacy compliance. In Life Sciences Cloud for Customer Engagement, users open the consent screen from record pages. The same screen works in the Life Sciences Cloud Mobile app after the admin configures and generates a metadata cache.

Two ways to reach the consent screen

Record pages offer two entry points to the same consent screen. The first is the "Capture Consent" quick action on an Account or Visit record page. The second is a "Consent" tab on the Account record page, where the user clicks "Edit" to reach the consent screen.

Agentforce Life Sciences Consultant Study Guide

Platform Administrator
Platform App Builder
Platform Foundations
Platform Developer
Platform Administrator II
Agentforce Sales Consultant
Agentforce Service Consultant
Platform Data Architect
Platform Development Lifecycle and Deployment Architect
Platform Identity and Access Management Architect
Platform Integration Architect
Platform Sharing and Visibility Architect
Heroku Architect
B2C Solution Architect
Experience Cloud Consultant
Agentforce Field Service and Operations Consultant
Agentforce Nonprofit Consultant
Data 360 Consultant
Omnistudio Consultant
CRM Analytics and Einstein Discovery Consultant
Platform User Experience Designer
Platform Strategy Designer
B2C Commerce Developer
JavaScript Developer
Omnistudio Developer
Platform Developer II
Marketing Cloud Engagement Administrator
Marketing Cloud Engagement Specialist
Marketing Cloud Engagement Consultant
Marketing Cloud Account Engagement Specialist
Marketing Cloud Next Consultant
Agentforce Sales Foundations
Business Analyst
Marketing Cloud Engagement Developer
Marketing Cloud Engagement Foundations
Agentforce Specialist
Agentforce Life Sciences Consultant
B2B Commerce Administrator AP
B2B Commerce Developer AP
Agentforce Communications AP
Agentforce Consumer Goods AP
Agentforce Financial Services AP
Agentforce Health AP
Agentforce Manufacturing AP
Public Sector Solutions AP
Revenue Cloud Consultant
MuleSoft Integration Foundations
MuleSoft Developer
MuleSoft Developer II
MuleSoft Platform Integration Architect
MuleSoft Platform Architect
Tableau Desktop Foundations
Tableau Data Analyst
Tableau Consultant
Tableau Server Administrator
Tableau Next Consultant
Tableau Architect
Slack Administrator
Slack Consultant
Slack Developer

Checklist progressProgress

0/279Learned

Checklist progressProgress

0/279Learned

Given a scenario, configure and manage Account and Relationships master data

0/25

HCP and HCO account modeling with Healthcare Provider records
Provider specialties and business licenses as account credentials
Valid healthcare provider criteria and their downstream effects
Account Address management for multi-purpose HCP and HCO addresses
Hard versus soft affiliations between HCPs and HCOs
Direct and reverse affiliation role mapping
Affiliation settings and prerequisites in the Admin Console
Affiliation list, hierarchy, and network views
Primary affiliation behavior and change governance
Institution Doctor Accounts for HCP-at-HCO tracking
Linking provider affiliations to products
Affiliation batch jobs for high-volume data loads
Account Search settings by org, profile, and record type
Search Before Create with internal and external account sources
Data Change Request configuration for governed account fields
Account Merge for duplicate HCP and HCO records
Account Teams for cross-territory collaboration
Ratings and rating cards for account segmentation
Account lists, filters, and admin-defined segments
Account record Dashboard tab components
Activity Timeline for account interaction history
Account Summarization versus Agentforce for Account Summarization
Bulk updates of account-related records from related lists
Provider affiliations versus platform account and contact relationships
Territory, product, and team-specific account details

Given a scenario, describe the processes and tasks needed to set up, configure, and troubleshoot the Agentforce Life Sciences mobile application

0/14

Agentforce Life Sciences mobile app prerequisites and offline scope
Object metadata cache configuration for offline mobile data
Generating the metadata cache after configuration changes
Mobile sync settings for offline duration and data usage
Mobile application, passcode, and UI settings by org default and profile
Mobile app translations for multilingual field teams
Global Search in the mobile app
Mobile app versus desktop site feature and component support
Deep linking into the mobile app from external apps
LSC Apps for extending the mobile app with custom components
Diagnosing records or lookup values missing on the mobile app
Device Sync Summary errors and the time-mismatch warning
Profile names that break metadata cache generation
Mobile Device Management distribution of the mobile app

Apply security and system configuration fundamentals for Agentforce Life Sciences

0/9

Permission sets and permission set licenses for Life Sciences personas
Profile and page layout minimization strategy
Field-level security versus page layouts for sensitive HCP data
Territory-based account access versus role hierarchy and sharing rules
Admin Console hierarchical settings at org default and profile levels
Audit trail and field history tracking for regulated Life Sciences records
Platform automation support on desktop versus the Agentforce Life Sciences mobile app
Security Exclusion and user access enforcement in trigger handlers
Agentforce trust and access controls for Life Sciences agents

Given a scenario, implement consent and subscription management for data privacy compliance

0/10

Agentforce Life Sciences consent data model and the consent giver

Learn this concept

Unseen

Communication subscriptions and data use purpose for product-level consent

Learn this concept

Unseen

Engagement channel types, subscription channel pairing and contact points

Learn this concept

Unseen

Consent status options and the Not Asked setting

Learn this concept

Unseen

Consent capture entry points on record pages and the mobile app

Learn this concept

Unseen

Consent proof requirements on desktop versus mobile

Learn this concept

Unseen

Consent save workflow and compliance snapshot audit trail

Learn this concept

Unseen

Filtering subscriptions, disclaimers, and terms by audience and territory

Learn this concept

Unseen

Object permissions and record sharing for consent data

Learn this concept

Unseen

Confirmation email to an HCP after consent capture

Learn this concept

Unseen

Given a scenario, configure Territory Management and assignment rules for account and product alignments

0/15

Life sciences territory alignment data model
Enterprise Territory Management account assignment rules for life sciences accounts
Territory model states and previewing account assignments
Align Account to Territory job for manual and externally loaded assignments
Align Zip to Territory versus Align Brick to Territory
Affiliation alignment rules for territories
Manual territory alignment of affiliated accounts by field users
Troubleshooting accounts that fail to align to territories
Product-territory alignment states and inheritance
Parent Territory Product Alignment admin setting
Bulk product-territory alignment from external systems
Product message alignment and exclusion by territory
Territory product alignment versus account-level product restrictions
Territory Planning setup and processing for Agentforce Life Sciences
Territory Planning area qualification with geographic containers and rules

Given a scenario, configure Agentforce Life Sciences

0/14

Agentforce Life Sciences domains and the Customer Engagement add-on
Org readiness, licensing, and the Customer Engagement managed package
Discovery workshops and user story backlog for Customer Engagement
Phased implementation sequencing for Customer Engagement features
Life Sciences product catalog structure and classification
Customer Engagement home page tailored by profile
App Alerts for field user notifications
Multi-step workflows and multi-object components
License validation checks for regulated engagement
Agentforce Life Sciences agent skills, topics, and actions for Customer Engagement
Salesforce products that extend Customer Engagement
Trigger handler management during data migration
Functional testing and release of Customer Engagement configuration
Monitoring packaged batch and integration jobs

Set up Intelligent Content, Presentations, and Field Email templates

0/17

Presentation source files and creation methods
Product, key message, and mandatory settings on presentation pages
Activation schedules and version control for approved content
Territory distribution and sharing for presentations and email templates
Targeted versus recommended presentations
Presentation player, feedback, and tracking settings
Surfacing the content library in visits and account lists
Sharing presentations by email attachment versus secure link
Expanded presentation search versus Data 360 smart content search
Org readiness and email verification for Field Email
Email template setup options for field reps
Email template ZIP files and dynamic content capabilities
Reusable email fragments versus standard Salesforce email templates
Communication subscriptions and consent on Field Email templates
Mobile app metadata cache for Field Email objects
Presentation engagement metrics and click stream data retention
Email queue monitoring, scheduled email jobs, and engagement tracking

Create standard reports, dashboards, and TabNext industry metrics

0/11

Standard and custom report types for Life Sciences engagement reporting
Dashboard running user and folder access for field reps and managers
Report Chart and Dashboard components on Life Sciences Lightning pages
Sales Data charts for prescription and drug distribution data
Mobile Reports tab settings in the Agentforce Life Sciences Admin Console
Report chart and dashboard support in the Agentforce Life Sciences mobile app
Life Sciences Data Kit for Data 360 integration
Lightning reports on Data 360 DMOs and calculated insights
Tableau Next metrics on semantic models for field KPIs
Embedding Tableau Next Metric, Visualization, and Dashboard components on Lightning pages
Followed-metrics tab in the Agentforce Life Sciences mobile app

Activity plan building blocks: Time Period records and activity measure types
Org readiness prerequisites for activity plans
Choosing an activity plan type
Associating activity plans with territories
Account-level goals and goal measures by activity type
Product-specific goal measures for launch focus
Activity plan status lifecycle and transition owners
Activity Plan Review prerequisites and tab setup
Review tab role checks from territory membership
Review deadlines and change thresholds for plan reviews
Rep and manager proposals during plan review
Final admin approval and activation of activity plans
Activity plan batch jobs and goal progress calculation
Goal progress tracking with list views and Activity Plan components
Mid-cycle Activity Plan Adjustments
Bulk goal editing and territory alignment sync
Cloning a previous activity plan for a new cycle
Activity weights and product weights in weighted goal plans
Calendar setup prerequisites across dependent features
Calendar event types and scheduling visits from the calendar
Calendar grid display: visit preview, views, and filters
Planner settings applied org-wide versus per profile
Holiday mapping to business hours for scheduling
Visit routines for recurring call patterns
Best time suggestions for HCP and HCO visit scheduling
Visit scheduling validations for overlaps and call frequency
Mirror territory shared calendar configuration
My Team calendar view for field managers
Time Off Territory prerequisites and downtime data model
Time Off Territory time input modes and time slots
Enabling Time Off Territory rules versus standard TOT validations
Time Off Territory rule scope by event type, profile, and TOT type
Working days calculation for activity plans from TOT
Account plans versus territory business plans
Key Account Management plans versus Activity Plans
Design-time template objects versus run-time plan records
Key Account Management access and trigger handler prerequisites
Goal definition templates and cascading goal levels
Action plan templates and template assignment for KAM
Account plan stakeholder mapping and influence attributes
Account plan participants and participant-stakeholder connections
Account plan products, related plans and strategic (SWOT) analysis
Tracking plan progress with completion status mappings
Sprints for time-boxed KAM plan execution
Updating KAM assessment tasks from visit records
Offline Key Account Management in the Agentforce Life Sciences mobile app
Action plan framework column customization
Next Best Action recommendation records and data sources
Next Best Action trigger handlers and user access setup
Next Best Action dependencies on visits, email, and Planner settings
Next Best Customer data, account scores, and rationales
Next Best Customers home page component setup
Next Best Customer in the Agentforce Life Sciences mobile app
Next Best Customer versus Next Best Action versus Next Best Message
Persona permission sets for Agentforce Life Sciences AI features
Enabling Agentforce account summarization for Customer Engagement
Agentforce visit planning topics and actions
Briefings audio summaries for pre-visit preparation

Remote engagement org permission, user permission and permission sets
Twilio setup for credentials, HCP Experience Cloud site and trusted URLs
Microsoft Teams setup and settings for remote engagement
Remote engagement trigger handlers for session keys and invitations
Start Remote Session actions from account lists and account records
Invitation emails and change notifications for remote sessions
Conducting and concluding remote visits with each service provider
Remote signatures for products, samples and product discussions
Signature disclaimers for remote sessions with compliance statement definitions
Remote consent capture during virtual HCP visits
Mobile metadata cache and device support for remote engagement
Twilio versus Microsoft Teams for HCP join and field user experience
Remote service provider fit for content control and engagement tracking
Multiple remote engagement service providers with separate visit channels
Visit and Provider Visit data model
Visit lifecycle stages and compliance checkpoints
Visit Management Admin Console and org readiness
Visit record types, channels and record type routing
Field Calendar scheduling tools for planning visits
Visit entry points and Quick Visit actionable list views
Pre-call preparation with Smart Summary and Account Timeline
Automated visit validations at scheduling and launch
Visit Engagement page sidebar, fields and troubleshooting
Product detailing versus product discussions in visits
Presenting Intelligent Content with the presentation player in visits
Recommendations sidebar for Next Best Messages and Content in visits
In-visit sample distribution checks and HCP license validation
Capturing HCP consent during an in-person visit
Surveys launched during HCP visits
Capturing next visit objectives
Visit compliance statements and electronic signature capture
Visit snapshot denormalization for audit traceability
Visit record page and post-visit features
Managing visits in Service Console subtabs
Group visits and attendee-level visit data
Joint visits with internal attendees and team visit sharing
Visit Agent voice-based visit logging
Mobile metadata cache for visit management
When to use Medical Insights versus product discussions and surveys
Per-profile Insight Settings in the Admin Console
Subject hierarchy for categorizing Medical Insights
Quick actions for capturing Medical Insights from Home, Account and Visit
Insight capture entry points and contextual pre-population
Insight layouts, field sets and related lists on Account and Visit records
Medical Insights Feed and tab access on web and mobile
Upvoting, tag filtering and linking for insight collaboration
Automatic territory-based sharing of Medical Insights
Extending insight visibility with public groups and sharing rules
Restricting visibility of sensitive Medical Insight topics
Mobile metadata cache for capturing Medical Insights
Formal Medical Inquiries versus Medical Insights
Parent Case versus child Inquiry in the Medical Inquiry data model
Medical inquiry lifecycle stages and role responsibilities
Profiles and permission sets for reps and MSLs in Medical Inquiries
Matching Medical Inquiry record types on Case and Inquiry
Case statuses and support process for the inquiry status ladder
Workflow path stage operations for Medical Inquiries
Update Record versus Open Component workflow actions for inquiries
Persona-based action visibility on the Inquiry record
Inquiry record page components and New/Edit button overrides
Account record page inquiry tab and one-click inquiry creation
Rep creation and submission of a medical inquiry
Capturing medical inquiries during a visit on mobile and desktop
Rep signature attestation and disclaimer for Medical Inquiries
Subjects, queues and routing of inquiries to Medical Affairs
MSL review, assignment and response to medical inquiries
Sharing settings for Inquiry Question records
Territory-based inquiry sharing with the MIRF Share Management job

Territory product quantity allocations versus sample limits
Sample limit template product assignments and product-level rules
Account segments for targeted sample limits
Sample limit initialization: batch job versus automatic initialization for new accounts
Provider sample limit and transaction records for tracking HCP consumption
Enabling HCP sample limits validation during visits
Updating or replacing sample limits after template and rule changes
Monitoring and reprocessing sample limit batch jobs
Setting up territory product quantity allocation records
Drop versus Ship allocation types for territory allocations
Territory quantity allocation validation and enforcement mode
Batch and lot traceability controls for sample distribution
License Management validations for sample eligibility
Sample limit template types for regional sampling rules
Choosing among sample inventory, territory allocation and HCP limit validations
Product disbursement trigger handlers and desktop record locking
Sample inventory setup records: locations, product items and batch items
Sample disbursement setup and Samples sidebar visibility
HCO account record types eligible to receive samples
Sample Drop versus Direct to Practitioner disbursement
Sample signature capture and validation timing on mobile versus desktop
Sample replenishment requests and approval controls
Acknowledging received shipments and transfers
Sample transfers between reps and returns to the warehouse
Sample inventory validation during disbursement
Unresolved product disbursements and their resolution
Offline Sample Inventory Management in the mobile app
Inventory count data model: assessment versus product batch item records
Inventory count assessment types and when to use each
Profile versus org-wide Sample Inventory Management settings for counts
Self-audits versus peer audits of inventory counts
Automatic discrepancy adjustments versus manual Adjustment operations
Field sets versus custom action overrides for count and adjustment screens
User access to Sample Inventory Management and its dashboard tab
Sample Inventory Management dashboard components for monitoring the stock lifecycle
Sample stock dashboards for field reps versus district managers
Report types on sample inventory transaction objects
Reporting on territory product quantity allocation usage

Prepare for the Exam

Play Today's Certle

Study Community

Ask questions and get the latest info from other Agentforce Life Sciences Consultant studiers. 757 members and growing.

Consent capture entry points on record pages and the mobile app

Key Takeaway

Users open the consent screen from record pages through the Capture Consent quick action or the Consent tab. After an admin changes a record page or page layout, they generate a new metadata cache so the change appears in the Life Sciences Cloud Mobile app.

Consent capture is how field users record which communication subscriptions and channels a healthcare professional (HCP) has agreed to, along with proof of that agreement. Admins set it up as part of consent and subscription management for data privacy compliance. In Life Sciences Cloud for Customer Engagement, users open the consent screen from record pages. The same screen works in the Life Sciences Cloud Mobile app after the admin configures and generates a metadata cache.

Two ways to reach the consent screen

Record pages offer two entry points to the same consent screen. The first is the "Capture Consent" quick action on an Account or Visit record page. The second is a "Consent" tab on the Account record page, where the user clicks "Edit" to reach the consent screen.