Reassessment Strategy
This setting governs the types of cases that the Engine can reassess.
The supported settings are:
- Automatically reassess all cases
The Engine allows reassessment of all cases and maintains dependency records for each case's assessment for as long as the case is recorded on the system. Over time, depending on the number of cases on your system, the ever-growing number of dependency records can affect the performance of your system.
- Do not reassess closed cases
The Engine allows reassessment of all cases except for those with a status of "Closed". Closing a case removes only the Dependency records relating to eligibility (not advice context, and so forth). The Engine maintains dependency records for each non-closed case. If a case's circumstances change when it is closed, the Engine does not reassess the case (but if the case is reopened, the Engine then reassesses the case).
This setting is the default for new products you add to your system.
If you change this setting for your product, then all existing cases are checked to see if dependency records should be created or deleted.
When a user publishes changes to a product, which include a change to the product's reassessment strategy, then at the point where the user is asked to confirm the publication, the system warns the user that a batch job request is queued up, and that the batch job must be run before the new reassessment strategy takes effect for existing cases.
For each product delivery case for the product:
- if the case was not reassessable under the old strategy but becomes reassessable under the new strategy, then an assessment is performed on the case to build up the dependency records for the case's determination result;
- if the case was reassessable under the old strategy but is no longer reassessable under the new strategy, then the dependency records for the determination result are removed;
- otherwise, no action is performed on the case.