Adding the User Actions Component to the Lightning Insight Panel

Lightning Experience

Coveo for Salesforce 3.38 (August 2019)

Contact us to enable this feature.

The UserActions component allows your agents to analyze all the user’s recent activities, such as User Query, Clicked Document, or Page View. It records up to 2,000 events. You can add this component to your Lightning Insight Panel.

  1. Access the Lightning Insight Panel.

  2. Access the Edit mode of the Lightning Insight Panel.

  3. Access the Code View tab.

  4. Insert the following code just before the <div class="coveo-tab-section"> element:

    <div class="CoveoUserActions"></div>
    • Ensure that you do not insert the code in the template or in the coveo-main-section.
    • The Start Date is displayed in the language of your browser.

Configure the UserActions Component for Specific Salesforce Object Types

Coveo for Salesforce 3.46 (February 2020)

By default, the UserActions component shows actions performed by the contact who created the current case. However, you can also use the UserActions component on other Salesforce object types. Depending on which record page you are using, you must configure the Insight Panel to use a different field to retrieve the user e-mail address.

  1. Access the Advanced Configuration mode of the Lightning Insight Panel.

  2. Locate User Actions email fields, and then set the field that contains the user e-mail address.

    Suppose you are integrating the Insight Panel in the Contact record page. To display the current contact user actions, you would set User Actions email fields to Email.

Validate the UserActions Component Configuration

Coveo for Salesforce 3.46 (February 2020)

When the UserActions component is configured correctly, the User Actions button appears in the Insight Panel.

User Actions button in the Insight Panel

If the User Actions button is not visible, please verify the field specified in User Actions email fields. It should:

  • Exist on the Salesforce object type and be referenced by its API name.

  • Have a value on the current record.

  • Be visible to the user opening the current record page.

Recommended Articles