The topic in this section describes background processes and case review.
Creation of customer review cases
When a document that has been 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 were acting as a contracting party when the document was 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 a period of 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 create requirement cases for all related parties, including customer B, what enforces the collection of a new version of the document.
The background process that detects the expiration of documents is active by default after the installation of Pega Client Lifecycle Management for Financial Services. 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.
|Rule name||Rule type||Usage|
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 a reference to the access group dedicated to background processes in your implementation.
If, for any reason, you do not want the system to create review cases on the expiration of documents, make a copy of the job scheduler and disable it.
Previous topic Integration points Next topic Upgrading from 1G into 2G