Contents
- 1 How can a developer check the test coverage of active process builder and flows deploying them in a changing set?
- 2 Do we need to activate process builder after deployment?
- 3 When to deploy an active process in Salesforce?
- 4 Can a flow definition be added to a deployment?
- 5 Is the default flow version included in the deployment package?
How can a developer check the test coverage of active process builder and flows deploying them in a changing set?
Required Editions
- From Setup, in the Quick Find box, enter Automation , then select Process Automation Settings.
- Select Deploy processes and flows as active.
- Enter the flow test coverage percentage.
- Save your changes.
Do we need to activate process builder after deployment?
Process Builder Processes are always deployed as inactive. This creates additional work during deployment (then go click to Activate it), and introduces new problems with APEX test coverage. For a future deployment, you can mark the Process as Inactive, and then re-activate it.
Can I add process builder to change set?
Step-by-step guide. Setup > Deploy > Outbound Change Sets > Continue > New > Name and Save > Under “Change Set Components” click “Add” button > Component Type: = Flow Definition > Select your “Process” > click “Add to Change Set” button. You can then choose to Validate or Deploy it.
When to deploy an active process in Salesforce?
When you deploy an active process or flow in a production org, Salesforce runs your org’s Apex tests and confirms that enough of your processes and flows have test coverage. Specifically, the Apex tests must launch at least 75% of the total number of active processes and active autolaunched flows in your org
Can a flow definition be added to a deployment?
We won’t automatically add a version of the flow to the deployment package for you, because we don’t want to make assumptions about which version (s) you’d like to deploy. That is, unless your flow definition references a specific version of the flow, which brings us on to the next error.
Are there problems deploying flows in process builder?
Thanks to feedback from some of our fantastic users, we’ve addressed the major challenges faced when deploying flows. Let’s take a look, one error at a time.
Is the default flow version included in the deployment package?
This fix is enabled by default, so if you click straight through the deployment warnings, we’ll include the referenced flow version in your deployment package automatically and your deployment should go ahead as intended.