Setting custom vault data to configure FileCloseBehavior to automatically check in documents on close

I have tried to implement a change of close behaviour so that all documents are checked in automatically when they are closed.  I have done this via a Custom Vault data and adding the below JSON into the Named Value Manager.  We've used other namespaces and these are working but I'm now trying to establish why this particular setting isn't working as expected.  Has anyone been able to force this user based registry key out via the Custom Vault Data Namespace configurations?

{    "Common": {

    "CheckInReminder": {
            "FileCloseBehavior": 0
                }
        }
}
Parents
  • Behavior at file close is a user setting for M-Files Desktop so you cannot modify it from the vault settings. In other words the same behavior is in effect for all vaults the user is connecting to with their desktop client.

    What you can do is set the behavior in the M-Files Desktop Settings and then export the .reg file which you can distribute to client computers for instance via GPO.

  • Hi Joonas, thank you for the above but in our current scenario it doesn't help.  We have some devices that we can't push GPO's to as they are non domain based but we still need to push this key to every user who might sign into M-Files on it.

    There are other user based settings that are pushed out via this method, for instance we set the "ShowSendAndSaveInBuiltInTab" which is also a user setting which creates the registry key via this method so I'd like to understand why one will work and another won't if this is the case?

  • In general:

    Vault-specific settings (i.e. behavior can be different in each vault) can be distributed from Advanced Vault Settings or other such configurations.

    Client settings (i.e. behavior is for the desktop client and the same for all vault connections) such as this one cannot be controlled from the vaults.

    ShowSendAndSaveInBuiltInTab for the Outlook plugin may be a bit of a special case.

Reply
  • In general:

    Vault-specific settings (i.e. behavior can be different in each vault) can be distributed from Advanced Vault Settings or other such configurations.

    Client settings (i.e. behavior is for the desktop client and the same for all vault connections) such as this one cannot be controlled from the vaults.

    ShowSendAndSaveInBuiltInTab for the Outlook plugin may be a bit of a special case.

Children