Archiving

K2 does not delete or automatically archive reporting data for completed process instances, which means that users can report on any K2 process instances that have ever been run in a K2 environment. This approach does mean that the K2 reporting database will grow over and depending on the implementation approach used for the workflows. The reporting database can grow significantly in a high-volume environment, especially when using InfoPath integration. To mitigate this impact, K2 administrators can use the Archiving section of the workspace to archive reporting data to a separate database. This action will physically move the reporting data for process instances (for the specified period) to a separate database. This action will reduce the size of the K2 reporting database while keeping the history for the completed process instances intact.

For more information about archiving in K2, please refer to the Knowledge Base article KB000322: K2 Archiving.

Archived data will not appear in the standard K2 reports, since these reports only read data from the K2 reporting database. If you need to report on the archived data, you may either create custom reports against the archive database, or use the Restore function in this section to restore the archived data back to the “active” reporting database so that the data appears in the standard K2 reports