unofficialsf.com Open in urlscan Pro
192.0.78.248  Public Scan

Submitted URL: https://unofficialsf.com/?page_id=20785&preview=true
Effective URL: https://unofficialsf.com/flow-action-and-screen-component-basepacks/
Submission: On February 06 via manual from AU — Scanned from AU

Form analysis 3 forms found in the DOM

<form id="jp-carousel-comment-form">
  <label for="jp-carousel-comment-form-comment-field" class="screen-reader-text">Write a Comment...</label>
  <textarea name="comment" class="jp-carousel-comment-form-field jp-carousel-comment-form-textarea" id="jp-carousel-comment-form-comment-field" placeholder="Write a Comment..."></textarea>
  <div id="jp-carousel-comment-form-submit-and-info-wrapper">
    <div id="jp-carousel-comment-form-commenting-as">
      <fieldset>
        <label for="jp-carousel-comment-form-email-field">Email</label>
        <input type="text" name="email" class="jp-carousel-comment-form-field jp-carousel-comment-form-text-field" id="jp-carousel-comment-form-email-field">
      </fieldset>
      <fieldset>
        <label for="jp-carousel-comment-form-author-field">Name</label>
        <input type="text" name="author" class="jp-carousel-comment-form-field jp-carousel-comment-form-text-field" id="jp-carousel-comment-form-author-field">
      </fieldset>
      <fieldset>
        <label for="jp-carousel-comment-form-url-field">Website</label>
        <input type="text" name="url" class="jp-carousel-comment-form-field jp-carousel-comment-form-text-field" id="jp-carousel-comment-form-url-field">
      </fieldset>
    </div>
    <input type="submit" name="submit" class="jp-carousel-comment-form-button" id="jp-carousel-comment-form-button-submit" value="Post Comment">
  </div>
</form>

GET https://unofficialsf.com/

<form action="https://unofficialsf.com/" method="get" id="adminbarsearch"><input class="adminbar-input" name="s" id="adminbar-search" type="text" value="" maxlength="150"><label for="adminbar-search" class="screen-reader-text">Search</label><input
    type="submit" class="adminbar-button" value="Search"></form>

<form autocomplete="off" role="search" class="jetpack-instant-search__search-results-search-form">
  <div class="jetpack-instant-search__search-form">
    <div class="jetpack-instant-search__box"><label class="jetpack-instant-search__box-label" for="jetpack-instant-search__box-input-1">
        <div class="jetpack-instant-search__box-gridicon"><svg class="gridicon gridicons-search " focusable="true" height="24" viewBox="0 0 24 24" width="24" xmlns="http://www.w3.org/2000/svg" aria-hidden="false" style="height: 24px; width: 24px;">
            <title>Magnifying Glass</title>
            <g>
              <path d="M21 19l-5.154-5.154C16.574 12.742 17 11.42 17 10c0-3.866-3.134-7-7-7s-7 3.134-7 7 3.134 7 7 7c1.42 0 2.742-.426 3.846-1.154L19 21l2-2zM5 10c0-2.757 2.243-5 5-5s5 2.243 5 5-2.243 5-5 5-5-2.243-5-5z"></path>
            </g>
          </svg></div><input autocomplete="off" id="jetpack-instant-search__box-input-1" class="search-field jetpack-instant-search__box-input" inputmode="search" placeholder="Search…" type="search"><button class="screen-reader-text assistive-text"
          tabindex="-1">Search</button>
      </label></div>
  </div>
</form>

Text Content

 * Home
 * Flow
 * Next Best Action
 * Orchestration
 * Ext. Services
 * Scheduler
 * Surveys
 * Utilities
 * Pages
 * Service Cloud
 * Search
 * Menu




FLOW ACTION AND SCREEN COMPONENT BASEPACKS

These BasePacks are libraries of useful actions and screen components that are
commonly used by developers as building blocks when they build their own 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).

If you already have some of the components in the base packs installed in your
org, you don’t have to worry about collisions because the versions in these base
packs have different names. You don’t have to modify any of your existing
actions or screen components that use the older versions of these components
simply because you’re installing these base packs.




