---
schema_version: "1"
id: 85d7378f91b47752cbf578f17e4e97404cb11073d3e6e825e991d11249bcf481
title: Handle Conflicts During Asset Date Amendments by Using Submit Order with Validation Flow
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/ind/264-0-0/dro_submit_order_with_validation_flow.md
canonical_url: https://help.salesforce.com/s/articleView?id=ind.dro_submit_order_with_validation_flow.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: 79eeed6abbda4c1ecfb7c9f63eae50ec1d70adc7a2a4fe4d8b5aaae9dfcccb5c
description: It's common to request adjustments to license subscription start dates, either moving them earlier if your users are ready to use them or delaying them if they are not. However, if the order that created the asset has incomplete steps in its fulfillment plan, submitting an asset amendment can result in two orders updating the asset simultaneously. Identify and handle incomplete steps in the fulfillment plan by using the Submit Order with Validation flow.
products:
  - Revenue Cloud
release: "264"
---
# Handle Conflicts During Asset Date Amendments by Using Submit Order with Validation Flow

It's common to request adjustments to license subscription start dates, either moving them earlier if your users are ready to use them or delaying them if they are not. However, if the order that created the asset has incomplete steps in its fulfillment plan, submitting an asset amendment can result in two orders updating the asset simultaneously. Identify and handle incomplete steps in the fulfillment plan by using the Submit Order with Validation flow.

### Required Editions

<table class="slds-table slds-table_bordered slds-max-medium-table_stacked slds-m-bottom_small edition"><colgroup><col></colgroup><tbody><tr class=""><td class="slds-cell-wrap" style="vertical-align:top;">Available in: Both Salesforce Classic (not available in all orgs) and Lightning Experience</td></tr><tr class=""><td class="slds-cell-wrap" style="vertical-align:top;">Available in: <strong>Enterprise</strong>, <strong>Unlimited</strong>, and <strong>Developer</strong> Editions</td></tr></tbody></table>

<table class="slds-table slds-table_bordered slds-max-medium-table_stacked slds-m-bottom_small permission">
        <colgroup>
          <col style="width:50%">
          <col style="width:50%">
        </colgroup>
        <thead class="slds-text-title_caps ">
          <tr class="">
            <th scope="colgroup" class="slds-cell-wrap" colspan="2" style="text-align:center;vertical-align:top;" id="d183156e69">User Permissions
              Needed</th>
          </tr>
        </thead>
        <tbody>
          <tr class="">
            <td data-label="User Permissions Needed" class="slds-cell-wrap" style="vertical-align:top;" headers="d183156e69 ">To run the Submit Order with Validation Flow:</td>

            <td class="slds-cell-wrap" style="vertical-align:top;" headers="d183156e69 ">
              <p>Fulfillment Designer</p>
              <p>OR</p>
              <p style="margin-bottom:0;">DRO Admin User</p>
            </td>

          </tr>
        </tbody>
      </table>

Use the flow to discard future-dated or pending steps that are no longer relevant in the existing fulfillment plan, so asset amendments are processed without conflicts.

The Submit Order with Validation flow uses the Get Steps from Order subflow, that retrieves the incomplete steps from an order. The order is identified using the orderID passed to the subflow. Both the flows are available as out-of-the-box template flows.

![Note](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-ind-revenue-264-0-0-production-enus/91ca99c6-d5c8-4986-b961-c6b7801e0d0d/images/icon_note.png)

Note The Submit Order with Validation flow is designed for orders containing up to 200 order line items. To work with larger orders, contact your Salesforce admin.

To use the Get Steps from Order subflow in the Submit Order with Validation flow, follow these steps:

1. From Setup, find and select **Flows**.
2. Find and select **Get Steps from Order**.
3. Save the Get Steps from Order template as a new flow and activate it.
4. Find and select **Submit Order with Validation**.
5. Save the Submit Order with Validation template as a new flow.
6. Replace the Get Steps from Order subflow step in the Submit Order with Validation flow with a call to the newly created active Get Steps from Order subflow.
7. Assign the same input and output variables that were used in the old subflow.
8. Activate the Submit Order with Validation flow.
    
    When you call the Submit Order with Validation flow using the orderId of an order with an incomplete fulfillment plan, the incomplete steps found in the order are shown. Review the steps and remove those that you don’t want to discard. Then, you can choose to discard the remaining incomplete steps and submit the order. Now, any future amendments to the asset can be processed without issues.