Release 5 functionality

The following list highlights the targeted functionality and changes planned for release 5.

Release 5 is targeted to be published in Q4 of 2025. Contact us if you have any contributions, thoughts, or requirements related to release 5.

Initial release

The first published release of Release 5 will include all the functions and features of Release 4.11.36.80 and convert the technology framework of the Connector to make the context menu functionality compatible with M-Files New_Desktop. This include

  • .NET Framework 4.8

  • VAF 25.3

  • UIX 2

  • M-Files 25

The update include significant changes to logging in the VAF and the operations of the context menu functionality.

This first release will lay the foundation for future improvements in the funcionality and scope of the Connector.

Planned changes

Use doc.lamininsolutions.com as primary source of information

  • redo landing page

  • redo summary of tool

  • Why use it

  • more use cases and practical guidance

Use M-Files Configurations to setup the Connector. This will require a connection from M-Files to SQL. Initially this will be optional until all MFSQL Connector customers have switched on a connection.

  • Set and update MFSettings Table

  • Set and update MFVaultSettings Table

  • Select classes to include in App and automatically create all class tables in SQL

  • Set and update custom Class and property settings

Use Configurations to show MFSQL Connector operational status

  • Listing of errors

  • Process Batch statistics

  • Provide overview of usage of MFSQL in the dashboard

Use Configurations to automate SQL procedures and views

  • custom procedures to update class tables

  • custom views for reporting and analysis

  • Use VAF to trigger the automatic updating of the metadata structure in SQL.

  • Make reporting functionality magic. Automate, ease of use, report in MF.

  • Metadata alignment - improve automation

  • Improve capabilities by grouping them into operations with options. MFSQL Connector Operations

  • Change metadata sync to allow for continious update of metadata without affecting transaction processing.#. Change updating of object change history to update the change history automatically without the need to run through all objects.

  • Change processing of updates to MF to reduce checkin checkout operations and the time it takes to process

  • Convert to the use of JSON instead of XML to avoid the restrictions of XML and improve performance.

  • Change pricing to be more usage focussed

Changes to installation routine

  • install vault App

  • Configure vault app

  • install web service on webserver.

  • install MF on SQL server

  • Check connection to SQL server

  • Execute SQL installation

  • Check connection from SQL to MF