Loading
Connect in real time with the Trailblazer Community in Slack Open BetaRead More
Workflow of Warranty Claim Adjudication Process

Workflow of Warranty Claim Adjudication Process

To set up a warranty claim adjudication process with scalable and comprehensive rules, use Flow Builder, Business Rules Engine, and Context Service. Learn how these capabilities work together, the key steps in a typical adjudication process, and the decisions to be made before building the process.

Required Editions

Available in: Enterprise, Unlimited, and Developer Editions

Learn About the Capabilities of an Adjudication Process

Understand the capabilities that you can use to build an automated adjudication process.

  • Context Service: Context Service enables easy retrieval and consumption of information in tools such as Business Rules Engine. It comprises context definitions, which is a structured set of data required to execute a process. Warranty Lifecycle Management has a predefined context definition called Claim Detail that can be used in adjudication processes. See Context Service.
  • Business Rules Engine: Business Rules Engine is a suite of components, services, and objects that are used to automate complex decision-making processes. Expression sets are the key components in the Business Rules Engine and consist of a sequential set of steps to run a process. In an expression set, you can add step elements to decide the operations to be performed, and can add variables and constants as placeholders for values. See Business Rules Engine .
  • Flow Builder: Flow Builder is a declarative tool for building complex workflows. Elements in a flow can run various actions, such as aggregate data, create or update records, and assign values to resources. See Flow Builder.

How do the different pieces fit together? You can use Context Service to consolidate all information related to a warranty claim, and pass the information into process automation tools. Use Business Rules Engine components to validate claims against eligibility rules, to determine approved claim expenses, and to decide their approval status. Use flows to invoke the Business Rules Engine components, to update the relevant claim records, and to perform other actions.

Explore the Key Steps in a Warranty Claim Adjudication Process

Review the key steps in a warranty claim adjudication process built by using the predefined Claim Details context definition, an expression set, and a record-triggered flow.

  1. Experience Cloud users, warranty adjudicators, or an automated process create warranty claim records.
  2. When a Claim record meets the predefined conditions, a flow is triggered. For example, a flow can be triggered when the status of a Claim record is Submitted and the claim type is Warranty Claim.
  3. To retrieve all information related to a Claim record, the flow invokes the Build Context invocable action. The invocable action consolidates and caches the claims data associated with a context definition. The cached claims data is used in succeeding steps.
  4. The flow invokes an expression set and passes the required input values to the expression set.
  5. The expression set validates the warranty claim by using business rules. It passes its output values—such as the adjusted amount in a claim coverage payment detail record or the status of a claim record—back to the flow.
  6. The flow performs operations based on the values from the expression set. For example, if a claim is rejected, the flow updates the status of the claim record and emails the claim participants.

Determine How Claims Data is Passed into Expression Sets

Warranty Lifecycle Management has an extensible data model to store warranty claims information. Before you build an expression set to specify adjudication rules, decide how data is passed from the claims objects to expression sets. You can choose one of these options, or do a mix of both.

  • Use Context Definitions: Add context tags from the predefined Claim Details context definition to expression sets. A context tag acts like a local variable in an expression set. To populate a context definition with the information about a specific warranty claim, add the Build Context invocable action to a flow. Clone and modify the predefined context definition if you’ve extended the claims data model or have other custom requirements. See Context Definition for Warranty Claims.
  • Use Object and Field Aliases: Add fields from objects as variables in expression sets. To use field aliases, first create object and field aliases of the Warranty Claim usage type. See Create Source Field Aliases.
 
Loading
Salesforce Help | Article