Although screen flow is usually visible, it can also be hidden on a Lightning page. When the user looks at the page, the flow will still work, but since it is an Invisible Screen Flow, the user will not notice it. This way, you can take actions based on page views.
There is a standard input component almost for any data type. For instance, text, number, checkbox, date, etc. Although you can configure them to be required fields, there is no way to make the screen components read only.
In this post, you can find a Lightning component that refreshes the page. You can call it as a local action from screen flows in order to refresh the page and see the updated data.
Although there are many global variables that give you useful information, there is no global variable about the user's device. Therefore, it is not possible to build a flow according to the user's device.
REST API can be used to launch autolaunched flows. Although you can perform most of the actions using REST API, in some cases it is a better practice to use an existing flow.
FlowFest V4 took place on February 22nd, 2023. Read this post to see the answer of the fourth challenge.
FlowFest V4 took place on February 22nd, 2023. Read this post to see the answer of the third challenge.
FlowFest V4 took place on February 22nd, 2023. Read this post to see the answer of the second challenge.
FlowFest V4 took place on February 22nd, 2023. Read this post to see the answer of the first challenge.
Launching a screen flow from a related list is a great way to streamline your processes and make your data more accessible to your users. Read this post to learn how to launch a screen flow in a modal for a record in a related list.
Copyright © 2026 | SalesforceTime.com