The SDK rendering configuration comes with sensible defaults so you can get started quickly. Let's see what those defaults are and how to configure them to your liking.
The SDK will render the Flows view in the configured container as a list.
Integrations that have been configured will be shown in a separate tab.
The search function supports fuzzy search and will return results that match Flow names, tags and third party app names such as Slack and Facebook.
The search function on the integrations tab supports fuzzy search and will return results that match integration names as well as tags.
Users can rename an integration from the list view by hovering over the name and clicking on the edit icon. Press 'Enter' to save the new name, or 'Escape' to cancel.
We require the consumer app to provide a
renderMode parameter when initializing views. This parameter controls where and how the Flow form will load when attempting to set up an integration.
Rendering in a modal
In this mode, the SDK will open a custom modal to show the Flow setup.
In this mode, the SDK will swap out the Flows view with the Flow setup form in the same container.
Rendering in a detached state
This mode is used when the Flow setup form does not exist in the same context and page as the Flows view. You can use this to render the form in a container in a different DOM hierarchy or a new page.