How to use ISCHANGED and PRIORVALUE in Before Save Flows by GORAV SETH
GORAV SETH demonstrates how you can use ISCHANGED and PRIORVALUE in Before Save Flows
Check it out
GORAV SETH demonstrates how you can use ISCHANGED and PRIORVALUE in Before Save Flows
Check it out
Created by Yumi Ibrahimzade
ABOUT
This is a Lightning Component that plays a sound effect.
It can be used on Flow Screens and Lightning Pages.
In order to play a sound, you have to upload the sound file as a Static Resource and then enter the name of the file to the “Sound File” parameter.
PARAMETERS
Sound File – Enter the name of the sound file.
CONSIDERATIONS
This component loads the sound file from Static Resources and plays it. So it is recommended to use smaller file sizes, otherwise it might take some time to load the file.
HOW TO USE
1- Upload the sound file as a Static Resource.
2- Add “SoundCMP” to your Flow Screen.
3- Enter the name of the sound file to the parameter called “Sound File”.
Have you ever wanted to add your own logging to your flows? I’m not talking about the system logs, but rather creating your own log entries at specific places in your flow.
I’ve had a couple of instances, where I could really use this. Both for debugging as well as simply tracing whether an auto-launched flow has executed.
After having reinvented the wheel a few times, I got tired of it and decided to create something that is more reusable, and it has proven its value already more than once.
What I’ve done is this… I’ve created a custom object, a number of flows and a few tools to manage it all. You can add this flow as a subflow to any of your own flows. This step will create a new record in the custom object on which you can report.
This Quip document contains all the details and the link to the managed package.

Jessie Rymph from the blog https://unhandledsunshine.com/ has published a post showcasing two new invocable actions available on this site showing how to Update N Records in Flow Without a Loop
The first post in a new series on the Salesforce admin blog demonstrates a novel way to launch auoto-launched flows from a formula field on a report. This has several very interesting use cases
Check it out
When our org migrated to Lightning, we were faced with an interesting issue: we had many task record types and in order to enable our end users to create tasks from the activity composer, we had to create a different quick action for each task record type. The result wasn’t pretty

Our users wanted a simple button where they could create a task with one click and be able to select the task record type.
When I set out to build the solution, I started by using a Get Records element to query the record type object but soon realized that I can’t filter this list based on the record types available to the current user.
I was able to provide a nice solution using the new invocable action and quickChoice component found here on this site. I used the Get Record Type Info by Object action to generate a list of record types available to the current user. Then I fed the record type labels and Ids into the Quick Choice component. Finally I created the task and used the Navigate to Record action to open the new task in edit mode.







GORAV SETH demonstrates how you can use the new flow before save trigger combined with duplicate rules to prevent creation of duplicate junction object records.
Check it out
This action can be used to generate a list of record types for a specific object. This can be useful when you would like to present a record type selector to the user. Can be used as inputs to the QuickChoice by setting Input Mode to “Dual String Collections”. Pass in one output collection for Labels and one for the underlying values

| Attribute | Type | Description |
| Object Name | String | API name of the target object example “Task” or “MyObject__c” |
| ignoreMasterRecordType | Boolean | If “on” then “Master” will not be added to the list of record types |
| onlyReturnActiveRecordTypes | Boolean | If “on” then only active record types will be added to the list |
| onlyReturnRecordTypesAvailableToCurrentUser | Boolean | If “on” then only record types available to the current user will be returned |
| Attribute | Type | Description |
| errors | String | captures details of any error that occurred |
| recordTypeIds | String | Ids of the records types. |
| recordTypeNames | String | Names of the record types. |
| defaultRecordTypeName | String | |
| defaultRecordTypeId | String |
1.1 Unmanaged 5/13/21 – Added outputs for the default Record Type
Narender Singh form ForcePanda wrote a two blog series about using map collections in flows. The second blog makes good use of the new generic sObject support in flows coming in the Spring ’20 release
Part 1: https://forcepanda.wordpress.com/2019/12/17/how-to-create-a-map-collection-in-flows-part-1/
Part 2: https://forcepanda.wordpress.com/2019/12/18/how-to-create-a-map-collection-in-flows-part-2flow-map-methods-spring20delight/
GORAV SETH shared a quick tip on his blog about a way to create a unique collection in flow
https://goravseth.com/creating-a-unique-collection-in-flow
