Understand Claim Workflow Rules Runtime

The runtime phase is initiated automatically to evaluate a specific claim against the rules configured during design time.

The process begins when an API call is made to the Rule Evaluation API, specifying the claim and the rule to be evaluated.
The API's first step is to call the Context Service to get the context definition of the object (Claim). This service retrieves the complete, hydrated context definition for the claim object, gathering all necessary data points required for evaluation.
The hydrated claim data, along with the rule definition, is passed to the Business Rules Engine (BRE). The BRE performs the core evaluation, comparing the claim's data against the rule's logic and returning an output (e.g. true or false).
Based on the evaluation output from the BRE, the associated actions are enqueued and executed by the Dynamic Revenue Orchestrator (DRO). When a rule condition is evaluated as true or false, specific actions are triggered.

Example: Claim Transition from Draft to Payment Processing
This example demonstrates how a Product Admin can configure conditions to transition a claim from Draft to either Payment Processing or Under Review.

Did this article solve your issue?

Let us know so we can improve!

Product Area