Create and Manage a Presentation
Learning Objectives
After completing this unit, you’ll be able to:
- Describe the records that define a presentation, and connect its pages with products and guidance messages.
- Compare the available methods for adding approved presentation content to Agentforce Life Sciences.
- Configure presentation pages with the context and controls required for field use.
- Explain how presentation settings and version management govern content availability.
Structure Approved Content for Field Use
An approved PDF or HTML5 package supplies the content that representatives present. Intelligent Content adds the Salesforce records that organize pages into a presentation, connect them with products and guidance messages, identify required content, and manage availability.
Throughout this badge, you follow Cumulus Pharma as it prepares approved presentation content for the launch of Immunexis, a fictional specialty biological product for autoimmune disease. The content begins as a set of approved HTML5 assets. In this unit you give those assets the structure needed to govern, deliver, and measure them.
Confirm the Supporting Configuration
Before creating presentations, prepare the data, access, and platform configuration that Intelligent Content relies on.
- Install Agentforce Life Sciences for Customer Engagement and assign the required permissions and field access.
- Configure the products and Product Guidance messages that presentations reference, and activate a territory model that aligns users and products.
- Set the organization-wide defaults for Presentation and Presentation Page to Private.
- Enable the Agentforce Life Sciences trigger handlers required for presentation processing.
- Generate an Object Metadata Cache for the core presentation objects to support offline mobile access.
- Prepare the approved PDF or HTML5 ZIP source files.
Read Get Your Org Ready for Presentations in Salesforce Help for the complete setup procedures.
Learn About the Presentation Data Model
A Presentation record defines the deck and stores its presentation-level settings. Related records identify its pages, associate those pages with source files, and connect them with products and guidance messages.
The following records form the core structure you work with when creating and maintaining a presentation.
-
Presentation (1) is the parent deck record. It stores presentation-level information such as its name, topics, and presentation-player configuration, including navigation, control placement, and zoom behavior.
-
Presentation Page (2) represents an individual content item available to the player. It stores page-level properties, including whether the content is mandatory, and associates the page with its source file.
-
Presentation Linked Page (3) connects a Presentation with its Presentation Pages. This junction allows an approved page to appear in multiple presentations without creating a separate copy.
-
Presentation Page Product (4) connects a page with its product and message context. Its product relationship can point to a Product2 or Life Science Marketable Product record.
-
Product Guidance (5) identifies the approved product message associated with the page through Presentation Page Product.
Together, these relationships separate the deck, its reusable pages, and the commercial context assigned to those pages. That structure helps administrators to assemble presentations from approved content and associate later page activity with the relevant products and messages.
Presentation files use the standard Salesforce Files model. ContentDocument identifies the file, ContentVersion maintains its versions, and ContentDocumentLink associates it with the related record. Other objects shown in the model support field interactions, external sharing, and engagement tracking and are covered in later units.
Select an Ingestion Route
Choose an ingestion route based on where the approved content originates, whether its pages already exist in Salesforce, and how much content to load.
-
Upload New Pages creates Presentation Page records from PDF or HTML5 ZIP files on a local drive. Use it for content entering the org for the first time.
-
Use Existing Pages assembles a presentation from active pages already in the library. This supports reuse of approved safety pages, clinical reprints, and other shared content.
- The Content Management REST API supports automated or high-volume ingestion from regulated content or digital asset management systems. Monitor processing from the API Job Queue in the Admin Console.
For the Immunexis launch presentation, the approved HTML5 packages are new to Salesforce, so the administrator selects Upload New Pages.
Upload and Validate Source Files
The file type determines how Salesforce creates the presentation pages and how the content behaves in the player.
- An HTML5 ZIP package supports interactive detailing and can contain HTML, media, surveys, and custom interactions. Each package creates one Presentation Page.
- A PDF provides static content with consistent rendering. Salesforce creates one Presentation Page for each PDF page. PDFs also support offline use and email attachments.
From the Presentations setup page, select Upload New Pages, upload the approved files, and continue after validation.
For Immunexis, the admin uploads four HTML5 packages: a brand overview, efficacy graph, patient survey, and risk summary. After validation, Salesforce creates one Presentation Page for each package. A multipage PDF behaves differently. Salesforce creates a separate Presentation Page for each PDF page. The next step adds the product and message context required for reporting and analysis.
Associate Pages with Products and Guidance Messages
Product and guidance-message associations identify the commercial context supported by each page. When a representative presents an associated page, clickstream data can retain the related product and Product Guidance message.
Apply an association only when the approved content supports it. An unbranded disease-state page can remain unassociated, while another page can support one or more products and messages.
Here’s how to apply the associations.
- On the Presentation Pages screen, select Add under Products and Messages.
- Find and select the product, then select the related guidance messages.
- Save your changes.
- Select the pages where the messages apply.
- Select Apply Products and Messages.
For Immunexis, the admin associates the product and approved messages only with the pages that support them.
Each recorded interaction with those pages can now retain the relevant product and message context for reporting.
Name Pages and Mark Required Pages
Give each page a descriptive name so administrators and representatives can identify it in the library, custom presentations, and reports.
Select Mandatory for content to be shown during every presentation session, such as safety information, risk summaries, or disclaimers. It’s important for a representative to display a mandatory page before closing the presentation or submitting the related visit. If an HTML5 page contains several internal slides, every slide becomes required.
For Immunexis, the administrator names the final page Immunexis Risk Summary and marks it mandatory.
The rule is stored on the Presentation Page, so it remains in effect whenever that page is reused.
Finalize Presentation Settings
Presentation settings determine how representatives identify and use the completed deck.
Enter a recognizable name, set the approved activation and deactivation dates, and assign topics that help users filter the library. Then select player options suited to the page design, including navigation gestures, control placement, and feedback position.
For a PDF that representatives can share as an attachment, select Send presentation by email. For approved external content used during remote sessions, provide a public content name and URL.
For Immunexis, the administrator enters the launch-deck name, applies its approved availability window and topics, and chooses player settings that complement the page layout.
Select Done to save the configuration. Activate and distribute the presentation before field users can access it.
Manage the Presentation Library
The Presentations page provides a central view of content across brands and use cases. Admins can review availability and product context, and update settings and content versions. They can also activate, deactivate, or retire presentations.
Version management preserves continuity when approved content changes. Uploading a revised PDF or HTML5 asset creates a new ContentVersion for the underlying file, while the Presentation and Presentation Page records continue to define how it is organized and used.
Clickstream records retain the Presentation Page Content Version and Presentation Version used during an interaction. Historical engagement therefore remains connected with the exact content and presentation version delivered in the field.
What’s Next?
You’ve learned about creating a presentation, adding its product and message context, applying required-page controls, and preparing it for ongoing management.
In the next unit, explore how to distribute presentations through the territory hierarchy, shape their account-specific use through targeting and recommendations, and configure search so representatives can find approved content.