Page History

...

• Execution Frequency
  • The days for execution of the service can be specified. If no days are specified then the service will not run and purge of the database remains a task to be completed manually.
  • For each day specified the service will run within the begin and end of the period specified.
  • It is recommended to choose days and periods with relaxed scheduling activity as this will reduce the number of times the Cleanup Service is interrupted by such activity. However, there will be no interference if workflows are executed while the service is running.
• Objects subject to Purge
  • Order History and Task History are purged in a common operation. 
  • Order logs and task logs are stored with the Order History and are purged when exceeding the specified retention period. A frequent use case is to purge logs after a shorter retention period and to retain the execution history for a longer period as logs consume more space in the database. Consider that it makes no sense to use a longer retention period for order logs and task logs than for the Order History as the logs would not be accessible by the GUI.
  • The history of Daily Plan submissions usually is relevant for a shorter period only. It is mostly used to detect if for certain days no orders have been submitted particularly when the Daily Plan is manually managed by a user and is not automated by use of the JS7 - Daily Plan Service.
  • For the Deployment History the number of deployments per object is specified, e.g. workflow, that should be retained. If this number is exceeded then older deployment history entries will be purged.
  • The audit log configuration should be considered with care as it can be subject to compliance requirements.
  • Monitoring History entries and Notification History entries by default are purged after the period of one day as longer periods are infrequently used for the JS7 - Monitor view.
• For further information about configuration and logging see JS7 - Cleanup Service

...