---
title: "Scenario 4: Promotion of a PingOne DaVinci flow policy (early access)"
description: Learn how promoting a PingOne DaVinci flow policy differs from promoting the flow itself and understand how versions and dependencies are handled.
component: pingone
page_id: pingone:early-access-features:ea-p1_config_promotion_scenario_4
canonical_url: https://docs.pingidentity.com/pingone/early-access-features/ea-p1_config_promotion_scenario_4.html
revdate: December 22, 2025
section_ids:
  configure-and-run-the-promotion-in-the-source-environment: Configure and run the promotion in the source environment
  steps: Steps
  result: Result
  verify-the-promotion: Verify the promotion
  steps-2: Steps
  result-2: Result
---

# Scenario 4: Promotion of a PingOne DaVinci flow policy (early access)

The goal of this scenario is for you to promote a PingOne DaVinci flow policy so that you can understand how flow versioning and dependencies are handled during promotion, and how the promotion of a flow policy differs from promoting the flow itself.

In this scenario, you'll promote the **PingOne Sign On and Registration** flow policy from the **Promotion-Source** environment to the **Promotion-Target** environment. This flow policy is associated with the **PingOne SSO Connection** application, which doesn't exist in the **Promotion-Target** environment.

![A screenshot of the Test Registration, Password Reset, and Recovery flow in the Promotion-Source environment showing that there are four versions of the flow and Version 3 is the deployed version.](_images/p1-promote-scenario4-dv-apps-in-both-env.png)

If you click the application to open it, you'll see that it references two flow policies:

* **PingOne - Sign On and Registration** (latest version)

* **New flow policy** (version 1)

![A screenshot of the PingOne SSO Connection application Flow Policy tab showing the two flow policies it references.](_images/p1-promote-scenario4-dv-flowpolicies-in-source.png)

## Configure and run the promotion in the source environment

To configure the promotion, you'll confirm the target environment, select the resource to promote (the **PingOne Sign On and Registration** flow policy) and determine how to manage several dependencies. Then you'll run the promotion.

### Steps

1. In the PingOne admin console for the **Promotion-Source** environment, go to **Promote > Promotions**.

2. Click **Run a Promotion**.

3. On the **Confirm Target Environment** modal, ensure that **Promotion-Target** is selected in the **Target Environment** list.

4. Select **The correct environment is selected and I want to continue** and click **Confirm**.

   ![A screenshot of the Confirm Target Environment modal with Promotion-Target selected in the Target Environment list and the confirmation checkbox selected.](_images/p1-promote-confirm-target-env.png)

   After you confirm the target environment, PingOne takes snapshots of both environments, compares configuration resources, and lists the resources that you can promote.

   ![A screenshot of the Select Resources to Promote page without anything selected.](_images/p1-promote-select-resources.png)

5. On the **Select Resources to Promote** page, search for the **PingOne - Sign On and Registration** flow policy and select it.

   ![A screenshot of the Select Resources to Promote page showing the PingOne Sign On and Registration flow policy selected.](_images/p1-promote-scenario4-source-flow-policy-selected.png)

6. Click **Next**.

   The **Map Resources** page displays. Because no versions of the flow policy exist in the target environment, the promotion service indicates that the flow will be created as a new resource.

   ![A screenshot of the Map Resources page showing that the Test Registration, Password Reset, and Recovery flow will be created as a new resource.](_images/p1-promote-scenario4-map-resources.png)

7. Click **Confirm and Continue**.

8. On the **Auto-Selected Dependencies** page, determine how to map the dependent resources and click **Continue**.

   ![A screenshot of the Auto-Selected Dependencies page listing the dependent DaVinci flows.](_images/p1-promote-scenario4-autoselected-dependencies.png)

   Notice the absence of the **PingOne SSO Connection** application in the list of dependencies.

9. Verify the promotion details on the **Confirm Promotion** page and enter release notes.

   The **PingOne SSO Connection** application is now listed as part of the promotion, even though it wasn't listed as a dependency. Because the flow policy can't exist without the application, the promotion service automatically includes it in the promotion.

   ![A screenshot of the Confirm Promotion page, with the PingOne SSO Connection application surrounded with a red box.](_images/p1-promote-scenario4-confirm-promotion.png)

10. Click **Run Promotion**.

### Result

You're returned to the **Promotions** page and the current promotion is listed with a status of **In Progress**. After about 30 seconds, refresh the page. The status will change to **Success** for a successful promotion.

![A screenshot of the Promotions page showing a successful promotion.](_images/p1-promote-promotion-successful.png)

## Verify the promotion

To verify the results of the promotion, first confirm the details of the promotion in the source environment, then ensure that the flow policy now exists in the target environment.

### Steps

1. In the PingOne admin console for the **Promotion-Source** environment, go to **Promote > Promotions**.

2. Locate the promotion in the list, click the **More Options** icon (⋮), and select **View**.

   |   |                                                                                                                    |
   | - | ------------------------------------------------------------------------------------------------------------------ |
   |   | Promotions are listed in reverse chronological order, so the most recent promotion appears at the top of the list. |

   Verify that the promoted resources match what you configured.

3. On the **Overview** tab, click **View Target Environment**.

   You're taken to the PingOne admin console for the target environment so that you can confirm that the promoted resources exist and match what you expect.

4. For this scenario, go to **DaVinci** and click **Applications** in the sidebar for the DaVinci admin console.

   The **PingOne SSO Connection** application is now listed on the **Applications** page in the target environment.

   ![A screenshot of the PingOne SSO Connection application in the target environment.](_images/p1-promote-scenario4-pingone-ssoconnex-app-in-target.png)

5. Click the **PingOne SSO Connection** application to open it.

6. Click the **Flow Policies** tab.

### Result

Only the **PingOne - Sign On and Registration** policy displays because that's the resource you promoted to the target environment. If you had promoted the application, then the **New flow policy** would also have been promoted.

![A screenshot of the Flow Policies tab for the PingOne SSO Connection application in the target environment, showing that only the PingOne - Sign On and Registration policy was promoted.](_images/p1-promote-scenario4-flow-policies-after-promotion.png)