You are here:
General Terms
Browse through this collection of terms, key objects, and key concepts. This collection is designed to give Salesforce admins, sales reps, and developers a clear and consistent understanding of context service concepts and helps them navigate the Context Service landscape.
- Attributes
- Represents one logical field within a node. You can map this field to fields of actual entities.
- Business Rules
- A set of rules based on which a decision table provides outcomes. The business rules are part of a standard object, custom object, or custom metadata type. A decision table can read up to 100,000 rules.
- Context Definition
- A logical data model with nodes, attributes, tags, and mappings that you must create before you access Context Service at run time.
- Context Hydration
- The process of reading data from actual data sources as defined in context mapping. This data is stored temporarily for use by consuming applications.
- Context Mapping
- A configuration within a context definition that defines the relationship between nodes and attributes.
- Context Service
- Admins use a data abstraction service to create logical data models, and connect the service to various real data sources and entities. Developers can create applications for the logical data model, independent of data sources.
- Context Tags
- A string that uniquely points to a node or an attribute within a context definition. It’s unique within a context definition.
- Custom Logic
- The custom logic must match the decision table to provide outcomes.
- Input
- The fields from the business rules that the decision table uses to evaluate records.
- Input Fields Condition
- A condition for the input fields. The decision table input fields evaluate values against the condition. When the condition matches the value, the decision table provides an outcome.
- Node
- Represents one logical entity within a context definition. You can map this entity to real entities, data model objects, and other objects. Nodes can have relationships between themselves.
- Standard Context Definition
- A context definition that’s shipped with any Salesforce cloud is available to help support certain out-of-the-box applications and processes. Customers can use these definitions but can’t alter them because they’re read-only.
- Cloned Context Definition
- You can create a custom context definition by cloning an existing standard or custom context definition. You can change cloned context definitions, including deleting them. However, definitions that are cloned from standard definitions aren’t automatically upgraded. If you want to keep the definitions in sync, you must upgrade them manually.
- Extended Context Definition
- You create a custom context definition by extending a standard context definition. The custom definition inherits all metadata from the standard definition and is upgraded whenever the original standard definition is updated. Customers can make additional changes to the extended context definitions.
- Operator
- Identifies how values are evaluated against the input field. Select an operator for each business rule field that’s used as a decision table input.
- Output
- When one or more rules match, the decision table returns the field values as outcomes.
- Time To Live (TTL)
- The duration for which the context service keeps the data available for applications to use. For extended, cloned, or custom definitions, you can set the TTL to any value between 1 minute to 30 minutes.
Did this article solve your issue?
Let us know so we can improve!
