generating-custom-lightning-type

To create custom lightning types for Einstein Agent, define a JSON Schema-based type definition and validate it against the CLT metaschema to enforce structured inputs and outputs. This process ensures consistent data contracts for Lightning Platform integrations.

Custom lightning type JSON schemas must enforce root and nested object constraints, specific array handling rules, and allowed primitive types. Validating against the CLT metaschema prevents invalid shapes and ensures deployment compatibility for Einstein Agent actions.

Configuring editor and renderer behavior for custom lightning types involves defining specific editor and renderer configurations within the CLT metadata. This workflow guides correct UI flows and ensures consistent structured data rendering across Lightning Platform integrations.

Custom lightning type deployment fails when the JSON Schema definition violates CLT metaschema rules, such as incorrect root object constraints or invalid array handling. Troubleshooting validates the schema structure and editor configurations to resolve the deployment errors.

Structured inputs and outputs for Einstein Agent actions are needed when you require consistent data contracts and specific UI flows on the Lightning Platform. Defining custom lightning types enforces these structured data shapes using JSON Schema-based type definitions.