Dear M-Files team,
I would like to submit a product improvement suggestion for M-Files regarding the naming of exported files. Currently, the system automatically adds the document ID in parentheses in the file name, which has caused significant operational issues for law firms that use electronic filing systems such as e-Proc (TJSP), since these systems do not accept special characters like parentheses in file names.
The current workaround requires manually applying a .reg file on each workstation to adjust this behavior, but this configuration stops working after every M-Files update, forcing the IT team to repeat the procedure on all machines after each new version. While this configuration is not properly set, users must save the files locally and rename them one by one before filing, which is time-consuming and increases the risk of operational errors.
The suggestion is to implement a native option in the administrative settings (per vault or per installation) that allows defining the file naming pattern used on export, including the ability to enable or disable the ID in the file name, choose the ID format (without parentheses, with a hyphen, or removed), and automatically sanitize special characters that are not accepted by court electronic filing systems. This configuration should persist across version updates, eliminating the need for manual intervention after each update.
It is very likely that other law firms face the same issue, especially with the growing adoption of electronic filing in Brazilian courts. A native feature to address this would bring significant benefits in productivity, reduce rework for IT teams, and ensure better compliance with judicial system requirements, while remaining aligned with the document management best practices that M4Law itself promotes.
Thank you in advance for your attention and for considering this suggestion in your product roadmap.
