Hayes Davis, Co-founder of GradientWorks, has posted a great walkthrough on how to utilize CPEs to help admins get more out of Invoked Actions and Screen Components in Flow.
Check it out!
https://www.gradient.works/blog/custom-property-editors-salesforce-flow
The flow IFrame Lightning Web Component gives an admin the ability to display a website/web page inside of a Flow Screen Component. iFrames can be tricky and they have their pros and cons and in some cases are depreciated by some websites however if you have a use case they can be great. When would you want to use it in a flow? A few ideas I have run into have been things like displaying a Salesforce File via a flow screen or showing data that is in an external system that is not available via a direct integration via external services or some other type of API but a user needs to see the data. Possibilities are endless last year I embedded a virtual career fair inside of an Experience Site that did not have a direct integration with Salesforce allowing us to present data and actions from the Experience Site while also displaying conversations and navigation of the Career Fair.
Gotchas. There are always Gotchas! In order for this to work you will need to add the domain of the site to your trusted sites in your org. The site also needs to allow for iFraming as well. iFrames come with their own inherent security risk so be careful what information you are passing through the iFrame.
I know you are all saying thank you for my rambling of how I have used this and the Gotchas can you just show us how it works already! Let’s take a look
The component has three input variables.
| Property Label | Data Type | Description |
| iFrame Height | Text String | The height in pixels of your iFrame |
| iFrame Width | Text String | The width in pixels of your iFrame |
| URL | Text String | URL of the site you wish to display in your flow |
In my example below I am going to take a file I upload in my first screen create a public url for it and display it via Flow iFrame (to learn more about creating a Content Delivery aka public url for files check out this post from Narender Singh)
Screen 1 user is uploading a new file via fileUploadImproved
Next I am looping the contentDocumentIds (which is only one but I need it as a single text variable to create my Content Delivery)
On my final screen I am displaying the file to the user via Flow iFrame.
Now that I’ve bored you with the technical stuff check it out in real time.
v1.0.1 – 1/19/23 Production Sandbox added frameborder property
Old Versions
Version 1.0 Unmanaged – 5/13/21
Tamar has upgraded this useful action to also output information about the default record type ID and Name.
This version includes two asks from the community. It includes the ability to restrict to only allow a single file for upload and also to set the accepted file formats check it out below.
There is now a new property for Accepted Formats this is a Comma Separated String Variable of accepted file formats for upload for example .pdf,.sxls,.jpg. If left null it will default to accept all file formats.
Also added was a property to control single or multiple file uploads. Allow Multiple Files is a boolean property that when set to True allows for multiple file uploads but when set to False will only allow for a single file upload. (The default is false)
Much like last month’s ‘Flowcast’ – I highlight a bunch of components, articles, and actions featured here on UnofficialSF – check it out in the link below!
The description in the video has links to each of the articles mentioned – enjoy!
I’m very impressed by the amount of great video content that’s getting published about Flow! Just in the last month or two, some vloggers have appeared, seemingly out of nowhere but with deep Salesforce knowledge and great video production chops.
Salesforce Break is publishing Summer 21 videos and created a monster 1 hour session on Flow with Terry’s Tidbits:
SFDC Craftmanship has an unmistakable look and is running a series right now on Flow solutions. Special props for using Unofficialsf’s beloved ‘Bangers’ font!
Adam started posting videos about Flow a month ago. I don’t know where Adam cut his vlogging teeth, but he’s bringin’ ALL of the video production goodness.
Shubham has built up thousands of subscribers and covers more than just Flow. Lately he’s been creating a lot of flow scenarios and enhancement reviews.
Check it out!
A huge thanks to Guillaume Davies and Jerry Poon from Accenture in Sydney Australia for sharing their solution for supporting Picklist Field editing in the Datatable component.
Download the latest version (3.2.0) of Datatable to take advantage of this new and often requested feature. Currently, all available picklist values will be made available for selection when editing the fields. I’m working on fututure enhancements to support picklist value restrictions based on one RecordType per table and to provide an option to include –None– as an available selection.
If you haven’t already, check out these blogs for an Overview of the pilot and a detailed tutorial!
How do I get access to this pilot feature?
PILOT REQUIREMENT:
OTHER CONSIDERATIONS FOR PILOT
Create an optional input variable named inputRecommendation in the invoked flow of data type ‘Record’ and Object type ‘Recommendation’ and mark it as Available for input as shown.
Now this variable holds details of the selected recommendations on the invoked flow that the admin can choose to display a more descriptive text on the screenflow invoked or save for custom reporting purposes. Example below where the category field(custom field) of the inputRecommendation is referenced in the invoked screenflow.
When you open the new recommendation strategy process type, 2 variables will be automatically created in the Manager tab under resources .
1.recordId: This is the variable that will have the value of the contextRecordId. (This is only pilot experience. In beta and beyond, this will be upgraded to support $Record variable that will hold context record
2. outputRecommendations: This is the collection variable that the user has to assign the final recommendation collection to so that the runtime component can display these recommendations (In beta and beyond an output/end node will automatically have access to the final recommendations but the admin will still have the ability to reassign it)
| To create or manage recommendations | Modify All Data or Manage Next Best Action Strategies |
| To open, edit, or create a flow in Flow Builder: | Manage Flow |
| To create and save Lightning pages in the Lightning App Builder: | Customize Application |
| To view Lightning pages in the Lightning App Builder: | View Setup and Configuration |
| To run a recommendation strategy on a Lightning record page: | Run FlowsORFlow User field enabled on the user detail page |
| To create, edit and delete custom report types: | Manage Custom Report Types |
| To view recommendation metrics data: | Modify All Data or Manage Next Best Action Strategies |
Check out the other blogs in the series for
Summer ’21 Pilot Preview: Einstein Next Best Action on Flow! (Blog 1 of 4 series)
Pilot Tutorial -Einstein Next Best Action on Flow(Blog 2 of 4 series)
Pilot FAQs-Einstein Next Best Action on Flow (Blog 4 of 4 series)
Happy Next Best Actioning!!
Bonus: You also get to check out the brand new Sort collection processor element on Flow!
This tutorial will help you create your first Recommendation Strategy on Flow! This is a pilot feature, so contact your Account Executive to get nominated for the pilot. Also if you haven’t already, check out this blog for an overview on the product. As an added bonus, this tutorial also helps you check out the brand new Sort collection processor element on Flow!
You can also download this pdf to follow along:
NBA-on-Flow-Pilot-4You can now create Next Best Action Strategies using the powerful Flow Builder and leverage the power of Salesforce’s mature Automation Platform .
NBA customers will now have a brand new way of creating recommendation strategies on flow builder that is packed with powerful platform features such as Templates, Versioning, Packaging 2.0 support, Sub Strategies, Debugging enhancements and also will be home to low code AI driven Recommendation, OOTB Reporting and analytics , OOTB Integration with Bots, Enhanced Display component with Mobile support and many other cutting edge decisioning builder elements. Planned GA in Spring ‘22 (Safe Harbor applies)
WHAT WILL BE AVAILABLE AS PILOT IN SUMMER ‘21
Try the following pilot tutorial out by creating a sample flow as follows. The use case is to show recommendations on a Case object. For a customer whose CSAT is greater than 50 show Cross-sell and Upsell offers (stored as recommendation records) and for a customer whose CSAT is lower than 50 show some Promotional offers. For every customer irrespective of CSAT, show any other recommendations. Also check out the demo video that explains all the features.
Let’s try and build the following flow and see some recommendations .
2. Create Recommendations :cRecommendations are created the same way as they are with the use of Strategy builder. Recommendations are standard Salesforce records, similar to accounts and contacts, that are processed by strategies and associated with flows (Make sure the flows associated with recommendations are Activated).Read ‘Create Recommendations’ from the documentation here.
3. Load Recommendations using GetRecords :
Use the GetRecords element to load Recommendation records that are evaluated in the strategy when the strategy executes. In the Beta version, you will be able to load records of any object and use a Map element to convert them into Recommendations.
Use the Decision element to conditionally evaluate the flow based on conditions such as in the example shown below: If CSAT is lower than 50, load promotional offers to retain the customer.
4. Sort recommendations( upto 3 levels deep)
With the Collection Sortnew element, you can reorder the recommendations using Recommendation fields up to 3 levels deep. Choose whether you want to sort in an ascending or descending order, and decide how many recommendations to allow through.
5. Save the flow and Activate it.
6. Display the resulting recommendations using the Next Best Action component on record pages
After creating a Recommendation strategy in Flow Builder, choose a page to display your recommendations and run your strategy. You can use a Lightning record page or an app’s Home page by following the steps below.
Lightning Page (Lightning App Builder)
7. Accept/reject a recommendation and launch a flow from the runtime component. The screen flow associated with the recommendation can be launched on Accept /reject as specified in the configuration.
8. Report on accept/reject recommendations from the runtime component
As with Strategy Builder, custom reports can be easily created to report on and track recommendation data and strategy metrics. You can see the monthly total recommendations that a Salesforce org’s strategies served. And you can analyze which recommendations are accepted and rejected, who responds to them, and more.
For the NBA on Flow pilot, the one primary difference is that the the primary objects to report on are Recommendation Response (As opposed to Recommendation Reactions) and Recommendation Strategy Metrics (Same as previous – for monthly metrics)
Refer documentation on
9. And finally .. you can also enable Recommendation Strategy process type to be invoked by the Flow Action endpoint.
The following example illustrates strategy execution via REST API
Thanks for following along this tutorial! Hope you had fun creating your first Recommendation Strategy on Flow! Wondering what more is coming up in subsequent releases?
With Beta/GA (Safe Harbor applies) you will have access to other collection processor and decisioning elements that is currently available in Strategy Builder such as Filter , Map , Branch Selector and Limit Reoffer elements in the new Recommendation Strategy process type in Flow.
In addition to having functional parity with Strategy builder, several other features such as OOTB low code AI recommendations, Scheduled/ Triggered Recommendations , Reporting enhancements, Display component enhancements, OOTB integration with Bots, Support for Mobile display and much more! Check out the blog for an in depth roadmap.
Check out these other blogs in the series for more information
Summer ’21 Pilot Preview: Einstein Next Best Action on Flow! (Blog 1 of 4 series)
Pilot other considerations and requirements: Einstein Next Best Action on Flow(Blog 3 of 4 series)
Pilot FAQs-Einstein Next Best Action on Flow (Blog 4 of 4 series)
Happy Next Best Actioning!!
With the Summer ‘21 Pilot we invite you to try out a brand new way to create Next Best Action Strategies using the Flow Builder that is packed with powerful platform features and many other cutting edge decisioning builder elements.
Planned GA in Spring ‘22 (Safe Harbor applies) Talk to your AE to get nominated for the Pilot and try it out!
This sounds exciting!! How do I try it out??
Since it’s a closed sandbox pilot, reach out to your AE and you can get nominated. Your AE will be able to share the following resources: Also available as blogs right here!
Don’t have an AE ? Do not fret. We will be out with the Beta version soon!! Until then, if you haven’t already get your hands dirty with the Strategy builder and try out building an NBA! Check out the Next Best Action Section of Unofficialsf to learn more.
Need a little more convincing to try out the pilot ?
Check out what’s coming up in Beta/GA in the next few releases with NBA on Flow!!!
Happy Next Best Actioning!!
Check out the other 3 posts in the series for a tutorial demo video , FAQs and more
Pilot Tutorial -Einstein Next Best Action on Flow(Blog 2 of 4 series)
Pilot other considerations and requirements: Einstein Next Best Action on Flow(Blog 3 of 4 series)
Pilot FAQs-Einstein Next Best Action on Flow (Blog 4 of 4 series)
