Total multi-language support
M-Files is available in over 17 languages, with multi-language enabled metadata (or properties). For example, one person may be looking for all documents sorted by “Industry Type”, another may be looking for the german equivalent; “Wirtschaftszweig”. Both will see the same results in their language of choice. Switching from one language to another is easy and happens at the client level, meaning that two users in the same room can be working on two different language editions.
It’s easy, just save and tag
Assume you have a proposal dated June 1, 2020, related to a customer of the "Corporation B" and "Website Renewal" project. In a traditional file system, you must choose whether to store the file in the customer, project, or proposals folder. However, in M-Files, you can access the same file through multiple Dynamic Views such as Documents by Customer- Corporation B, Proposals by Month – June 2020, or Documents by Projects – Website Renewal.
M-Files is fundamentally a metadata-driven system where documents and other data entities are classified with metadata instead of traditional folders. Navigation in M-Files is based on dynamics views that are based on metadata. Object permissions in M-Files can be based on metadata so that, for instance, document class and the customer the document is related to define the visibility of the file together. Workflows are strongly metadata-driven, too.
Administrators can easily manage the metadata structure using a centralized console with a simple graphical user interface. No programming or scripting is required. With the system administrator console, it's easy to define new object types, classes, property definitions, workflows, and more. In addition, all common data types are supported, such as text, numbers, Boolean, dates, times, lists, and more.
Beyond simple content indexing
M-Files metadata properties can also be filtered and driven based on the other properties: For example, after selecting a country, the list of cities can be automatically filtered, and once a city is picked, the list of ZIP codes can be automatically filtered. Additionally, metadata properties can have automatic values, from simple auto-numbering to concatenated automatic values. For instance, document naming conventions can be enforced by automatically naming certain document types with a combination of type, date, and generated numbers. Automated validation rules are supported, too (e.g., project number must contain four digits). It's also possible to populate M-Files metadata properties with values directly from your CRM or ERP system. For example, a Customer metadata property can be defined as a pop-down list populated from your CRM; when a new customer is added in the CRM, the list in M-Files automatically updates.