When you create a context definition, manually entering attributes and tags can be
time-consuming, especially if your node has several attributes. To save time, clone an existing
context definition and modify it based on your requirements. When cloning an extended context
definition, you can also preserve the inheritance to the parent context definition.
Required Editions
Available in: Lightning Experience
Available in: Developer, Enterprise, Professional, and
Unlimited editions for Industries clouds where Context Service is
enabled
User Permissions
Needed
To clone context definitions:
Context Service Admin
Differences Between Cloning and Extending a Context Definition
FEATURE
CLONE CONTEXT DEFINITION
EXTEND CONTEXT DEFINITION
Applicable To
Both Standard and Custom Definitions
Only Standard Definitions
Upgrades
Not available for standard definitions (no automatic upgrades)
Available for
clones of extended definitions with Preserve Inheritance
enabled.
Available (Auto upgrade and Sync Now option available)
Customizations
Customizable (can edit, delete, or add components)
Only additive changes are allowed (to add new components)
Editing Standard Components
Edit or delete components, including standard components
Can't edit or delete standard components
Use Case
Full flexibility for creating a custom definition
Customization on top of the Standard Definition, while preserving all the
standard components
Important The newly cloned context definitions show the same active or inactive
state as the context definition from which it's cloned.
While cloning an extended
definition, if Preserve Inheritance is selected, the new clone is
created in an inactive state so you can edit it before activating it.
From Setup, in the Quick Find box, enter Context Service, then
select Context Definitions.
For the context definition that you want to clone, click , and then select Clone.
Give your new cloned context definition a name.
While cloning an extended definition, to maintain the inheritance to the parent
standard definition, select the Preserve Inheritance
checkbox.
When you preserve inheritance, your cloned definitions, including all custom nodes,
attributes, and mappings, remain eligible for upgrades in future releases.
Save your changes.
Note Definitions that are cloned from a standard definition aren’t auto upgraded.
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.