Starting with Summer ’20, some Process Builder processes (which are technically Flows with process type ‘Workflow) can be converted to Flows of process type ‘Autolaunched’. The new flow shows up in Flow Builder and takes advantage of the new Record Change trigger that Flow Builder now supports.
The package here will install into your org a flow called Convert Processes to Flows. it allows you to select a Workflow:
It will then retrieve the workflow metadata from your org using the new Transfer Metadata screen component, then pass the metadata to a flow action called ConvertFlowMetadata.
Here’s a video:
Flow Builder’s ability to do the things Process Builder does is a little limited in Summer ’20. Most notably:
- Flow doesn’t have Scheduled Action support
- Flow doesn’t support related field references like myVar.Owner.FirstName
- Flow doesn’t support the ISCHANGED, ISNEW, PRIORVALUE functions
If you select a workflow with any of these characteristics, the Flow will report the error and stop.
Here’s an example of a Process Builder workflow:
And here’s what it looks like after conversion:
It’s recommended that you only run this on Sandboxes for the time being.
The converter automatically creates a unique name for the new flow by taking the Process Builder name and adding ‘-Converted’. It does not change the label or interviewLabel (used for paused flows). Keep in mind that you’ll now have two processes, one in Process Builder lists and one in Flow lists, with the same Label. If this turns out to be a problem we can add logic to automatically create a modified label.
(We recommend that you only install this in sandboxes for now)