Background processes
After installing Pega Client Lifecycle Management and KYC, the system activates the background process that detects the expiration of documents by default. If you want your organization to make use of it, you must configure the following job scheduler to point to an access group in your implementation.
If you want your organization to make use of the background process, you must configure the following job scheduler to point to an access group in your implementation.
| Rule name | Rule type | Usage |
| RNGCreateCustomerDocExpiryEvents | Job Scheduler | Make a copy of the job-scheduler rule in your application. Configure the frequency according to your need and also the nodes where it should run according to your infrastructure. Replace the reference to the out-of-the-box access group CLMFS_Agents with reference to the access group dedicated to background processes in your implementation. |
Creation of customer review cases
When a document that was used previously to satisfy a given requirement subsequently expires, the system can create a Customer Review journey to ensure that a new version of the document is collected. The system detects in which context the document was used and then creates review cases for those customers who are acting as a contracting party when the document is collected.
For example, during the onboarding of customer A, the system creates a requirement case for a related party B. The requirement is satisfied with a document that expires after some time. When the expiration is detected, the system creates a new customer review case for the contracting party at the time of collection (customer A). The new review case, in turn, creates requirement cases for all related parties, including customer B, which enforces the collection of a new version of the document.
Previous topic Integrating with a DMS system Next topic Upgrading from 1G into 2G