PingOne DaVinci

Change management

Follow these best practices to manage and track changes to your flows.

Use flow aliases for version control

When your flow reaches a milestone, add an alias to the flow version with a name, deployment status, and version number, such as Dashboard-PROD_v.117.

  1. Open the flow.

  2. Go to More options ( ) → Flow Versions.

  3. Find the correct version and go to ... → Set Version Alias.

  4. Enter the alias and click Save.

A screen capture showing flows with the environment and version included in their names.

Configure your application’s flow policy to use the specific version of the flow instead of the latest version. This allows you to continue developing your flow without affecting production.

A screen capture of an application’s flow policy, showing that the selected version of the flow is not the latest version.

When you change the flow, update the version number in the name, as shown in the following examples.

A screen capture showing a flow renamed to include the version number.

Export flows and subflows for source control

With each version change of the flow, go to the menu and export the flow as a JSON file:

  1. In the upper-right corner of the flow editor, click the More Options ( ) icon and click Download Flow JSON.

  2. Save the file.

  3. Follow your organization’s source control best practices for maintaining the file.

    Do not post flows or subflows to externally-accessible locations to protect secure information.