---
schema_version: "1"
id: 84fedd1bda124e0374d9bd658322f3d48c8bf682f08ddf72057c288eb27347d2
title: Use Custom Dates To Schedule Fulfillment Steps
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/ind/264-0-0/dro_custom_dates_for_fds.md
canonical_url: https://help.salesforce.com/s/articleView?id=ind.dro_custom_dates_for_fds.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: bc0b21d5c65cf165410eb9f01ec1cf5eacc781c8ea8bcee23d061352e602ccc8
description: Configure the execution of steps in your orchestration plan based on custom dates that correspond to date or datetime tags in context definition. For example, you can map a custom context tag to a custom field to activate a service on a date requested by the customer.
products:
  - Revenue Cloud
release: "264"
---
# Use Custom Dates To Schedule Fulfillment Steps

Configure the execution of steps in your orchestration plan based on custom dates that correspond to date or datetime tags in context definition. For example, you can map a custom context tag to a custom field to activate a service on a date requested by the customer.

### 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="d65858e69">User Permissions
              Needed</th>
          </tr>
        </thead>
        <tbody>
          <tr class="">
            <td data-label="User Permissions Needed" class="slds-cell-wrap" style="vertical-align:top;" headers="d65858e69 ">To define how a product decomposes:</td>

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

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

- Configure the context definition with Date/Datetime fields. See [Configure Steps for Future Execution](https://help.salesforce.com/s/articleView?id=ind.dro_configure_steps_for_future_execution.htm&release=264.0.0&type=5 "Fulfillment designers can configure the steps to be executed at a future date and time. They can set a delay for the execution of steps based on the start date of the source line item, the execution time of the previous steps, or a custom date based on a context definition field.").
- Turn on the Future Dated Steps setting in Dynamic Revenue Orchestrator Settings.

![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

If there are multiple sources for a fulfillment step, the latest of the dates from all sources is used for schedule calculation before applying the delay.

If no value is found for the Custom Date during orchestration, the, current time is used as the execution time and any specified delay is ignored.

Follow these steps to configure the fulfillment steps with custom dates:

1. From the App Launcher, find and select **Fulfillment Step Definitions**.
2. Create or edit a fulfillment step definition.
3. Navigate to the Execution Schedule section.
4. From the Execute Based On dropdown list, select the Custom Date option.
5. From the Custom Date picklist displaying the available date and datetime tags from your configured context definitions, select a value.
6. Optionally, enter a delay value along with a delay unit.
    
    To schedule future-dated orchestration steps to occur before a specific event, use negative delay values.
    
    Check the execution time in the orchestration plan. The execution date for the step is calculated by extracting the date from the standard object field mapped to the chosen context tag and then applying the specified delay. To verify the schedule, click the ![Dependency icon](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-ind-revenue-264-0-0-production-enus/91ca99c6-d5c8-4986-b961-c6b7801e0d0d/revenue/images/dro/icons/dro_calendar_icon.png) on the step card in Orchestration Plan viewer.
    
    ![Orchestration Plan Viewer showing the Future Date Step Details](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-ind-revenue-264-0-0-production-enus/91ca99c6-d5c8-4986-b961-c6b7801e0d0d/revenue/images/dro/dro_custom_dates_fds_orchestration_plan.png)
    
    ![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
    
    If there are multiple sources for a fulfillment step, the latest of the dates from all sources is used for schedule calculation before applying the delay.
    
    If no value is found for the Custom Date, or if a calculated run time has already passed during orchestration, the current time is used as the execution time and any specified delay is ignored.
    
    Negative delays that are logically invalid are excluded, such as steps dependent on a previous step’s execution date.