MENU
Choose 1 option.
Cumulus Pharma uses Agentforce Life Sciences for Customer Engagement to provide Account Summaries. The Agentforce Life Sciences Consultant configured a Cross-Object Field History Graph to include related Provider Visit and Medical Inquiry records. Key Account Managers report that summaries include all related data; however, field sales reps report that their summaries exclude visit and inquiry data. Both user groups have Read access to the underlying objects.
What is the cause of this issue?
The correct answer is A because Account Summarization can use different Cross-Object Field History Graph assignments by org or profile. Salesforce Help for Life Sciences Account Summarization states that administrators can create a Cross-Object Graph for Account Summarization and assign cross-object graphs to an org or profile. Salesforce also describes the Account Summarization workflow as using configured cross-object field history so summaries can include recent and relevant account changes from related objects.
In this case, KAMs see summaries that include Provider Visit and Medical Inquiry records, while field sales reps do not. Both groups have Read access to the objects, so object permission is not the root cause. The difference is most likely profile-based summarization configuration: the graph containing Provider Visit and Medical Inquiry data has been assigned to the KAM profile but not to the field sales rep profile.
Option B is incorrect because Account Summary generation in this scenario is driven by Cross-Object Field History Graph configuration, not membership in a Data 360 segment. Option C is also incorrect because the question explicitly says both user groups have Read access. View All is not the stated requirement for using a graph in summarization. Therefore, the issue is that the Cross-Object Field History Graph is not assigned to the field sales rep profile.
=========
Currently there are no comments in this discussion, be the first to comment!