Posts

July Flow Update

Disclaimer: Content and opinions are my own and not the views of my employer. The software discussed here is not official Salesforce software.


Some nice Flow-related posts from the community

Terrence Chiu with a great example that incorporates both the lightning:datatable component and record:editForm.

Part 1

Part 2

Rich Engelhard has a two-part post that also incorporates datatable and goes into fabulous detail.

Part 1

Part 2

More enhancements to the Lookup Component

Eric Smith has added “default” functionality: You can enter a default value for the input field (I2_Display Which Field). When provided, it will override any WhereClause and display the default value as Placeholder text in the input field. You will still need to select the drop-down then select the single value that is displayed. If you start to overtype the input field, the default value will be cleared and the WhereClause (if provided) will be reset and the field will act like a normal filtered lookup with search. Install the updated version here.

Adding Flow Screen Components to a Screen

A growing set of powerful yet easy-to-use screen components are available to Flow users. These can be installed today, although easier installation methods are on the horizon.

I wanted to provide a little documentation for how screen components are added to screens. Once your org is updated to Spring ’18 or later, you’ll find a new Lightning Components choice at the bottom of your list of screen controls in Cloud Flow Designer:


Simply drag the control over to the right and drop it where you want it to go in your screen.

When you click on a Lightning Component screen element on the right, you can give it a title and then you need to select the component you want to use:


Read the documentation for your component to determine which inputs and outputs you should hook up.