The Back4 cleanup process, if enabled, runs at fixed intervals, specified in the Interval box. The process does the following:

•Purges all the objects without an explicit purge date-time and deleted since longer than a specified time span (default: 365 days)

•Collects all the objects that have an expiration date in the past and either delete them or apply the expiration workflow (depending on what is specified on the Expiration Rule).

The cleanup process configuration is in back4config.xml:

<!--

      Back4 Cleanup Process configuration

 

      PollingDelay

        Time to wait between each cleanup (timeSpan).

        Default: 04:00:00     (4 hours)

        Minimum: 00:01:00     (1 minute)

 

      Priority

        The priority of the tasks generated for each cleanup process

 

      ObjectsPurgeTimeSpan

        Objects without an explicit purge date-time and deleted since longer than a specified time span will be deleted.

        Default: 365.00:00:00 (365 days)

        Minimum: 1.00:00:00   (1 day)        

        

      Profile

        The execution profile for the tasks created.

        Default: "" (use the default profile values)

-->

  <CleanupProcess

    PollingDelay="04:00:00"

    Priority="10"

    Profile=""

    ObjectsPurgeTimeSpan="365.00:00:00" >

  </CleanupProcess>

LoginLastAccessTimeSpan

When Back4 call the cleanup process, this attribute is used for check the column gn_LoginAccess in gn_LoginTable.

If the gn_LoginAccess data is older than the difference of current time and LoginLastAccessTimeSpan the correlated Login will be eliminated, recovering them and then executing on them the normal log-out process.

The default value of this attribute is 30 minutes.

To use this feature it is necessary uncomment the CleanupProcess values into Back4Config.xml and update the configuration.