Do more with the new and changed Life Sciences objects.
Engagement Execution
- Conduct remote engagement sessions with Microsoft Teams and understand the remote session’s status
- Use the new RemoteChannelServiceProvider, RemoteSessionStatus, and RemoteSessionStatusReason fields on the existing ProviderVisit object.
Engagement Planning
- Track the territories from which field users send emails for accurate reporting and goal measurement in Activity Plans
- Use the new SenderTerritoryId field on the existing LifeScienceEmail object.
- Represents the reusable configuration required to generate an end-user content asset, such as an audio summary
- Use the new Presentation Content Definition.
- Represents the AI-generated static asset at run-time, based on a Presentation Content Definition record
- Use the new Presentation Content Definition Assignment.
- Represents the AI-generated static asset at run-time, based on a Presentation Content Definition record
- Use the new Presentation Content.
- Represents information about the usage of the content asset, including number of times it has been consumed and the point till which it has been consumed
- Use the new Presentation Content Usage Summary.
Provider Engagement Compliance
- Represent the action plan that a compliance cycle is associated with.
- Use the new ActionPlan field on the existing Provider Engagement Compliance Cycle object.
- Represent additional information about related records, such as the care program with which the assessment task is associated.
- Use the new AdditionalRefRecord field on the existing AssessmentTask object.
- Indicate the restart behavior for a provider engagement compliance.
- Use the new StartOver value in the RestartBehaviorType field on the existing ActionPlanTemplate object.
- Indicate the task type for a provider engagement compliance.
- Use the new ProviderEngagementComplianceTask value in the TaskType field on the existing AssessmentTask object.
Life Sciences Cloud Mobile App
- Understand the APIs that enable offline synchronization for complex transactions in the Life Sciences Cloud mobile app
- Use the new ApiName and ApiType fields on the existing DeviceSyncTransaction object and the new ApiResponse field on the existing DeviceSyncTransactionRecord object.