Skip to main content

AutoRecords 1.1

Version 1.1 Release Notes

  1. Multi-Server Mode Support - AutoRecords now supports the M-Files Multi-Server Mode of operation leveraging task queues. Several new configurations have been added to provide configuration around exactly how AutoRecords tasks will be created in the Multi-Server Mode environments. For more information please reference the Administrator Guide.

  2. Performance Improvements, Segmented Searching & Multi-Threading - As part of the Multi-Server Mode change, AutoRecords has changed to use “segmented searches” and multiple threads when it is processing. This along with some changes to processing help to improve some performance issues especially in large environments.

  3. Force Processing Of Indirect Triggers - There are some situations where a Records Manager may with to clear the last run date in AutoRecords and rerun the process for all items rather just for those items that have changed since the last run. When this happened a significant amount of processing could happen if the configuration involved Indirect Triggers. All Indirect Triggers would essentially be reapplied. This flag allows the user to specify whether they want to include Indirect Trigger reprocessing when AutoRecords is re-run.

  4. Chained Events - A new feature has been added which provides a way for Records Managers to easily chain together Events for a Retention Category. By specifying the Next Event To Schedule for an Event Template a Records Manager can more easily chain together events. For example, after Owner Approval the next Event may be to Archive in 30 days. After Archive the next Event may be to Delete. While this was possible before, the new feature makes this type of chaining much simpler and more intuitive.

  5. Event Template Validation - Additions and changes to the Event Templates specified on a Retention Category are limited in terms of what they impact. A warning message has been added to alert the user of the limitations.