Input components are like object fields in another important way: They share a lot of the same data types. To save data beyond the end of the flow run, you need a data element, such as Create Records or Update Records. However, screen flows hold the data only until the flow ends. Think of input components like fields on a Salesforce object: They allow users to input data, and they hold that input. Of these three components, input components are used the most. We talk about Record Field components in a later unit. Record Fields also receive input from users, but store that input in a record variable.They hold that input to use later in the flow. Input Components receive input from users.Display Components only display information.Screen components come in many types, but they fit into three broad categories. To present multiple pages of questions and instructions to users, you use multiple Screen elements. When the user clicks Next, the flow continues down its path. When a flow runs a Screen element, the flow remains on that element and waits for the user. Even if the flow is embedded in just a small part of your Salesforce window, it’s still called a screen. It doesn’t have to take up the user’s whole monitor screen. Each page is defined by a single Screen element on the flow canvas. Within the Screen element, you chose screen components to collect user input, and you arranged them on the screen canvas.Ī screen is a page that the user sees when the flow runs. Of all the element types, the Screen element is the only one that users see when the flow runs. In the screen flow, you used a Screen element. If you completed the Flow Builder Logic badge, you created a screen flow for setting a shipping address. When we talk about screen flows, we also talk about Screen elements, screen components, and screens. By presenting them what they need, when they need it, and using their input to guide them and automate their tasks, you save your users valuable time and mental energy. With all this power, screen flows position you as a superhero to your users. You can embed it on a Lightning page, or kick it off with the click of a button, or dock it at the bottom of any Salesforce app, or expose it externally on Experience Cloud pages. Plus, you choose how to show a screen to your users. Based on the user’s answers, a screen flow can update data, send out communications, and show more questions or information. With screen flows, Salesforce interacts with your users, asking questions and presenting information. It’s people that make decisions and take action, so sometimes people need to drive how your automation runs. People, not programs, are the heart, soul, and mind of your organization. The Power of InteractionĪutomation is amazing, but sometimes you need automation to be a little less… automatic. If you aren’t familiar with these concepts or need a refresher, see the Data and Actions in Flows badge and the Flow Builder Logic badge. This badge assumes that you know how to create a flow with variables, inputs, and data elements, such as Get Records. Follow this recommended sequence of badges to build strong process automation skills and become a Flow Builder expert. From start to finish, the Build Flows with Flow Builder trail guides you through learning all about Flow Builder. This badge is one stop along the way to Flow Builder proficiency.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |