Config Wizard Overview

The integrations you build are meant to be reusable and deployable across your heterogeneous customer base. To achieve this, you need to provide customers with a mechanism to configure integrations for their specific environments.

When customers configure and activate an instance of your integration, they follow a configuration wizard where they authenticate with third-party apps and provide any additional information required for the integration to function. Some integrations have simple configuration wizards that only require third-party authentication, while others may involve multiple configuration pages with dynamically generated dropdown menus, toggles, text fields, and other input types.

Hosted and headless configuration

You can present configuration to your customers in one of two ways:

• Hosted configuration: Prismatic renders a config wizard from the config pages and config variables you define. Your app embeds it with the embedded SDK, and you style it with theming. Hosted configuration works with both low-code and code-native integrations.
• Headless configuration: Your app renders the configuration experience with its own UI components, using Solis, Prismatic's custom UI SDK. You define the configuration's schema, server functions, and an init function in a code-native integration, and Prismatic handles validation, storage, and instance lifecycle. See Headless configuration.

The rest of this section covers hosted configuration.