INSTALL


FLOWACTIONSBASEPACK

V 3.12 Managed 1/18/23 29/22 Production Sandbox Metadata Service classes updated
to V57





NOTE: The FlowActionsBasePack is also available on the AppExchange. Due to the
overhead of passing security reviews, the version published on App Exchange
won’t always be the latest version available here at UnofficialSF.com. More
details can be found in this article.



NOTE: if you are installing now and you previously installed Version 2.x,
Version 3 will be installed alongside Version 2. Don’t worry about deleting
Version 2. It will continue to work for older components.



Troubleshoot Installation Issues

View Source


FLOWSCREENCOMPONENTSBASEPACK

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.

Version 3.0.18 1/6/23 Production Sandbox Bug fixes in Field Selector. Now
requires Action Base Pack 3.10





Note: If you get an upgrade error that references FlowTableViewDefinition please
follow the steps in this document.

View Source

--------------------------------------------------------------------------------


REFERENCE

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


DISPLAY ERROR

This component allows the developer to highlight an input in their CPE with an
error condition.

Reference


DUAL LISTBOX

This component surfaces the dual listbox in flow screens. It allows for multiple
selection and returns the selected values either as a comma-separated list or
(more usefully) as a collection of strings that can be looped over.

Reference


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


FLEXCARD

Flexcard is a great way to display collections of records:

Reference


FLOW BANNER

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

Reference


FLOW BUTTON BAR

Flow Button Bar brings a more user-friendly interface, new features like icons
and vertical buttons, and now offers two distinct “modes” of Flow functionality:
Navigation Mode and Selection Mode. It has its own CPE giving much greater
flexibility and control over configuring the component.

Reference


FLOW CHECKBOX

This is useful for any custom property editor. It provides checkbox component
for CPEs that will support a default value of True and will correctly retain the
checkbox status when exiting the CPE.

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


GET FIELD INFORMATION

Get Field Information is a simple action that takes the name of an object (e.g.
‘Contact’) and returns information about all of its fields in a collection,
including name, label, type, required. The data is returned in a collection of a
custom datatype called a FieldDescriptor that can be manipulated declaratively
in Flow.

Reference


ICON PICKER

This component can add a visual icon picker to your Flow Screen and developers
can include it in a Custom Property Editor or other Lightning Web Components. 

Reference


OBJECT AND FIELD PICKER

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

Reference


QUICK CHOICE

Add picklists, radio button groups and visual cards that can use dynamic
defaults, record-type-filtered picklist fields, and string collections.

Reference


SHOW TOAST

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

Reference


TRANSFER METADATA

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

Reference


CONVERT RECORDS TO CSV

This action takes a collection of records and outputs a CSV file. More detail
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"
    }
}

--------------------------------------------------------------------------------

VERSION HISTORY – FLOWACTIONSBASEPACK

V 3.11 Managed 12/29/22 Production Sandbox MetadataUtils function add

V 3.10 Managed 11/20/22 Production Sandbox Misc Fixes

V 3.8 Managed 11/20/22 Production Sandbox more adds to Metadata Service

V 3.7 Managed 11/12/22 Production Sandbox more adds to MetadataService

3.6 Managed 10/31/22 Production Sandbox

V 3.4 Managed 10/29/22 Production Sandbox Added a few missing Flow data entities

V 3.3 Managed 10/21/22 Production Sandbox MetadataService updated with the
latest Flow data model

Version 3.2 Managed 7/21/22 (Production or Dev) – fix in MetadataService to
address test problems with SetupViaFlow
Version 3.2 Managed 7/21/22 (Sandbox)

Version 3.1 Managed 6/20/22 (Production or Dev) – fix to ConvertRecordsToCSV
Version 3.1 Managed 6/20/22 (Sandbox)

Version 3.0.0 Managed 4/14/22 (Production or Dev) – change to ‘usf3’ namespace
Version 3.0.0 Managed 4/14/22 (Sandbox)

Version 2.38 Managed 4/7/22 (Production or Dev) – fixed problematic test class
Version 2.38 Managed 4/7/22 (Sandbox)

