You are here:
Build Rich Screens with Custom Screen Components
Use screen components to unlock the look, feel, and functionality of your flow screens.
Required Editions
| View supported editions. |
You can install screen components from AppExchange or have a developer build Lightning components for you. With custom screen components, you can do these actions and more:
- Customize the navigation in your flow
- Display data in a table
- Use a branded header instead of the default flow header
Note Before you add custom screen components to a flow screen, make sure that:
- The flow’s type is Screen Flow.
- Users can run the flow only in Lightning runtime. For example, don’t distribute the flow using a Visualforce component.
When you have the appropriate screen component in your org, add it to your flow screen.
- In Flow Builder, open an existing screen, or add a Screen element to the canvas.
-
From the list of screen components, drag the appropriate component onto the screen
canvas.
If a screen component is built from a Lightning component, it has a lightning bolt icon next to its name. If the custom screen component includes an API name and label, the label is shown on the screen canvas.
- Use values from the flow to set the screen component’s attributes.
-
To use values from the screen component as resources later in the flow, start typing
the API name of the screen component.
We automatically store all the attribute values in a variable with the same name as the screen component’s API name.
To store the action’s output values manually, select Manually assign variables (advanced).
Tip
By default, screen components that run on Lightning
runtime version 58 and prior have no memory. If a user enters a value, and then does one
of the following, the value is lost.
- Navigates to another screen and returns to the component’s screen.
- Pauses the flow then resumes it.
- Navigates to the next screen and triggers an input validation error.
Setting the attribute enables a flow to remember the value. The flow stores the value automatically. If you store values manually, store the attribute’s output value in a variable.
Did this article solve your issue?
Let us know so we can improve!
