Pausing background processing
To avoid inconsistencies and data integrity issues during the manual import, pause any background process that might trigger the running of rules before the update is complete. Otherwise, the application might start running rules before the new rule base is consistent and ready for use.
Review the following background processes that are provided and active by default, and that might be in use by your application.
Type | Process | Description |
Agent (Standard) | PegaCLMFS:FSEventQueueConsumer | Processing of EDA events |
Agent (Standard) | PegaCLMFS:CreateCustomerReviewEvents | Identification of customers subject to customer review due to the next review date |
Agent (Standard) | PegaCLMFS:CreateCustomerDocExpiryEvent | Identification of customers subject to customer review due to expiration of documents |
Agent (Standard) | PegaCLMFS:GenerateAndAttachPDF | Generation and attachments of PDF file representation of KYC questionnaires |
Job Scheduler | RNGCreateCustomerDocExpiryEvents | Identification of customers subject to customer review due to expiration of documents (2G) |
Queue Processor | RNGDMSOutboundSync | Propagation of document metadata to external DMS systems |
Queue Processor | AsyncProcessing | Background execution of cases queued for asynchronous processing (immediate) |
Queue Processor | AsyncProcessingDelayed | Background execution of cases queued for asynchronous processing (delayed) |
Queue Processor | SyncUpPoint | Synchronization and data propagation of Group Management cases after completion of related cases |
Queue Processor | SPUCore | Detection of changes in regulatory rules and propagation to cases (SPU) |
Queue Processor | SPUMaster | Detection of changes in regulatory rules and propagation to cases (SPU) |
Consider any other background process or inbound flow that your organization might have implemented and that might trigger the execution of logic. For example, processes of this type might be the remote creation of cases through Pega API or the reception of events through data flows.
Previous topic Preparing your environment Next topic Backing up your system