Version 2.37 Managed 1/21/22 (Production or Dev) – Removed test class that fails
Version 2.37 Managed 1/21/22 (Sandbox)

Version 2.36 Managed 1/21/22 (Production or Dev) – Added Convert Records to CSV
action, which is used by some components to support exports.
Version 2.36 Managed 1/21/22 (Sandbox)

Version 2.34 Managed 12/30/21 (Production or Dev) – Support Multiselect Field
picking in pickObjectAndField; some security improvements to metadata transers
Version 2.34 Managed 12/30/21 (Sandbox)

Version 2.33 Managed 10/11/21 (Production or Dev) – update to 53.0
Version 2.33 Managed 10/11/21 (Sandbox)

sion 2.32 Managed 8/13/21 (Production or Dev) – getFieldInformation updated to
API 52.0
Version 2.32 Managed 8/13/21 (Sandbox)

Version 2.32 Managed 8/13/21 (Production or Dev) – getFieldInformation updated
to API 52.0
Version 2.32 Managed 8/13/21 (Sandbox)

Version 2.29 Managed 7/22/21 (Production or Dev) – Fix for bug that prevents
metadata deployment to production orgs
Version 2.29 Managed (Sandbox)

Version 2.28 Managed 7/21/21 (Production or Dev) – Fixes some problems in
Formula Evaluator
Version 2.28 Managed 7/15/21 (Sandbox)

VERSION HISTORY – FLOWSCREENCOMPONENTSBASEPACK

Version 3.0.17 12/28/22 Production Sandbox Minor tweaks. Now requires Action
Base Pack 3.10

Version 3.0.16 12/1/22 Production Sandbox Added rich text support to Flow Banner

Version 3.0.14 9/18/22 Production Sandbox FlexCard now has automatic scroll bars

