You can now pass in a number of pixels (default is 320) in the attribute “style_width” to set the width of the control.

Problem preventing Get Layouts action from working in non-debug environments have been fixed.

“ObjectAndFieldName” attribute has been removed to simplify the interface, which still has an Object Name and a Field Name for use specifying picklist fields to use as choice inputs. (Note that you may need to remove the quick choice component from existing flows in order to install this version. We’ll try not to mess with the interface, moving forward.)

Learn more about QuickChoice.

Install Latest Version

Salesforce Spring ’20 Release brings us a powerful enhancement – Flow Builder before-save updates.

In the following article, Gidi Abramovich demonstrates how to use this feature to update a Region field.

Check It Out

Chris Van Der Merwe has launched a promising new Flow Blog this week, starting out with an article explaining how to mod Eric Smith’s Datatable component for orgs where permissions limitations prevent the standard version from working. He has followed it up with a streamlined Visual Picklist component that automatically transitions to the next page as soon as the button is clicked.

For the latest on the Datatable component, please go here: Datatable – Lightning Web Component for Flow Screens – UnofficialSF

Chris Van Der Merwe has written a nice post on how he customized the datatableFSC component to handle a single custom object. His post gives easy to follow step-by-step instructions that a non-developer can easily follow to create a version of the datatable componet to support any object of their choice.

The Email Alerts that are available in Workflow Rules are limited in functionality. I remember thinking this as a customer of Salesforce more than 15 years ago. Salesforce isn’t investing in Email Alerts because it wants to transition to more modern technology. In the meantime, here’s an approach for getting massively customizable email into your Workflow Rules.

In this example, we’ll assume that you have a Workflow Rule that runs on Contact every time the email address of the contact changes. You want to send certain things to certain recipients, but Email Alerts don’t give you enough flexibility.

With Process Builder and Flow you can get the flexibility you need, but you’ll need to trigger the process by updating a special field.

1. Add a text field to your object. Suppose you are sending emails about something affecting Contact. In this case, add a boolean field called “TriggerEmailSend” and set it by default to False. Modify your Workflow Rule to set this field to true using an Update Field
2. Create a Flow that uses the Send Rich Email action. Use the “Autolaunched” Flow Type. Configure the flow with input variables to capture any information you’re going to need in your email. For example, if you want your email to have a link that brings the user to a record, you’ll need a recordId input variable. Activate this flow.
3. Create a Process Builder trigger that runs whenever the TriggerEmailSend field is changed to True on the Contact object. Have it call the Flow you’ve created, passing it the recordId of the Contact that triggered the change.
4. The Flow that you created in step 2 above should also modify the contact using an Update Record element with an Assignment element to set the TriggerEmailSend back to False.

This process will get easier later this year, when Flow gets the ability to trigger on all record changes. That will eliminate the Process Builder step.

Note that you may not need step 1 at all. You can create a Process Builder process that triggers on the same field that triggered your workflow rule.