Considerations and Limitations for Custom Lightning Types

Review the considerations and limitations for custom Lightning types.

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.

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.
Testing or previewing custom Lightning types for Agentforce Service agent in Agentforce Builder isn’t supported. To test and preview custom Lightning types for Agentforce Service agent, go to the Embedded Service Deployments Settings page and click Test Enhanced Web Chat.
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.

Did this article solve your issue?

Let us know so we can improve!