![]() Flow should be accessible from a record but not expanded automatically: Flow action.Flow is important enough to be expanded automatically: Lightning page.Page Layout > Mobile & Lightning Actions > drag new action to Salesforce Mobile and Lightning Experience Actions sectionĭisplay a Flow on Every Page in Your Salesforce Org Describe use cases for displaying a flow on every page in your app.Ĭreate a Lightning app and add a flow to its utility bar.Once the flow action is created, add it to the appropriate page layouts to make the button available.Create via: Object Manager > Buttons, Links, and Actions > New Action > Action Type: Flow.Flow actions can also be placed in the record’s action menu in the Salesforce app. Once created and added to a page layout, it appears in the associated record’s page-level action menu.Flow Actions are custom actions that renders a flow. ![]() Flow isn’t used often enough to be expanded by default.If flow is added to the Account page, the flow would create a task every time a user loaded an account, resulting in a lot of unnecessary tasks being created. Ex: Flow creates a task before displaying a screen to the user.First element in the flow isn’t a screen.For some use cases, it makes sense to have the user decide when they’re ready to launch a flow:.Just drag and drop a “Flow” element onto the page and select the appropriate flowĪdd a Flow as an Action on a Record Describe use cases for adding a flow as an action.Ĭreate a flow action, and add it to a page layout. For this reason, recommend making the first element in these flows a screen so unintended actions are avoided. If the flow includes elements that come before that screen, the flow performs those actions even if the users is working with a different element. If you add a flow to a Lightning page, every time the page loads, the flow starts and its first screen renders.Flow is important enough to take up screen space.Email application pages: what users see from Lightning for Outlook or Lightning for Gmail.App pages: page that isn’t tied to an object.Record pages: seen when users open a record.Home pages: seen when users navigate home.Several available types of Lightning pages with different use cases:. ![]() If you want to expose a flow as a region of a Salesforce page, the only choice is a Lightning page, built using the Lightning App Builder Only admins with the Manage Flow user permission can run Inactive Flows.ĭisplay a Flow on a Page in Your Salesforce Org Describe use cases for displaying a flow on a Lightning page.Ĭreate a new Lightning page and add a flow to it. Users with the Run Flows system permission can only run Active Flows.To view the permissions assigned to a specific flow, click the down arrow next to a flow, then click “Edit Access.” If “Override default behavior and restrict access to enabled profiles or permission sets” is selected, add the flow itself to profiles/permission sets.Add the “Run Flows” permission to user profiles/permission sets for the org. Users need to be able to actually run flows.Processes, Bots, Apex actions, and the API.For autolaunched flows, the list also includes:. ![]() ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |