Adding an attribute to a context definition changes the definition metadata, but Revenue Management services do not consume that revised structure until the context definition isactivated. Activation publishes the current definition so dependent services such as Salesforce Pricing can use its nodes and attributes.

That explains why the newly created custom field is visible in the context-definition configuration but unavailable when the consultant attempts to reference it from the pricing procedure. The definition has not yet been promoted into an active runtime state.

Option A is not the primary missing step identified in this scenario. Tags can be important for locating and semantically identifying contextual attributes, but they do not substitute for activating the modified context definition. Option C is unnecessary. A pricing procedure does not need to be cloned merely because another usable attribute has been added to its associated context.

The correct sequence is to modify the context definition, complete the required mappings,activate the definition, and then configure the pricing procedure to consume the newly available attribute.

Study Guide Reference:Configure, Price, Quote — Context Service and Salesforce Pricing; context definitions; activation and pricing procedure inputs.

===============