M-Files Essentials
M-Files Essentials is one vault application holding eighteen small utilities. Each one does a job that comes up in nearly every vault and that M-Files has no built-in answer for: naming an object automatically from its properties, copying a value from one object to another when something happens, reminding someone that a workflow state is overdue.
They are independent. Switching one on has no effect on the others, and a deployment that uses two of them is as normal as one that uses ten.
Where to begin
Section titled “Where to begin”What is in this documentation
Section titled “What is in this documentation”| Section | What it holds | Written for |
|---|---|---|
| About | How a utility is switched on, and what to watch when several are | Anyone evaluating or about to configure it |
| Set up | Install, licence, and the first utility — in order | The partner doing the deployment |
| Configuration | Reference for every setting of every utility | Whoever is editing the configuration |
| Troubleshooting | Symptom, cause, fix | Administrators and support |
Requirements at a glance
Section titled “Requirements at a glance”| Current version | 0.26.6.1 |
| Minimum M-Files version | 23.6.0.0 |
| Licence | Per vault, applied as a .lic file |
| Other CtrlDocs products required | None |
The two collections
Section titled “The two collections”| Collection | What the utilities in it act on |
|---|---|
| Object utilities | Objects and their properties — names, identifiers, references, validation, published copies |
| Workflow utilities | Workflow states — due reminders, how long something has been somewhere, comments, holds |
What it needs from the vault
Section titled “What it needs from the vault”That depends entirely on which utilities are used. Every utility names the object types, classes and properties it works on, and none of them is required by the application as a whole — the utility that is switched off needs nothing. Each utility’s page lists what it binds.