Expanded presentation search versus Data 360 smart content search
Key Takeaway
To let users find presentations by linked products, key messages, or page properties, use expanded presentation search: a record-triggered flow fills a custom text field on Presentation Page Product, and you select that field in Presentation Settings. Its required editions don't include Data 360. Smart content search finds presentations by meaning, but it needs Data 360 in the same org as Life Sciences Cloud and isn't supported in a Data 360 companion org.
Field users find approved presentations for interactions with healthcare professionals (HCPs) in the content library. They open the content library from the Intelligent Content tab in Life Sciences Customer Engagement. By default, they search for presentations there by keyword. Two features extend that search beyond presentation names. Expanded presentation search uses a flow to fill a custom text field, so users can match on page properties, linked products, and key messages. Smart content search uses Data 360 to index the content of the presentations, so users can match on meaning rather than exact words.
Expanded presentation search
Expanded presentation search works on record data. You create a custom text field on the Presentation Page Product object. A record-triggered flow fills that field with joined values such as page name, product name, product message, and product ID. Users can then search by page properties, linked products, and key messages.
You need a flow instead of a formula field because the product field on Presentation Page Product records is polymorphic. The related record can come from either the Product object or the Life Science Marketable Product object. Polymorphic fields can't be used directly in formula fields.
The flow runs when a Presentation Page Product record is created or updated. So when those joined values change, the flow refreshes the custom field, and search results keep returning the correct presentations.
Dana manages content for a cardiology brand called Veltrana. A presentation named "Q3 Cardiology Update" has a page named "Dosing Guide". A new Presentation Page Product record links that page to Veltrana. The flow runs on the create and writes the page name, product name, product message, and product ID into the custom field, for example "Dosing Guide Veltrana Once-daily dosing 01t5g000002AbCd". A field rep who searches for "Veltrana" in the content library now finds "Q3 Cardiology Update", even though the product name isn't in the presentation name.