Review the considerations and limitations for custom Lightning types.
Required Editions
| Available in: Lightning Experience |
| Available in: Enterprise, Performance, Unlimited, and Developer Editions. |
Considerations
- Unless you select a custom component for a custom Lightning type, Enhanced Chat v2 uses the Agentforce (Lightning Experience) component by default.
Limitations
- When creating an Apex-based custom Lightning type, the list of available Apex classes doesn’t include file-based Apex classes. If you can’t find your class in the list, you can manually enter its fully qualified name.
- You can’t configure specific properties, such as minimum, maximum, multipleOf, minLength, and maxLength, in the schema.json created via Metadata API in the Setup UI. However, updating the object-based custom Lightning type in the Setup UI preserves these values.
- You can’t configure the title property created via Metadata API for schema.json in the Setup UI. Updating the object-based custom Lightning type in the Setup UI sets the title value to the Field Name.
- You can’t configure property-level component overrides or layouts created via Metadata API in editor.json in the Setup UI. Updating the editor configuration in the Setup UI removes these configurations.
- If you use a custom label for properties such as title or description via Metadata API, updating the object-based custom Lightning type in the Setup UI overwrites the label reference with the static text displayed in the UI.
- When previewing custom Lightning types (CLTs) in Agentforce Builder, these
considerations apply.
- Preview for CLTs is supported for Agentforce Employee agents and Agentforce Service agents. Service agents must have an Enhanced Chat v2 connection, and you must select the Enhanced Chat v2 connection from the Preview Mode dropdown in the Agentforce Builder Preview panel.
- To preview CLTs for an agent, start a preview conversation in live test mode.
- Agents can be in draft or committed states.