DSS to increase or decrease the time for keeping cases excluded from archival

General
, ,
1

In our process we need to archive resolved cases.

Cases resolved with status Resolved-A must be archived after 2 years

Cases resolved with status Resolved-B must be archived after 5 years

To achieve this requirement we want to use the standard archival policy but it seems that it is not possible to set multiple policy for a single case type.

So we want to exclude the Resolved-B cases from archival for 5 years but it seems that “Pega Platform keeps cases on exclusion for a default of 365 days” (Viewing case archiving statistics and log file entries | Pega)

Also : “If you need to increase or decrease the time for keeping cases excluded from archival, change the number of days in dynamic system settings.”

In our case we need to increase the time for keeping cases exclude, but I cannot find the dynamic system settings

Does anyone know this dynamic system settings ?

Regards

Philippe

2

Hi @Philippe Marlier,

The Log-ArchivalSummary class holds 365 days worth of archived cases. Entries older than this number are trimmed from display. To change the number of days that the class holds entries, use the TrimLog activity.

  1. Open the TrimLog activity:
    1. In the navigation pane of Dev Studio, click Records > Technical > Activity.
    2. In the Activity Name column header, click the Filter icon, and then, in the Search Text field, enter TrimLog.
    3. Click Apply.
    4. Click the TrimLog activity.
  2. Select Actions****Run.
  3. In the daysAgo field, enter the number of days that you want to hold Log-ArchivalSummary class entries.
  4. Click Run.

For further details please refer this link :

Hope it helps.

Thanks

Megha

3

@Megha007 Thank you for your answer.

I was a bit confused with that part : “Pega Platform keeps cases on exclusion for a default of 365 days”

As the documentation refer to Log-Archival, I assume that cases are still excluded after 365 days, but the logs are trimmed and as you said, it is possible to update this behavior with Trimlog activity.

It’s clear now.

Regards,

Philippe