Entries by Alex Edelstein

Adding Lightning Web Components to Flow Screens

Note! This is a preview of Winter ’20 Functionality For the last two years, Flow creators have been able to add lightning component to Flow Screens. This has powerfully extended the capability of screens. We’ve had a great time creating reusable components as a community, and many of those components are available for use to […]

Flow Action: Get Picklist Values

In my spare time I’m experimentally rebuilding Approval Processes on top of Flow and I recently had a need for a way in Flow to retrieve a set of picklist values that I could then work with. So I built a simple Flow Action to enable all flow designers to do this without code. It’s […]

Scaling to Thousands of Screens with Lightning Flow

In the common diagnostic use case, you have a tree structure of information and you work your way through the tree, gathering information and using it to determine the next diagnostic question. This is useful for important and distinctive use cases like troubleshooting and coming up with a good offer. Here’s an example: Now, you […]

Hosting Components on UnofficialSF

When we learn about a good component, we seek to: create a page for it on unofficialsf. This can either be a Post or a Page. make sure the install instructions on that page provide links to unmanaged and managed packages. Managed packages can be important if there are collisions between support files. For example, […]

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 […]