![]() ![]() These conditions can reference anything in the flow, including other components on the same screen. When you add conditional visibility to a component, the flow displays the component only when the conditions you specify are present. Like Lightning page components, flow screen components support conditional visibility. This screen is so aesthetically pleasing, you should call yourself Michelangeflow! To see your newly arranged screens in action, save the flow and click Run. Drag the CallbackTimes Checkbox Group component to the second section’s third column.Drag the Case Reason Record Field component to the second section’s second column.Drag the ScreenReviewer Lookup component to the second section’s first column.The second section has three columns now. In the Section sidebar, click +Add Column twice.Drag another Section from the Components sidebar to the screen canvas, below the first Section component.Drag the ScreenPriority Radio Buttons component to the second column.Drag the PointOfContact Data Table component to the first column.Your screen canvas should look like this. Drag the CloseCase Toggle component to the second column, below ScreenSubject.Drag the ScreenSubject Text component to the second column.Drag the ScreenDescription Long Text Area component to the first column, below SayThisText.Drop the component into the first column when it’s highlighted. ![]() Green highlighting shows which section is active as you move over the canvas. Drag the SayThisText Display Text component to the first Empty column.In the Section sidebar, click +Add Column.Drag Section from the Components sidebar to the top of the screen canvas.In the Section component, you define the number of columns and the relative width of each column.Īdd Section components to your screens to use that extra space. The Section component splits a flow screen into multiple columns, allowing you to position components side by side and make use of that horizontal white space. How can we use the screen space more efficiently? Plus, the second screen has quite a few questions, which take up a lot of vertical space. Now the flow screen has a lot of unused white space. Organize Components into Rows and Columnsįlo embedded the Create Case for Contact flow in the wider column of a contact Lightning page. For more information, check out Prepare Your Org for Paused Flow Interviews in Salesforce Help. Pause lets users freeze their progress in a flow, saving the flow to resume later. The Configure Footer section has settings for the Pause button too, but it doesn’t appear unless it’s enabled in org-wide settings. When the flow runs the File Upload screen, the Finish button has the clearer label Restart, and the Previous button is hidden. Now when the flow runs the Questions screen, the Next button tells the user exactly what happens when they click it: the flow creates a case. For Previous Button, select Hide Previous.For Next or Finish Button Label, enter Restart.In the File Upload Screen element, make sure no components are selected in the screen canvas.For Next or Finish Button Label, enter Create Case.For Next or Finish Button, select Use a custom label.In the Screen Properties sidebar, click Configure Footer.In the Questions element, make sure no components are selected in the screen canvas.Let’s customize the buttons on the Questions and File Upload screens, and hide that potentially hazardous Previous button on the File Upload screen. Remove unneeded buttons and give each button a label that describes what happens when a user clicks the button. It’s best practice to make your flows as transparent and foolproof as possible. When the user clicks Next to proceed, the flow runs the Create Case element a second time (which we don’t want)! If a user clicks the Previous button, they return to the previous screen: Questions. After some troubleshooting and investigation, Flo discovers that the problem occurs when an agent clicks the Previous button on the final screen. Sometimes they generate two new cases instead of one. ![]() When they click Finish on the last screen, the flow unexpectedly restarts from the beginning, and they don’t know what to do. Pyroclastic’s support agents are having some trouble when they run the Create Case for Contact flow. Let’s unlock your screens’ full flowtential! Set a Screen’s Footer Buttons We can make it better, stronger, faster… Or, at the very least, we can make it tidier, easier to use, and mindful of your data requirements. In this module, you built a flow that asks support agents a lot of questions and then creates a case. 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. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |