Loading
Prepare for Email to Become the Default Login ExperienceRead More
Use Custom Dates To Schedule Fulfillment Steps

You are here:

  1. Salesforce Help
  2. Docs
  3. Agentforce Revenue Management

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

Available in: Both Salesforce Classic (not available in all orgs) and Lightning Experience
Available in: Enterprise, Unlimited, and Developer Editions
User Permissions Needed
To define how a product decomposes:

Fulfillment Designer

OR

DRO Admin User
  • Configure the context definition with Date/Datetime fields. See Configure Steps for Future Execution.
  • Turn on the Future Dated Steps setting in Dynamic Revenue Orchestrator Settings.
Note
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 on the step card in Orchestration Plan viewer.
    Orchestration Plan Viewer showing the Future Date Step Details
    Note
    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.

 
Loading
Salesforce Help | Article