Skip to main content

Sequences in Smart Claims Engine

In Smart Claims Engine, one or more modules are combined to create a sequence. A sequence runs the modules in the order selected when the sequence is created. This allows for unique configuration of the claim adjudication processing steps.

For example, you might create a sequence in Smart Claims Engine called “Validation processing”. The sequence could be made up of five modules, in the following order:

Sequence illustration

A claim encountering this sequence would enter each of the modules in the defined order. The order is important. In this example, the “Member match” module is placed before the “Policy selection and eligibility” module – because the member must be selected before the appropriate policy and associated eligibility is determined.

Sequences may be reused across multiple orchestrations. Once a sequence has been added to an orchestration, it may not be removed from the Smart Claims Engine application.

If desired, you may extend sequences by calling initialization and finalization rules – these can be used to initialize or finalize any values before or after the sequence is run. 

Sequences produce a result status that is used to determine whether to continue to the next sequence, restart the sequence, restart the orchestration, or stop processing.

 

Check your knowledge with the following interaction.


This Topic is available in the following Module:

If you are having problems with your training, please review the Pega Academy Support FAQs.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best.

Pega Academy has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice