---
schema_version: "1"
id: 6c604dba029b4cf267ebacfa92f9f3a38f5854aa9124c02ea669873f4941f591
title: "Example: Add Action with Time-Awareness Turned On"
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/ind/264-0-0/dro_time_aware_fulfillment_example_add.md
canonical_url: https://help.salesforce.com/s/articleView?id=ind.dro_time_aware_fulfillment_example_add.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: 2b093214eb1bf2c56d60811a9066070d999f1d6f67ad4ba82add5c01ab209e81
description: Let's see how Dynamic Revenue Orchestrator (DRO) uses time-awareness to decompose a multi-year ramp deal into fulfillment order line items (FOLIs) and Fulfillment Asset State Period (FASP) records that align with each year's effective dates.
products:
  - Revenue Cloud
release: "264"
---
# Example: Add Action with Time-Awareness Turned On

Let's see how Dynamic Revenue Orchestrator (DRO) uses time-awareness to decompose a multi-year ramp deal into fulfillment order line items (FOLIs) and Fulfillment Asset State Period (FASP) records that align with each year's effective dates.

### 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: <strong>Enterprise</strong>, <strong>Unlimited</strong>, and <strong>Developer</strong> Editions</td></tr></tbody></table>

Consider a commercial product, Agentforce for Sales, that decomposes into SC-Business or SC-Enterprise based on the Business attribute, and Tenant and License Provisioning. This example uses the Business attribute, so only SC-Business is created.

![Agentforce for Sales commercial product decomposes into SC-Business (Business attribute), SC-Enterprise (Enterprise attribute), Tenant, and License Provisioning technical products.](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-ind-revenue-264-0-0-production-enus/91ca99c6-d5c8-4986-b961-c6b7801e0d0d/revenue/images/dro/dro_advance_amendment_example.png)

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

Example

The customer purchases Agentforce for Sales in a 3-year ramp deal that starts January 1, 2026, with license quantities increasing each year.

- Year 1: 100 licenses
- Year 2: 200 licenses
- Year 3: 300 licenses

Without time-awareness, decomposition produces a single configuration with no effective start or end dates. Later amendments overwrite past or future data and leave the asset in an inaccurate state.

With time-awareness enabled, DRO generates FOLIs mapped to each effective date range.

![Three Order Line Items (OLIs) for Agentforce for Sales each produce Add-action FOLIs for the SC-Business, Tenant, and License Provisioning technical products. The Fulfillment Asset (FA) timeline on the right shows one FA per technical product.](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-ind-revenue-264-0-0-production-enus/91ca99c6-d5c8-4986-b961-c6b7801e0d0d/revenue/images/dro/dro_advance_amendment_example1.png)

DRO generates these FOLIs for each technical product:

- SC-Business: Three FOLIs for 100, 200, and 300 licenses, one per year.
- License Provisioning: Three FOLIs that match the ramping quantities across the timeline.
- Tenant: Three FOLIs that maintain a quantity of 1 across all three years. Because Tenant has account scope, its quantity stays at 1 regardless of the license ramp.

Each FOLI produces an Add action because no prior Fulfillment Asset or FASP records existed for these technical products on this account.

Because the FOLIs are sliced by time, DRO creates FASP 1, FASP 2, and FASP 3 for each FA. This structure prevents data overwrites and makes sure that the asset configuration that is active at any point in time drives orchestration.