Minimize the Window When a Utility Bar Flow is Finished – Evan Ponter

By Evan Ponter

Flows are a great way to collect information from your users in a guided fashion. They can be added to the utility bar of an app for easy access no matter where the user navigates. But the normal behavior for flows in utility bars is an endless loop – when the flow ends, the first screen is shown again. This doesn’t always make sense for each flow you are distributing. Wouldn’t it be nice if you could have the flow window minimized when the flow ends?

Introducing the Minimize Utility Item component. With the addition of this action element to the end of your flow logic, you can tell the flow to minimize its window. There are no inputs or outputs specified for this element – just connect it within your flow canvas and the flow’s window will be minimized at that point in the flow interview execution. As an added bonus, components on the current page will be refreshed with any info that was manipulated in your flow.

If you distribute your flow in multiple locations, only the flow in the utility bar will see the effect of this element. A flow that is launched from a record action will behave as-if this Minimize Utility Item element were not in the flow at all.

Getting Your Users Attention with Custom Notifications

Andy Fawcett explains how to use Notification Builder to add custom notifications with Process Builder and flows. He includes an ingenious method to use custom metadata types to get the notification ID for a subflow.

Getting Your Users Attention with Custom Notifications

Assignment Plug-in by GearsDesign

Easily send records back through Assignment Rules using Process Builder or Flow. Compatible with Leads or Cases, this simple plug-in gives Administrators flexible options to build out a solution that works with their existing configuration. This Plug-In will work in Classic or Lightning

Click here to access this Appexchange solution

Adding Validation Functions to Flow Screen Components

This feature shipped quietly back in Winter ’19.

The official docs are somewhat hidden away here. This blog post is mainly an effort to raise the profile of this feature a bit.

If you wrap a base component that has a “required” attribute, even if you expose the attribute, Flow will not know to check unless you implement a validate function as described here.

Flow Screen Component: Dependent Picklists with RecordType and MultiSelect Picklist support by Narender Singh

Narender Singh created a flow screen component for a dependent picklist tha supports picklist value selection based on the record type.

https://forcepanda.wordpress.com/2019/06/11/flow-screen-component-dependent-picklists-with-recordtype-and-multiselect-picklist-support/

How to Declaratively Handle with Flow When Files are Shared to Records by DOUGLAS C. AYERS

Douglas Ayers and Michelle Hansen developed an Apex trigger that could know when a file was being shared to a record and then call an autolaunched flow where the business logic could be implemented declaratively.

How To: Use Collection Operators in Assignment Element

This video was done in 2018, but it’s still one of the best demonstrations of how to make use of the Collection Operators in the Assignment element.

Summer 19 Release Readiness Video

Templates, Apex-defined Types, and more. Check it out.

Mass Action Scheduler 2.2 by Doug Ayers

Declaratively schedule Process Builder, Flows, Quick Actions, Email Alerts, Workflow Rules, or Apex to process records from Reports, List Views, SOQL, or Apex.

Click here for release notes, source code and install package

How to do more with Custom Permissions in Salesforce Lightning Flows by Scott McClung

Apex Action to make Custom Permissions even more useful in flows.

  • Detailed write up available here
  • To install the package click here