Flow Action and Screen Component BasePacks

These BasePacks are packages with Actions and Screen Components that are commonly used by developers to build additional Actions and Screen Components.

The BasePacks are separated into two packages, one for Actions and one for Screen Components (the reasons they can’t be combined right now are somewhat arcane).

Install

FlowActionsBasePack

Install Version 2.6 Managed 11-28 bug fix to dual list box

View Source

FlowScreenComponentsBasePack

FlowScreenComponentsBasePack is available as an unlocked package.

FlowScreenComponents BasePack requires the presence of FlowActions BasePack (see above), because some of the screen components inside of it rely on Apex classes that are included in FlowActions BasePack. So you’ll need to install FlowActions BasePack first.

Install Version 2.1.0 Unlocked 11-26 (fixes to FlowComboBox; added FlowBanner)

View Source

Reference

When an org has the BasePacks installed, it has access to the following screen components and their support Actions:

Expression Builder

A full expression builder. Generates formula strings for output, and these can be evaluated at runtime by the Evaluate Formula action, which is part of this package.

Reference

Flow Banner

This is useful for any custom property editor. It provides a section banner with optional section help text.

Reference

Flow Combobox

This is essential for any custom property editor. It provides a picklist showing upstream merge fields.

Reference

Formula Builder

A full formula builder. Generates formula strings for output, and these can be evaluated at runtime by the Evaluate Formula action, which is part of this package.

Reference

Object and Field Picker

Provides a drop in component for selecting Objects or Object/Field combinations.

Reference

Show Toast

A simple local action that pops a toast up. Works with Screen flows only.

Learn more.

Transfer Metadata

A screen component that can retrieve or deploy any salesforce metadata.

Learn more.

Quick Choice

Learn more here.

Dual ListBox

Learn more here.

Developer Notes

When creating a project that relies on Screen Components Base Pack, you need to specify both the Actions Base Pack and the ScreenComponents Base Pack as dependencies, as shown below. This is because the Screen Components Base Pack makes use of the Actions Base Pack. Furthermore, the order you list the dependencies is critical. The ActionsBasePack has to come first.

{
    "packageDirectories": [
        {
            "path": "force-app",
            "dependencies": [
                {
                    "package": "FlowActionsBasePack@2.1.0-0"
                },
                {
                    "package": "FlowScreenComponentsBasePack@2.1.0-0"
                }
            ],
            "default": true,
            "package": "testproj",
            "versionName": "ver 0.1",
            "versionNumber": "0.1.0.NEXT"
        }
    ],
    "namespace": "",
    "sfdcLoginUrl": "https://login.salesforce.com",
    "sourceApiVersion": "50.0",
    "packageAliases": {
        "FlowScreenComponentsBasePack@2.1.0-0": "04t5G000004PuTgQAK",
        "testproj": "0Ho5G000000XZNfSAO",
        "FlowActionsBasePack@2.1.0-0": "04t4W000002vXUCQA2"
    }
}

Old Versions – Actions

Install Version 2.2 Managed 11-9. Bug Fix

Install Version 2.1 Managed 10-11

Old Versions – Screen Components

Install Version 2.0.6 Unlocked 11-2 (removed lwcLogger)

Install Version 2.0.5 Unlocked 11-2

Install Version 2.0.4 Unlocked 10-24