---
schema_version: "1"
id: 14d0dc2dce972bbd7f00a5863210c8b43c6a1de3d89b93a0fe4cf9dcca18b2ab
title: Create Context Dimensions
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/ind/264-0-0/comms_create_context_dimensions.md
canonical_url: https://help.salesforce.com/s/articleView?id=ind.comms_create_context_dimensions.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: 75e5c0fe04c18aaf4e2956fe07ebadb506606d9497c36fc76346ed89b051013d
description: Context dimensions are variables that describe the values that can be used in a context rule condition.
products:
  - Communications
  - Media
  - Energy and Utilities
release: "264"
---
# Create Context Dimensions

Context dimensions are variables that describe the values that can be used in a context rule condition.

For more information about context dimensions, see [Context Dimensions](https://help.salesforce.com/s/articleView?id=ind.comms_context_dimensions.htm&release=264.0.0&type=5 "Context dimensions are variables that describe the possible values to use in a context rule condition. You can reuse context dimensions across multiple rule conditions. Context dimensions are linked to one or more context mappings. The rules engine compares them to the linked context mappings.").

1. In Vlocity Product Console, in the **Rules** area, next to Context Dimension, click **Create** ![The plus icon for Create](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-ind-comms_media_energy_managed-264-0-0-production-enus/ff4079f6-a384-475c-b863-578bbbb0ef9b/resources-product/images/productconsole_create.jpg).
2. On the **New Context Dimension**tab, enter the following information.
    
    - Name is the context dimension name.
        
        ![Note](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-ind-comms_media_energy_managed-264-0-0-production-enus/ff4079f6-a384-475c-b863-578bbbb0ef9b/images/icon_note.png)
        
        Note
        
        You cannot use spaces in a context dimension name due to rules parsing engine requirements.
    - Code is the code that refers to the rule when creating custom expressions. Use a unique but meaningful code, so that it is easy to read custom expressions. For more information about custom expressions, see [Child Rules and Expression Modes and Custom Expressions](https://help.salesforce.com/s/articleView?id=ind.comms_expression_modes_and_custom_expressions.htm&release=264.0.0&type=5 "When a rule set contains more than one child context rule, you must use the expression mode to specify how the rules engine combines the child rules into a logical expression.").
        
        ![Note](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-ind-comms_media_energy_managed-264-0-0-production-enus/ff4079f6-a384-475c-b863-578bbbb0ef9b/images/icon_note.png)
        
        Note
        
        You cannot use spaces in a context dimension code due to rules parsing engine requirements.
    - **Description** describes the context dimension's purpose.
    - **Condition Weight** helps the TightestMatchInterface weigh rules for price list entries and child price lists. Product and promotion rules do not use condition weight.
    - **Data Type** describes the context dimension data type, for example Text, Number, Date, DateTIme, or Boolean.
    - **Domain Type** describes how rule condition values appear when creating a rule condition.
        
        - **Picklist**: Select rule condition values from a Vlocity picklist.
        - **Object Lookup**: Select a specific record from an sObject.
        - **Type In**: Enter free form strings.
    - **Object** specifies the sObject to look up when the **Domain Type** is **Object Lookup**.
    - **Vlocity Picklist** specifies the picklist to use when the **Domain Type** is set to **Picklist**. If you are using a Vlocity picklist as the domain type, you must create the picklist before creating a context dimension. You cannot use Salesforce picklists in context rules.
    - **Picklist Selection Mode** specifies whether to allow the user to select a single value or multiple values from the Vlocity picklist.
        
        ![Note](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-ind-comms_media_energy_managed-264-0-0-production-enus/ff4079f6-a384-475c-b863-578bbbb0ef9b/images/icon_note.png)
        
        Note
        
        The context rule service supports only single values.
    - **Cacheable Mode**; When this option is checked, cacheable jobs (that is, jobs that populate the API Cache) will use this Context Dimension. If this option is not selected, the Context Dimension will not be cached, and therefore will not available to Digital Commerce APIs.
    - **Default Value** specifies the value that will be used for the Context Dimension (and passed to the Context Rules) when the input context parameters do not have a given value. The value is used in the case of tightest match for price list entries. If this field is left empty, then the value will be passed as null.
        
        ![Note](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-ind-comms_media_energy_managed-264-0-0-production-enus/ff4079f6-a384-475c-b863-578bbbb0ef9b/images/icon_note.png)
        
        Note The Default Value field present in the Context Dimension is used only in the Digital Commerce (DC) APIs.
    - **Values for caching** specifies the list of possible values for this dimension. For each of these values, the Cacheable Jobs (for example, the Populate API Cache job) will cache a response.During runtime, if the input context parameter is passed a value that is not present in this list, the CPQ engine will evaluate the response on the fly and then cache the result.
    
    - **Active** specifies whether this context dimension is active or not.
    - **Effective From** is the start date of the period during which rules can use the context dimension.
    - **Effective Until** is the end date of the period at which rules can no longer use the context dimension.
3. Click **Save**

After creating your context dimension, the next step is to create a context mapping. For more information on creating context mappings, see [Creating Context Mappings](https://help.salesforce.com/s/articleView?id=ind.comms_creating_context_mappings.htm&release=264.0.0&type=5 "Context mappings allow the rules engine to compare context dimensions to data stored in an sObject, calculated using a function, or entered during design time within a specified context scope. Create context mappings in Vlocity Product Console.").

Some example context dimensions include:

- [Create the Originating Channel Context Dimension](https://help.salesforce.com/s/articleView?id=ind.comms_create_the_originating_channel_context_dimension.htm&release=264.0.0&type=5 "These instructions use the Channel_PKL picklist which has been previously created. The picklist has the following values: Web and Retail.")
- [Create the Account Status Context Dimension](https://help.salesforce.com/s/articleView?id=ind.comms_create_the_account_status_context_dimension.htm&release=264.0.0&type=5 "These instructions use the CustAcctStatus_PKL which has been previously created.")
- [Create the Order Status Context Dimension](https://help.salesforce.com/s/articleView?id=ind.comms_create_the_order_status_context_dimension.htm&release=264.0.0&type=5 "These instructions use the XStatus_PKL which has been previously created. The picklist has the following values: Draft and Activated.")
- [Create the Account SLA Context Dimension](https://help.salesforce.com/s/articleView?id=ind.comms_create_the_account_sla_context_dimension.htm&release=264.0.0&type=5 "These instructions use the AccountSLA_PKL which has been previously created. The picklist has the following values: Gold, Silver, Platinum and Bronze.")