Migrate to Flows v2

We're thrilled to announce a new version of our flow infrastructure (V2) designed to provide you with enhanced performance, scalability, and new features. In this article, we'll guide you through the simple process of updating your flows. You'll find step-by-step instructions and best practices to ensure a smooth transition.

While the updates are under the hood and won't affect your day-to-day interactions within the Flow Builder or Styles configuration, they are critical for future compatibility. It is critical to note that V1 Flows will not be compatible with newer SDK releases. See this matrix for flow and SDK version compatibility details.

Updating Descope Flows

Before Updating

Updating to the V2 infrastructure is a project-wide update, which means all of the flows and styles within the project will be updated. Updating your flows to V2 is a one-way activity with no revert possible. With this change across the project, doing some due diligence when deploying to your production environment is recommended.

• You must ensure that you use a specific SDK version with your V1 Flows and not import the latest SDK versions. This matrix shows the SDK and flow version compatibility.
• It is recommended to test V2 flows within your application before upgrading your production flows to V2. To test, we suggest utilizing a dev or sandbox project. If you do not have a dev or sandbox project, you can export and import your flows and styles within a new project. You'll then be prompted to update your flows within that project and test with your application.
  • Exporting and Importing Flows Guide
  • Exporting and Importing Styles Guide
• If you have E2E tests running on your application, such as Cypress Tests, you will need to update your tests and validate that they are functioning as expected after updating your flows. It is recommended to make the applicable updates within your development environment, and then update your production E2E tests when you migrate your production project to flows V2.
• If you are utilizing a Content Security Policy (CSP) on Flows V1, you will need to update your CSP to also include static.descope.com as a script src. You can see an example CSP within our Security Best Practices guide which includes this configuration.

Updating within Console

Within the Descope Console, flows can be updated to V2 within the Flows, Styles, or in the Flow Builder screen. The below are examples of the prompt to update your flows within the console. To update, simply click the Update button.

Updated Confirmation

Once the update to V2 has been completed, you will receive a confirmation. You can then update your application to utilize the correct SDK versions per this matrix

SDK Compatibility Matrix

You must ensure that you use a specific SDK version with your V1 Flows and not import the latest SDK versions. This matrix shows the SDK and flow version compatibility.