Component types for which old snapshots might not work:
New component types Introduced:
Changes related to Flow:
1) Now we can only retrieve the latest version of a flow. The version number postfix in a flow name is removed.
2) After deployment of a flow, it will create the latest version of that Flow in target org. It doesn't matter that what version was in source org.
3) As part of this upgrade, flow definitions are no longer necessary when you deploy or retrieve with Flosum. If you deploy with flow definitions, the active version number in the flow definition overrides the flow’s status field. For example, the active version number in the flow definition is version 3, and the latest version of the flow is version 4 with an Active status. After you deploy your flow, version 3 is the active version.
Deploy Active Processes and Flows
You can choose to deploy processes and flows as part of continuous integration and continuous delivery model without manually activating them. Previously, processes and flows were always deployed as inactive. In production orgs, a new setting lets you deploy a new active version of a process or flow. This setting doesn't appear in non-production orgs (such as scratch, sandbox, and developer orgs), because you can always deploy a new active version.
Where: This change applies to Lightning Experience and Salesforce Classic in Essentials, Professional, Enterprise, Performance, Unlimited, and Developer editions.
How: You must opt-in to deploy active processes and flows. From Setup, enter Process Automation Settings in the Quick Find box, then select Process Automation Settings.
Select Deploy processes and flows as active.
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 auto-launched flows in your org. The required percentage is the same as the code coverage requirement for Apex code. If the required percentage isn’t met, the deployment is rolled back.