Version 3.0.15 10/29/22 Production Sandbox lwc modal (bugs reported
https://trailhead.salesforce.com/trailblazer-community/feed/0D54S00000JeWml)

Version 3.0.14 9/18/22 Production Sandbox FlexCard now has automatic scroll bars

Version 3.0.13 Production Sandbox Bug fix to Quick Choice card mode. More.

Version 3.0.12 Production Sandbox Visual improvements to Quick Choice card mode.
More.

ersion 3.0.11 Unmanaged 8/14/22 (Production or Dev) fix for Dual List Box.
Requires 3.0.0+ FlowActionsBasePack
Version 3.0.11 Unmanaged 8/14/22 (Sandbox)

Version 3.0.10 Unmanaged 7/21/22 (Production or Dev) misc fixes. Requires 3.0.0+
FlowActionsBasePack
Version 3.0.10 Unmanaged 7/21/22 (Sandbox)

Version 3.0.7 Unmanaged 6/1/22 (Production or Dev) misc fixes. Requires 3.0.0
FlowActionsBasePack
Version 3.0.7 Unmanaged 6/1/22 (Sandbox)

Version 3.0.6 Unmanaged 4/14/22 (Production or Dev) misc fixes. Requires 3.0.0
FlowActionsBasePack
Version 3.0.6 Unmanaged 4/14/22 (Sandbox)

Version 2.7.8 Unmanaged 4/7/22 (Sandbox)

Version 2.7.7 Unmanaged 3/10/22 (Production or Dev) fixed bug in Object Picker
that was causing values entered by the user to get forgotten, improved sorting
library
Version 2.7.7 Unmanaged 3/10/22 (Sandbox)

Changes since 7/21/21 (Version 2.5.1)

 * fsc_flowCombobox fix for error introduced in API 52.0 for selecting a field
   from an object variable in a CPE (v2.5.5)
 * Added support for Quote and QuoteLineItem to Quick Choice and Dual List Box
 * New Static List attribute type for Quick Choice
 * fsc_lwcModal utility for CPE developers
 * Quick Choice CPE will now show the current version #
 * Fixed default value issue in Quick Choice

Version 2.5.4 Unmanaged 8/13/21 (Production or Dev)
Version 2.5.4 Unmanaged 8/13/21 (Sandbox)

Version 2.5.3 Unmanaged 8/10/21 (Production or Dev) – fixes: Quick Choice CPE
gets static list builder, lwcModal utility for CPE added to package NOTE will
not install currently

Version 2.5.3 Unmanaged 8/10/21 (Sandbox)


The views of Alex Edelstein and any other Salesforce employees participating on
this site are their own and not those of Salesforce.
Popular
Recent
Comments
Tags
Popular
 * Create a Next Best Action Employee App – Part 2June 30, 2020 - 3:20 pm
 * Create A Next Best Action Employee App- Part 1June 30, 2020 - 3:19 pm
 * Adding Lightning Web Components to Flow ScreensOctober 21, 2019 - 7:45 am
 * The Top 10 Things You Want to Know About the New Flow B...February 11, 2019 -
   5:36 pm
 * Salesforce Einstein Next Best Action “Getting Started”...February 3, 2019 -
   2:34 am
 * Send Rich Email (Send HTML Email Action)September 12, 2019 - 4:15 pm
 * QuickChoice – Improved Picklists and Radio Buttons...December 25, 2019 -
   12:57 pm
 * Collection Processors for Flow (Sort, Filter, Find, Join,...December 17, 2019
   - 12:18 am
 * Send Richer Email with the ‘Send Better Email’...August 11, 2020 - 10:23 am

Recent
 * Create a Next Best Action Employee App – Part 2June 30, 2020 - 3:20 pm
 * Create A Next Best Action Employee App- Part 1June 30, 2020 - 3:19 pm
 * Adding Lightning Web Components to Flow ScreensOctober 21, 2019 - 7:45 am
 * The Top 10 Things You Want to Know About the New Flow B...February 11, 2019 -
   5:36 pm
 * Salesforce Einstein Next Best Action “Getting Started”...February 3, 2019 -
   2:34 am
 * Developer Blog: LWC Best Practices for Screen FlowsFebruary 2, 2023 - 7:38 am
 * Extended Working Hours for Privileged CustomersJanuary 30, 2023 - 7:59 am
 * From Kevin Luptowski: Tips and Use Cases for Running Screen...January 19,
   2023 - 5:52 pm
 * Working with Remote Site SettingsJanuary 12, 2023 - 7:49 pm

Comments
 * […] So I turned to Google for a solution and sure...January 28, 2023 - 6:02
   pm by Automate Exchange Rates with HTTP Callout —
 * […] மேல் கட்டமைக்கப்பட்டுள்ளன...January 21, 2023 - 1:14 am by வணிக
   நிர்வாகியின் வழிகாட்டி, பகுதி 2 - varanasi live
 * […] previous blog post
   (https://unofficialsf.com/running-screen-flows-in-slack/)...January 19, 2023
   - 5:52 pm by From Kevin Luptowski: Tips and Use Cases for Running Screen
   Flows in Slack – UnofficialSF
 * […] Actions are fully customizable and built on top...January 19, 2023 - 5:39
   pm by Salesforce winter 2023 release: The business executive’s guide, part 2
   - NewsAltitude

Tags
Apex apex action customer ratings customisation Design Dynamic duration external
services feedback management Flow Flow Actions Flow Orchestrator Flow Screen
Component food fun google maps on location screen Invocable Actions JavaScript
Lightning Flow Lightning Out Lightning Scheduler location selection LWC Next
Best Action Omni-Channel Omni-Channel Supervisor ratings Salesforce Salesforce
Development Salesforce Feedback Salesforce Flow Salesforce Lightning Salesforce
Scheduler Scheduler service territory selection Sfdx shift rostering shifts
slack Spring 21 Summer 21 Surveys Topic Hierarchy Virtual Winter 22 Work Type
Group
Scroll to top

 

Loading Comments...

 

Write a Comment...
Email Name Website


Skip to toolbar
 * About WordPress
    * WordPress.org
    * Documentation
    * Support
    * Feedback

 * Log In
 * Helpie Settings
 * AMP
    * View AMP version

 * Search


SEARCH RESULTS

Magnifying Glass
Search
Close search results
Sort by:
Relevance•Newest•Oldest


NO RESULTS FOUND


FILTER OPTIONS


Close Search