Which valid actions can a consultant perform on a standard context definition?

Standard (out-of-the-box) context definitions provided by Salesforce are protected to ensure the integrity of core system functionality. A consultant cannot directly modify or deactivate these standard definitions. To introduce custom logic or variations, the sanctioned methods are to either clone the standard definition to create a new, editable custom version or to extend it. Extending allows a new definition to inherit the attributes of the standard one while adding new, specific elements, promoting reusability and a clear upgrade path.

A. Deactivate & Edit: Standard context definitions cannot be directly edited or deactivated. These actions are restricted to prevent breaking dependent processes that rely on the standard configuration.

C. Copy & Edit: While "Copy" is synonymous with "Clone" and is a valid action, the term "Edit" is misleading. You cannot edit the original standard definition. You can only edit the new custom version created after cloning.

1. Salesforce Help, Industries CPQ Pricing Designer Guide, "Context Definitions": The guide details the management of context definitions. It specifies that to customize a standard definition, you must first clone it. The documentation states, "You can't edit or delete a standard context definition. To customize a standard context definition, you must clone it." This confirms that direct editing is prohibited and cloning is the correct procedure.

2. Salesforce Help, Industries CPQ Pricing Designer Guide, "Extend a Context Definition": This section explicitly describes the process and purpose of extending context definitions. It notes, "You can extend a context definition to reuse its structure and add more nodes to it... Extending a context definition is useful when you want to reuse the structure of an existing context definition." This validates "Extend" as a permissible action on standard definitions.