Implementing error handling for new and existing modules

From PegaWiki
This is the approved revision of this page, as well as being the most recent.
Jump to navigation Jump to search

Implementing error handling for new and existing modules

Description Implementing error handling for new and existing modules
Version as of 8.5
Application Pega Smart Claims Engine for Healthcare
Capability/Industry Area Healthcare and Life Sciences



Definition and concept[edit]

SCE handles the errors and exceptions raised in all modules, sequences, and orchestrations in one central place. Once an exception is raised the processing of the claim will stop, the exception will be added to the audit log and the claim will be added to the configured error handling workbasket for review; then the processing will continue with the next claim.

Key considerations[edit]

The existing steps and actions for exceptions are required for SCE to work properly. For this reason, while the error handling process can be extended to add new steps and actions, the existing ones should not be removed.

General guidelines[edit]

The CE_MainProcess activity is the activity that calls all modules, sequences, and orchestrations. If any of them raises an exception, this is where the exception will be caught. If a new module, sequence, or orchestration is created, it should raise all exceptions so that they are handled in a consistent way rather than trying to handle the exceptions within the module itself.

Once the CE_MainProcess activity catches an exception it will call the CE_ErrorHandling collection to handle the exception. The CE_ErrorHandling collection has three steps:

  1. Calls the ME_RemoveSubscriberLock Activity which will remove the lock placed on the subscriber during the processing of the claim.
  2. Adds the error to the audit log
  3. Routes the claim to the error handling workbasket for review by calling the CE_ErrorHandling flow.

If desired, the CE_ErrorHandling collection can be overridden to extend its functionality.  Once the collection has been overridden, click on the Rules tab to see the steps mentioned above. You can add more steps as long as the existing steps are kept. If you click the Pre/Post tab you will be able to add actions to be executed before or after the collection.

The CE_ErrorHandling flow comes with only one option for manually fixing the claim.  But it can be extended to automatically correct the claim and send it to be re-processed whenever appropriate if desired.

Figure 1: CE_ErrorHandling Flow