Revenue Cloud: Product Configuration Rule silently skipped for custom attribute mapped in extended Sales Transaction Context

Work through the causes below in order. The most common root cause is that the extended context definition is not the one bound to the Rule Library, or the extended definition was edited without being re-activated.

Cause 1: Extended context definition is not activated after editing
1. Navigate to Setup > Feature Settings > Context Service > Context Definitions.
2. Open the Custom Definitions tab and select your extended SalesTransactionContext definition.
3. Confirm the Status column shows Active. If it shows Draft, the runtime engine continues to use the previously active version, so any newly added custom attribute mapping is invisible to rules.
4. Click Activate. Wait for activation to complete (status changes to Active).

Cause 2: Custom attribute is not mapped to the source field on the correct node
1. Navigate to Setup > Feature Settings > Context Service > Context Definitions and open your extended definition.
2. On the Structure tab, confirm the custom attribute (for example RecipientCity__c) is defined on the SalesTransactionItem node with direction INPUT OUTPUT and the correct data type (STRING, NUMBER, BOOLEAN).
3. On the Map Data tab, for QuoteEntitiesMapping click Edit SObject Mapping.
4. Select Mark as Default and click Map. The Mark as Default option is required — if no mapping is marked default, runtime hydration silently skips the mapping.
5. On the ContextMapping page, map the custom attribute to the source field on Quote Line Item [QuoteLineItem] (for example RecipientCity__c to QuoteLineItemRecipient.ServiceCity).
6. Repeat steps 3-5 for OrderEntitiesMapping so the same attribute is hydrated at order save.
7. Save your mappings and re-activate the context definition.

Cause 3: Rule Library is bound to the wrong context definition
1. From the App Launcher, find and select Rule Libraries.
2. Open the Rule Library used by the failing Product Configuration Rule.
3. Confirm the Usage Type [UsageType] is set to Configurator and the Context Definition Developer Name [ContextDefinitionDeveloperName] matches the extended SalesTransactionContext definition (not the standard SalesTransactionContext). If the library points at the standard definition, the custom attribute does not exist in its schema and the rule is silently skipped.
4. Update the Context Definition Developer Name to the extended definition and save.
5. Open the Product Configuration Rule and re-validate. Deactivate and re-activate the rule so it picks up the updated library binding.

Cause 4: Configurator Setup is not pointed at the extended definition
1. Navigate to Setup > Feature Settings > Revenue Cloud > Revenue Settings.
2. Under Set Up Configuration Rules with Business Rules Engine, confirm the selected context definition is the extended SalesTransactionContext definition. If it is set to the standard definition, custom attributes are not available to the rule engine.
3. Save your changes.

Cause 5: Custom field context tagging limit exceeded (Known Issue KI-60098)
1. In Setup > Feature Settings > Context Service > Context Definitions, open the extended definition and count the custom attributes on SalesTransactionItem.
2. If the org has more than 256 custom field context tags, this is tracked as Known Issue KI-60098. There is no published workaround; reduce the number of custom-tagged attributes by consolidating fields, or open a case referencing KI-60098 to track the fix.

Verification:
Confirm the issue is resolved by re-opening the affected Quote [Quote] in the Quote Line Editor, adding or editing a product line that should trigger the Product Configuration Rule on the custom attribute, and saving. The rule must now fire — for example, the disqualification, default value, or validation message defined in the rule must appear. Repeat the test on an Order [Order] line to confirm the rule fires at order save as well.