Cleanup tasks that remove temporary system data

The following cleanup tasks permanently remove system data and temporary files from the database. The organisation’s original data is not affected.

None of the following cleanup tasks can be configured.

Cleanup task: Permanently remove partially created PDF files

The cleanup task deletes PDF files that failed during generation in F2 and are therefore only partially created. Documents are automatically converted to PDF files in F2, so they can be displayed in modules such as F2 Manager and F2 Manager 2. Partially created PDF files are not accessible in the user interface. The cleanup process therefore only takes place on the server.

The cleanup task permanently deletes partially created PDF files when they are more than 24 hours old. The task does not remove original data.

The cleanup task cannot be configured.

Cleanup task: Permanently remove temporary copies of documents

The cleanup task permanently removes temporary copies of documents from the database that F2 created to optimise performance when generating reports.

Temporary copies are not accessible in the user interface. The cleanup process therefore only takes place on the server.

The cleanup task permanently deletes temporary copies when they are more than 24 hours old. The task does not remove original data.

The cleanup task cannot be configured.

Cleanup task: Remove expired user sessions

The cleanup task removes user sessions that have expired.

When a user logs in to F2, F2 creates a user session. This means that a log is created in the database of the user being connected to F2. When the user logs out of F2, the session expires.

The cleanup task deletes expired user sessions on the same day they expire.

The cleanup task cannot be configured.

Cleanup task: Remove expired document locks

The cleanup task removes document locks that have expired or no longer exist.

F2 creates a document lock on certain elements when a user opens and edits them. The document lock prevents other users from editing the same element simultaneously.

The following elements are locked with a document lock when a user edits them:

  • Records

  • Comments in an approval process

  • Case templates

  • DBAppSettings (the "F2 settings" dialogue).

The cleanup task removes expired document locks. A document lock expires after 12 hours by default. Hereafter other users can "take over" the lock and edit the relevant element.

The cleanup task deletes expired document locks on the same day they expire.

The task also removes document locks without an existing user session. The absence of a user session means it has been removed by the cleanup task Remove expired user sessions.

The cleanup task cannot be configured.

Cleanup task: Remove document locks for deactivated users

The task removes document locks created for a user who has been deactivated. See Remove expired document locks for a description of document locks.

The cleanup task deletes document locks from deactivated users on the same day as the user is deactivated.

This cleanup task cannot be configured.

Cleanup task: Remove expired statuses from the Metadata Remover module

The cleanup task removes statuses used by the Metadata Remover module when they have expired. Read about the Metadata Remover module (documentation available in Danish). Statuses from Metadata Remover expire when the documents cleaned by the module have been sent.

The cleanup task deletes expired statuses from Metadata Remover on the same day they expire.

The cleanup task cannot be configured.