Improve the efficiency of sharing and using business application data with Context
Service. This service helps your business users boost application performance by optimizing data
access and eliminating redundant inputs. When an application requests data, Context Service
gathers all required information from the database and loads it. It then delivers the necessary
data to the appropriate processes to meet the application's needs.
Insurance Claims Management supports two prebuilt context definitions. A context definition
defines the relationship between the nodes and the attributes within each node. Your users can
use nodes and attributes to easily access the relevant data from the mapped data source. Both
context definitions provide a structured extensible framework that maps relationships between
various sObjects. The context service efficiently manages and interacts with Claim data,
enabling services to access, save, and modify mapped source data during transactions. Users
can extend these standard contexts to include specific details tailored to their unique
business needs, providing flexibility and comprehensive data handling.
Claims Context: Within this context, the SalesTransaction context
nodes are mapped to Claim, ClaimAttribute, ClaimItem, ClaimItemAttribute, and
ClaimItemRelatedObject. The Standard Configurator searches for SalesTransaction context
nodes during the execution of claim workflow rules. This context is used during business
processes such as the FNOL process, creating, updating, and retrieving claims, as well as
for claim workflow rules.
Policy Limit Context: This context maps relationships for the
InsPlcyLimit and InsPlcyLimitTracking sObjects. This context is used during the execution
of default expression sets to calculate claim adjustments and process limits.
We use three kinds of cookies on our websites: required, functional, and advertising. You can choose whether functional and advertising cookies apply. Click on the different cookie categories to find out more about each category and to change the default settings.
Privacy Statement
Required Cookies
Always Active
Required cookies are necessary for basic website functionality. Some examples include: session cookies needed to transmit the website, authentication cookies, and security cookies.
Functional Cookies
Functional cookies enhance functions, performance, and services on the website. Some examples include: cookies used to analyze site traffic, cookies used for market research, and cookies used to display advertising that is not directed to a particular individual.
Advertising Cookies
Advertising cookies track activity across websites in order to understand a viewer’s interests, and direct them specific marketing. Some examples include: cookies used for remarketing, or interest-based advertising.