Skip to main content

AutoRecords 25.11

Version 25.11 Release Notes

  1. Event Name Change - Previouly Event Names were automatically created with the date the Event was triggered appended to the name. That has been changed so the Event Name now has the date the Event will execute appended.
  2. Labels & Helptext - All labels and helptext have been updated and now point to online help.
  3. Logging Level Defaults - These defaults have been changed to Counts & Timing to provide the most likely setting Records Managers will need.
  4. Content Pack Validation - AutoRecords checks to makes sure the Content Pack has been upgraded to match the rest of the application. It now generates a user friendly error indicating that the Content Pack has not been upgraded.
  5. Performance Increases - Several performance improvements have been made including improvements to generating Log Files and processes within Step 5, 6 and 9 when handling changed Policy criteria. Additional improvements have been made when processing Indirect Retention categories.
  6. Manual Addition Of Retention Category - Previously the user was able to manually add retention categories to files. This has been changed to eliminate manual addition of a Retention Category to existing documents to prevent confusion and insure data integrity when AutoRecords runs.
  7. Expanded Scheduling - Added the ability to run AutoRecords based on the week or day of the month. For example, the 2nd Saturday of the month.
  8. Disposition Log Enhancement - The disposition log has been enhanced so instead of a single CSV file, it generates a data file along with a formatted Dispostion Log. This provides a ready to view and easy to read format along with the ability to import raw data into other systems or applications. Both files can be imported into Excel depending on the desires of the end user (raw data or formatted report). Additionally, each Policy now has the ability to specify a number of properties whose values can be copied to the Disposition Log.
  9. Audit Logging - A new setting is available in the Administration Utility which provides the ability to enable or disable the recording of subtask operations. This reduces overhead and makes the Audit Log cleaner when it's running in a production environment.
  10. Total Run Time - Added a Total Run Time calculation which is reported in the Audit Log as part of the last step.
  11. Updated Event Template Triggers - Improved the handling of updated Event Template Triggers to increase performance and handle edge cases where updated triggers weren't always causing scheduled Events to recalculate correctly.
  12. Update File Version Handling - Deal with conditions where file versions already exist and need to be removed as part of initial run of AutoRecords.
  13. Revise End Of Years Calculation - The new end of years calculation will not count the current year. A document dated 11/25 with 5 end of years as the retention period, will be processed at the earliest on December 31st 2030. Previously it would have processed December 31st 2029.
  14. Event Template Deprecated - The Event Template has been deprecated. Event Templates were intended to be used for specific reporting situations where each file must be reported individually for audit purposes. Improvements in Disposition Logging and Reporting have made this unnecessary. The Event Template still exists for clients using it, however if you attempt to create a new Event Template you will get an error indicating you should use Event Group Templates.
  15. Bug Fixes
  • End Of Month Scheduled On Leap Year - Clients running AutoRecords at the end of the month using a certain combinations of settings experienced a problem with AutoRecords not running on schedule. The leap year calculation in M-Files framework has been fixed and implemented.
  • Enhanced Required Metadata Detection - Previously if a client installed the vault app but failed to import the associated properties, it would result in errors saying "-1 not found." A clear error message is now presented indicating the issue.
  • Is User Records Manager Error - Previously, there were conditions when M-Files would experience problems with Event Handlers and since AutoRecords uses Event Handlers, the underlying error would manifest as an AutoRecords error when in fact it was a lower level issue within the environment. This has been fixed so the lower level errors are surfaced.
  • Prevent Use Of Soft Deleted Configurations - Previously if selected AutoRecords configurations were deleted but not destroyed (soft deleted) the deleted configuration could be used in certain edge cases.
  • Fix Processing Status Window - The dates and times in the Processing Status window within the Dashboard have been fixed to show the date and time on the server.
  • Step 2 Task Queue Message - Step 2 will now report the correct "segment" that it is processing within the AutoRecords dashboard.