Archiving Applications

Use FICO Application Studio Manager to define the archiving criteria and initiate the archiving process.

The archiving process has a default schedule. Once you set up the archiving criteria, applications will be archived at the scheduled time. You can change the time specified in the schedule or start the archiving process right away. The archiving properties are specified on a per-client basis.

When you archive an application, you also archive all items associated with that application so that you can restore the application at a later date if needed.
  1. Log on to FICO Application Studio Manager with administrator credentials and select Factory > eSpaces.
  2. In the list of eSpaces, click the link for the om_apm_archive_web module.
  3. Click the Tenants tab and select the tenant.
    1. In the Site Properties tab, click the ApplicationNumbersToArchive site property and provide one of the following values:
      • The number of oldest applications to be archived (for example, Oldest:25). The oldest applications are determined based on the date of last activity.
      • A comma-separated list of applications to be archived (for example, OM1000,OM1001,OM1002).
    2. Click Apply.
    3. Click ArchiveFolder site property, provide the relative folder path where archived applications are to be stored, and click Apply.
      The default location for archived applications is /tmp/ApplicationsArchive/. If the Couchbase is enabled, the archived XMLs will be stored in the bucket in Couchhbase .
      Note: Do not store the archived applications in the /tmp folder. Ensure that you change the location for archived applications from the /tmp folder to different or standard location.
    4. (Optional) Click DeleteApplicationAfterArchive, specify whether you want applications to be removed from the active database when they are archived, and click Apply.
      With the default value (True), applications are deleted when they are archived.
    5. The CustomUpdatesFields site property contains a comma-separated list of values in table.field format. Due to the mechanism used to restore application data, some of the field updates for a restore operation must be made at the end of the restore process. These fields are updated at the end of the insert scripts for the affected tables. For example, BaseApplication.ApplicantId specifies that the BaseApplication table's ApplicantId field must be updated in an application after the applicant is created. Your installation may require this if the application data is extended; your Technician will identify the settings for this site property depending on the configuration of your data model.
      The following fields are included by default in the CustomUpdatesFields site property:
      • IncomeExpenseStatement.IncomeStatementId
      • BaseApplication.ApplicantId
      • Application.DecisionPartyId
      • BaseDuplicateCheckBusinessDetected.BaseDuplicateCheckDetectedId
      • BaseDuplicateCheckApplicantDetected.ApplicantOrCoApplicantId
      • BaseDuplicateCheckApplicantDetected.ApplicantIdMatched
      • BaseDuplicateCheckApplicantDetected.CoApplicantIdMatched
  4. In the Timers tab of the tenant, the Archive (om_apm_archive) timer is set up with a default schedule. Archiving will automatically occur at the time specified in the schedule. If you want to change this, you have two options:
    • To start the archiving process immediately, select the check box for the Archive timer and click Run Now.
    • To modify the schedule, click the link for the Archive timer and make your changes on the Timer Archive page for the client.

  • ©2023 Fair Isaac Corporation. All rights reserved.

    • www.fico.com