Deep cloning uses the preconfigured context definition
FulfillmentWorkspaceDeepCloneContext by default. Configure deep clone settings to include
supported custom fields or objects, or to transform field values during cloning.
Required Editions
Available in: Enterprise, Unlimited, and Developer
Editions
User Permissions
Needed
To configure deep cloning for fulfillment workspaces:
DRO Admin
Turn on Context Definitions to load the FulfillmentWorkspaceDeepCloneContext context
definition. For more information, see Turn On Context Definitions.
By default, deep cloning uses this preconfigured FulfillmentWorkspaceDeepCloneContext
context definition to copy the fulfillment workspace, workspace items, step definition
groups, step definitions, and step dependency definitions. This configuration is optional.
Configure deep cloning only when you want to:
Extend the context definition to include supported custom fields or objects. Create a
context definition that extends FulfillmentWorkspaceDeepCloneContext, and then select it
for deep cloning.
Select an expression set when you want to transform field values in the cloned
records.
From Setup, in the Quick Find box, enter and then select Dynamic Revenue
Orchestrator Settings.
Select Deep Clone Settings.
For Fulfillment Workspace Context Definition, select a context definition.
To copy the standard supported records, select
FulfillmentWorkspaceDeepCloneContext.
To also copy supported custom fields or objects, select a context definition that
extends FulfillmentWorkspaceDeepCloneContext.
Optional: To transform field values in the cloned records, select an expression set for
Fulfillment Workspace Expression Set.
For example, use an expression set to append text to cloned record names or assign a
different value to a custom field.
The selected context definition and expression set apply to all subsequent fulfillment
workspace deep clones.
We use three kinds of cookies on our websites: required, functional, and advertising. You can choose whether functional and advertising cookies apply. Click on the different cookie categories to find out more about each category and to change the default settings.
Privacy Statement
Required Cookies
Always Active
Required cookies are necessary for basic website functionality. Some examples include: session cookies needed to transmit the website, authentication cookies, and security cookies.
Functional Cookies
Functional cookies enhance functions, performance, and services on the website. Some examples include: cookies used to analyze site traffic, cookies used for market research, and cookies used to display advertising that is not directed to a particular individual.
Advertising Cookies
Advertising cookies track activity across websites in order to understand a viewer’s interests, and direct them specific marketing. Some examples include: cookies used for remarketing, or interest-based advertising.