---
schema_version: "1"
id: 2981dfe0b067cfe14df7809e33a1662a4ee562b1ddc802571f2ea5fd5c655f2b
title: Context Service
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/release-notes/262-0-0/rn_ctx_intro.md
canonical_url: https://help.salesforce.com/s/articleView?id=release-notes.rn_ctx_intro.htm&release=262.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: 0ef6e9a3bbf21c7dcbac4bb62150b2a45a0f985e38b21d11bf1fe31ab2960bff
description: Streamline automation with Apex classes generated from your context definitions to mirror metadata in Salesforce Flow without coding. Build more complex data structures with increased design-time limits for nodes and attributes. You can also use Data Processing Engine to apply complex logic, such as hierarchical rollups, directly to your context data for use cases such as document generation.
products:
  - Cross Cloud
release: "262"
---
# Context Service

Streamline automation with Apex classes generated from your context definitions to mirror metadata in Salesforce Flow without coding. Build more complex data structures with increased design-time limits for nodes and attributes. You can also use Data Processing Engine to apply complex logic, such as hierarchical rollups, directly to your context data for use cases such as document generation.

- **[Generate Apex Classes for Context Definitions](https://help.salesforce.com/s/articleView?id=release-notes.rn_ctx_flow_with_apex_for_context_definitions.htm&release=262.0.0&type=5)**  
    Create Apex classes from context definitions to mirror your definition's metadata and hierarchy in Salesforce Flow without coding.
- **[Boost Design-Time Scalability with Increased Context Definition Limits](https://help.salesforce.com/s/articleView?id=release-notes.rn_ctx_guardrails.htm&release=262.0.0&type=5)**  
    Build and manage more complex data structures with increased design-time limits for context definitions. You can now include up to 80 nodes per definition and up to 1,600 attributes per definition. Additionally, the limit for attributes per node is now 600, and you can create up to 5 levels of hierarchy in a context definition structure.
- **[Transform Context Data at Scale with Data Processing Engine](https://help.salesforce.com/s/articleView?id=release-notes.rn_ctx_dpe_integration.htm&release=262.0.0&type=5)**  
    Enhance your business processes such as document generation by using the power of Data Processing Engine (DPE) to transform context data. Use DPE to read data directly from context objects, apply complex logic such as hierarchical rollups or groupings, and write the results back to a JSON structure.
- **[Categorize Transformation Definitions with the Context Service](https://help.salesforce.com/s/articleView?id=release-notes.rn_ctx_dpe_integration_processtype.htm&release=262.0.0&type=5)**  
    Keep your transformation definitions separate and manageable within the broader Data Processing Engine (DPE) ecosystem. By associating definitions with the Context Service process type, you get more control over custom rules, validations, and row limits. When you create a transformation definition from a context definition, it automatically uses the Context Service process type. You can also select Context Service from the Process Type dropdown when setting up a definition manually in DPE.
- **[Build Precise Context Filters with Custom Filter Logic](https://help.salesforce.com/s/articleView?id=release-notes.rn_ctx_custom_filter_logic.htm&release=262.0.0&type=5)**  
    Combine context filter conditions with nested AND and OR logic instead of a single operator across all conditions. Reference each condition by its row number in an expression such as 1 AND (2 OR 3), the same way you filter Salesforce reports and list views. Custom filter logic helps you hydrate exactly the data your context definitions need.
- **[Add Multiple Sort Order Conditions in Context Filters](https://help.salesforce.com/s/articleView?id=release-notes.rn_ctx_multiple_sort_orders.htm&release=262.0.0&type=5)**  
    You can add two sort order conditions in your context filter.
- **[New and Changed Context Service Objects](https://help.salesforce.com/s/articleView?id=release-notes.rn_ctx_new_and_changed_objects.htm&release=262.0.0&type=5)**  
    Do more with these new and changed Context Service objects.
- **[New Invocable Actions for Context Service](https://help.salesforce.com/s/articleView?id=release-notes.rn_ctx_new_invocable_actions.htm&release=262.0.0&type=5)**  
    Do more with these new and changed invocable actions for Context Service.
- **[New and Changed Context Service APIs](https://help.salesforce.com/s/articleView?id=release-notes.rn_ctx_new_and_changed_apis.htm&release=262.0.0&type=5)**  
    Do more with these changed APIs for Context Service.
- **[Context Namespace](https://help.salesforce.com/s/articleView?id=release-notes.rn_ctx_apex_context_namespace.htm&release=262.0.0&type=5)**  
    The Context namespace has this new method.