You are here:
Context Scopes
Context scopes describe the relational path from a root sObject, such as an Order, to related sObjects. Context mappings use context scopes to identify the fields on the sObjects or computed data that is matched with context dimension variables. The Context Rule Service evaluates the information.
The following root context scopes are supported:
-
Order
-
Opportunity
-
Quote
-
Asset*
-
Any
*You can only use the Asset scope for rules invoked during repricing.
Each of these scopes can then reference account and contract scopes.
For more information about the any context scope, see Any Context Scope.
Types of Context Scopes
Most context rules use an Entity context scope type. Entity context scopes refer to specific sObjects entities such as Order, Quote, and Asset.
As of CME Summer '18, context rules for pricing adjustments must use a Virtual context scope type. You use virtual context scopes to map to data entered by users at run time, which is stored only in memory.
Creating Context Scopes
If context scopes are not defined in your environment, you must define them before creating context rules. For instructions about how to create context scopes, refer to Creating Context Scopes.
- Creating Context Scopes
If context scopes have not been created in your environment, you must create them before defining context rules. This process is performed once as part of the initial context rule setup. - Virtual Context Scopes
Starting in Summer '18, virtual context scopes enable you to create context mappings to virtual objects. Virtual context scopes and virtual objects enable you evaluate data entered by the user at run time that is stored only in memory, such as pricing adjustment data. The Summer '18 release contains one supported virtual object, AdjustmentData, that is used for context rules for pricing adjustments. - Any Context Scope
Theanycontext scope enables you to create context mappings that can be used across all root context scopes. For example, instead of creating separate context mappings to evaluate the status field across orders, quotes, and opportunities, you can useanycontext scope to evaluate the status for all root entities, including orders and quotes. You can also specifyanyas the entity for second-level context scopes, enabling you to evaluate information in accounts and contracts across all root entities.
