Configuring Archived Processes

This page is for system administrators enabling, configuring, and deleting archived processes in self-managed Appian environments.

For conceptual guidance on when to archive or delete processes, see Considerations for Archiving Processes.

Enable archived processes

In your self-managed environment, add the following to customProperties in the Appian custom resource (CR) configuration file, then stop and restart Appian:

1
2
3
spec:
  customProperties:
    appian.feature.isProcessHistoryInKafkaEnabled: "true"

This populates the Process Activity tab in the Monitor view with all existing and newly archived processes after the site restarts.

Map existing archive files when upgrading to Appian 25.2

If you upgraded to Appian 25.2 from an earlier version, map your existing .l archive files to Process Activity by running a one-time script. The create-archive-process-csv.sh script creates a mapping between Process Activity data and .l files using CSV files that the application server imports automatically. Processes archived in Appian 25.2 and later already have this mapping.

To create the mapping:

1. Pull the latest image of webapp from the external registry so the script is present.
2. While your site is running, exec into the webapp pod.
3. Run the create-archive-process-csv.sh script, updating the directories for your environment:

1
$APPIAN_HOME/_admin/_scripts/internal/archive/create-archive-process-csv.sh $APPIAN_HOME/server/archived-process/ /tmp/ $APPIAN_HOME/_admin/shared/archive-process-index/

After the script finishes, confirm it created an empty archive-process-csv-complete.txt file in the same directory. The application server uses this file to recognize that the script completed successfully and to import the generated CSV files.

The script is safe to rerun. Existing CSV files are rewritten line by line, and new CSV files are added if necessary.

Customize default archive interval

By default, Appian archives completed and canceled processes every seven days.

To change this interval, set the server.conf.exec.AUTOARCHIVE_DELAY property in customProperties in the Appian CR configuration file, as described in Configuring the Process Engine Servers.

Configure automated archived process deletion

The number of archived processes can grow rapidly in a busy application. To automatically delete archived processes, add the server.conf.processcommon.AUTODELETE_ARCHIVES_DELAY_DAYS property to customProperties in the Appian CR configuration file:

1
server.conf.processcommon.AUTODELETE_ARCHIVES_DELAY_DAYS: "<days>"

Replace <days> with the number of days after which Appian cleans up archived processes. For example, to delete all archived processes after 90 days, set the value to 90.

Feedback