Posts

Showing posts with the label beta

Salesforce Fact #923 | Find out matching leads/contacts using screen action

Image
Another use case using Screen flow action(Beta). We can have a screen flow to take email Id as input and find out what all existing contacts and leads are present with the same email. For this, we create a subflow to fetch the contacts and leads based on the input email passed. Also, to avoid unnecessary fetching of records, we can add validation to ensure the get records are performed only when the email is of valid email format. And in the main flow, we can refer the subflow in screen action and show the matching contacts or leads instantly. Attached are the screenshots.

Salesforce Fact #873 | Exploring screen flow action button(Beta)

Image
With Summer'24 release, we can now access the screen flow action button feature as a Beta feature. As a use case, we know that capitalizing text does not work properly with screen flow reactivity. We can make use of a subflow which takes a string as input and returns the capitalized version. In this example, we are calling the subflow from a action button and the returned text is also set on the actual input with the help of formula resource 'InputDisplayValue'. Attached are the screenshots.

Salesforce Fact #820 | Auto populate date in repeater component in screen flow

Image
Suppose we have a use case in screen flow where we need to autopopulate some date input based on the user choice in all the instances of the repeater component. So, we can have a checkbox 'apply to all' along with a date type input. Once the checkbox is selected, the input date will get populated automatically in repeater instances. Thanks to the screen reactivity support of Repeater(Beta) which avoids manually changing the date in each of the repeater instances. Attached are the screenshots.

Salesforce Fact #812 | Repeater(Beta) component in screen flow

Image
In Spring'24 release, we have the new Repeater(Beta) component introduced in screen flow builder. The input components inside the repeater component are tracked using the AllItems attribute. So, in order to get the length of the repeater collection, we need to iterate over the AllItems list and count its length, since the equals count operator is not supported yet to get the collection length. Reference:  https://help.salesforce.com/s/articleView?id=sf.flow_ref_elements_screencmp_repeater.htm&type=5 Attached are the screenshots. Output:

Salesforce Fact #806 | Flow Transform(Beta) in action

Image
Suppose we need to show the account names in capitalized format after retrieving in screen flow. Now, no need to iterate over the list of accounts. We have the Transform(Beta) component which can take care of the formatting right when the mapping is done. Attached are the screenshots.

Salesforce Fact #694 | Reactive screen components(beta)

Image
With Summer'23 release, we now have the reactive screen components(beta) feature. Although there are certain limitations currently, but this will definitely be a game changer. To enable this feature, go to Setup -> Process Automation Settings -> Enable the checkbox 'Opt in to Reactive Screen Beta'. In this example, we have an input text field in screen flow and we are setting the value of the slider component with the length of entered data. Reference:  https://admin.salesforce.com/blog/2023/flow-reactive-screen-components-beta-learn-moar-summer-23?icid=TH:th-trailmix:learn_moar_summer_23 Attached are the screenshots.

Salesforce Fact #693 | User access policy in action

Image
User Access Policies is now in Beta phase. Thanks to Summer'23 release. Now, you can automate the Permission Set, Public Group or queue assignments once you create or update the any user which matches a particular Profile/Role/Permission Set condition. In this example, we have setup a User access policy which assigns the PS 'Test Permission Set' and Public group 'Test PG1' if the user with profile 'Test Profile' is created/updated. Note: There are couple of statuses available while configuring User access policy. It gets executed only if it is in 'Active' status.  In order to enable the feature, go to User Management Settings -> Enable 'User Access Policies (Beta)'. Attached are the screenshots.

Salesforce Fact #569 | Datatable(Beta) in screen flow

Image
With the Winter'23 release, now we can show records in lightning datatable from screen flow. It can take a collection of records as source and also it supports preselected rows. Also , we can select columns to be shown and configure certain properties. Reference:  https://admin.salesforce.com/blog/2022/learn-moar-in-winter-23-with-flow-enhancements?utm_source=trailhead&utm_medium=trailmix&utm_campaign=learn_moar_winter_23&_ga=2.56687146.1493055349.1669019286-156340033.1662614994 Attached are the screenshots.