SALESFORCE-REV-CON-201 practice question 10 of 25

A company selling hardware and software needs to implement a 2-day delay for software provisioning after hardware delivery in its order-to-cash…

Full set: 165 questions

Domain Revenue Cloud Core Concepts

A company selling hardware and software needs to implement a 2-day delay for software provisioning after hardware delivery in its order-to-cash process. While configuring the Dynamic Revenue Orchestrator (DRO) plan, the Fulfillment Designer notices the option for adding this delay is not visible on the provisioning task. What should the Revenue Cloud Consultant enable to add this option for the Fulfillment Designer?
Answer options
A: Future-Dated Steps in the DRO settings Correct answer
B: Modify All Data permission in the Fulfillment Designer's profile
C: Link Task to Step Source button in the DRO settings
Correct Answer:
A. Future-Dated Steps in the DRO settings
Explanation

Dynamic Revenue Orchestrator (DRO) plans require specific features to be enabled to expose advanced configuration options. To implement a time-based delay for a fulfillment task, such as provisioning software two days after hardware delivery, the "Future-Dated Steps" feature must be activated within the DRO plan's settings. Enabling this feature makes the necessary fields and options visible in the configuration interface, allowing the Fulfillment Designer to define the required delay relative to a predecessor task's completion. Without this setting enabled, the functionality to schedule a step for a future date remains hidden.

Why Incorrect

B. Modify All Data permission in the Fulfillment Designer's profile: This is a system-wide data permission and is not required for configuring specific features within a DRO plan. The issue is a missing feature option, not a general inability to edit records.
C. Link Task to Step Source button in the DRO settings: This function is used to associate a fulfillment step with its originating record (e.g., an Order Product). It establishes the "what" to fulfill, but does not enable the "when" or time-delay logic between steps.

References

1. Salesforce Help - Configure a Dynamic Revenue Orchestrator Plan: "To use certain advanced features, such as future-dated steps or step grouping, you must enable them on the DRO plan record. ... To allow fulfillment designers to set a delay for a fulfillment step, select Enable Future-Dated Steps." This documentation explicitly states that the "Future-Dated Steps" setting must be enabled on the plan to allow for delays.

2. Salesforce Help - Dynamic Revenue Orchestrator Step Dependencies: "You can create a dependency that starts a step a certain number of days after its predecessor is completed. To use this feature, your admin must select Enable Future-Dated Steps on the DRO plan." This source confirms that time-based dependencies are contingent on the "Future-Dated Steps" feature being enabled at the plan level.

Scroll to Top