-
Customizing Coveo for Salesforce Components
- Common Customizations
- Integrating Coveo Lightning Console Components
-
Customizing the Coveo Lightning Community Components
- Integrating Coveo Components in a Custom Lightning Component for Your Community
- Creating a Search Driven Page in a Salesforce Community
- Creating a Custom Standalone Searchbox for Your Lightning Community
- Using Salesforce Page Variations With Coveo for Salesforce
- Adding Hidden Fields in a Case Creation Component
- Sending Custom Context Information In a Custom Page View Tracker
- Integrating Coveo Classic Components
- Changing the Default Quick View in Coveo for Salesforce
- Changing the Search Result Links for Salesforce Items
- Sending Custom Context Information in Salesforce Lightning
- Displaying Product Pricing in a B2B Search Page
Customizing the Coveo Lightning Community Components
-
Coveo for Salesforce 3.25 (February 2019) The Coveo Community Search component is the Locker compliant version of the Coveo Search component.
-
Coveo for Salesforce 3.29 (March 2019) The Coveo Case Deflection Component is the Locker compliant version of the Coveo Case Creation Component.
The Coveo components offer some customizable properties using the Experience Builder.
In the following screenshot, you can see that when the Coveo component is selected, the property editor on the right lights up with a set of options available to use.
Name
This is the name of the Visualforce component that’s created.
By default, its value is communitySearchCoveo for CommunitySearch components, and communityCaseDeflectionCoveo for CaseDeflection components.
When you create a Coveo-powered search page, the HTML content of the page is saved in a Visualforce component. To find the component of the same name, in your Salesforce instance, go to Setup > Develop > Visualforce Components.
-
If you have two different Coveo Search Lightning components on two different community pages, and both have the same Name property, then they will both load the same HTML content.
-
If you don’t set the Search Hub property, then the origin level 1 or the
Page/Hubfor your usage analytics reports will be the name of the search page.
Debug
This Boolean value tells the Lightning component to load the debug version of the different resources.
By default, this option is deselected.
In practice, this means:
-
When deselected, this loads the
*.min(minified) versions of all JavaScript resources. The box shouldn’t be selected in production mode. -
When selected, this will load the non minified versions of all JavaScript resources. This can be useful during development or for debugging purposes.
Search Hub
This sets the analytics search hub to a different value then the default value.
This value is passed in the Origin 1 (Page/Hub) Usage Analytics dimension (see Usage Analytics Dimensions).
If not set, the value of the search hub will be that of the Name property of the Lightning component.