CaseCreation Lightning Component

DELETED - Non-Locker Compliant

The CaseCreation Lightning component allows you to insert a case creation component in your Experience Cloud site.

It takes care of wrapping and including the correct scripts and different resource references needed to do so.

For a tutorial on how to implement a custom Lightning component, see Integrating the Coveo components in a custom Lightning component.


Reference it in your Lightning component as you would for any other Aura component, using the namespace prefix of the Coveo package.

<aura:component implements='forceCommunity:availableForAllPageTypes'>
  <CoveoV2:CaseCreation />

Resources Included With This Component

This component includes the Coveo JavaScript Search Framework, the jQuery(latest 3.x.x version) and Underscore.js (latest 1.x.x version) libraries, and the Coveo for Salesforce specific assets.

Aura Events

This component inherits from the Base Lightning component, and shares all of its aura events (see Aura Events).


This component inherits from the Base Lightning component and supports all its options (see Options).

However, the default values change for the following options:


This option is set to communityCaseCreationCoveo by default when used with this component.

If this Visualforce component doesn’t exist, you will be prompted to create it when inserting the Lightning component in your community.

You can reference another Visualforce search component by changing this option:

<CoveoV2:CaseCreation name="<MY_CUSTOM_CASE_CREATION_NAME>"/>

Where you replace <MY_CUSTOM_CASE_CREATION_NAME> with the name of the Visualforce search component you want to use.


This option is set to false by default when used with this component.

This means users are only proposed solutions once they start typing.