Loading
Salesforce now sends email only from verified domains. Read More
Table of Contents
Select Filters

          No results
          No results
          Here are some search tips

          Check the spelling of your keywords.
          Use more general search terms.
          Select fewer filters to broaden your search.

          Search all of Salesforce Help
          Supported Attributes in Presentations

          Supported Attributes in Presentations

          Using Mustache variables, you can access Life Sciences Customer Engagement attributes dynamically from presentation ZIP files.

          Required Editions

          Available in: Lightning Experience
          Available in: Enterprise and Unlimited Editions with Life Sciences Cloud, Life Sciences Cloud for Customer Engagement Add-on license, and the Life Sciences Customer Engagement managed package.

          Keep these considerations in mind when you reference Salesforce objects and fields as variables in presentation ZIP files.

          • Formula and lookup fields aren’t supported.
          • When you reference a standard Salesforce field, don’t use a prefix or suffix.
          • When you reference a custom field in your Salesforce org, use the custom suffix __c.
          • Format mustache variables in lowercase, for example, accounttype.
          • Users must have access to the Salesforce objects and fields that the presentation template references.

          Account Objects and Fields

          In the JSON structure, account fields appear in the customers node.

          Object Fields Additional Details
          Account All standard and custom Account object fields.
          • accountType returns HCP for Person Accounts and HCO for Business Accounts.
          • recordType returns the name and ID of the account’s record type.
          ContactPointAddress An array of the account’s associated ContactPointAddress records and fields. Only active records are returned.

          Addresses are used in this order.

          • If the preferred address is set on the related provider account territory info, that address is used.
          • If the preferred address isn’t set but a related contact point address record is set to primary, that address is used.
          • If the account has more than one primary address, the primary address that was created most recently is used.
          • If there’s no recent primary address, the address that was created most recently is used.
          HealthcareProviderSpecialties An array of the account’s associated HealthcareProviderSpecialties.

          To access the first specialty in the array, use this code.

          {{#customers}}
          Customer Name: {{name}}
          Specialty: {{healthcareProviderSpecialties.0.name}}
          {{/customers}}

          Returns only active records that are set to primary, ordered by most recently modified.

          ContactPointEmail An array of the account’s associated ContactPointAddress records and fields. Returns only records that are set to primary, ordered by preference rank.
          ContactPointPhone An array of the account’s associated ContactPointPhone records and fields. Returns only records that are set to primary, ordered by preference rank.
          ContactPointSocials An array of the account’s associated ContactPointSocial records and fields. Returned records are ordered by the social platform provider.
          HealthCareProvider All fields on the account’s related HealthcareProviderRecord. None

          Presentation Fields

          Field Description
          id The presentation ID.
          name The presentation name.
          sourceSystemIdentifier A user-provided unique, external identifier for the presentation.
          Pages

          A predefined list of page fields.

          • id
          • sourceSystemIdentifier
          • contentDocumentId
          • name
          • slides:
            • name
          isCustom

          Identifies whether the presentation is a custom presentation created by a field user (true) or not (false). Depending on the variable’s value in the variable, you can apply custom logic.

          See this HTML code example.

          <dl>
              {{#presentations}}
                <dt>Name:  {{name}}</dt>
                <dt>Is Custom:  {{#isCustom}}
                    This is a custom presentation.
                {{/isCustom}}
                {{^isCustom}}
                    This is a standard presentation.
                {{/isCustom}}
               </dt>
            <br>
            {{/presentations}}
          </dl>

          User Objects and Fields

          Object Fields Additional Details
          User All standard and custom fields. None
          UserAdditionalInfo All standard and custom fields on the associated UserAdditionalInfo record. None
          LifeScienceMobileApp On the associated LifeScienceMobileApp record, all fields that contain data about the user’s device, such as location and last download sync date. Available only for the Life Sciences Cloud Mobile app.

          Visit Fields

          Field Description
          id The visit ID.
          accountId The account ID.
          isParent Returns true when the Parent Visit field is blank.
          sourceSystemIdentifier A user-provided unique, external identifier for the visit.

          Top-Level JSON Fields

          These fields are at the top level of the JSON hierarchy, before Life Sciences Customer Engagement data.

          Field Description
          currentMode The current mode of the presentation player.
          currentTerritoryId The current territory ID.
          currentTerritoryName The current territory name.
          emailTemplateId The ID of the email template associated with the current presentation page.
          state The saved state of the presentation on the Life Sciences Cloud Mobile app.
          presentationIndex The presentation index in the presentations array.
          pageIndex The page index in the pages array.
          slideIndex The slide index in the slides array.
           
          Loading
          Salesforce Help | Article