Check-in in rules, stop check-in if criteria isn't satisfied

[Neil_Cross]

Apologies if this is a repeat post, nothing came up on the subject search.

Forgetting data standard, iLogic, or any other methods that require programming knowledge and complicated ancillary file editing.  It would be extremely useful if Vault (probably Pro) could allow an administrator to apply check-in criteria.  I see it as being similar to the category allocation rules, configurable via the Vault Client in the administration options.  E.g.

Document check-in is refused if there is no comment entered into the check-in dialog.

Document check-in is refused if there is no description in the iProperty of the file.

Document check-in is refused if the local file is not generated from a Vault numbering scheme, or does not follow the format a pre-configured naming scheme/standard.

Anything like that would be a good starting point to help us make Vault a better document management system.  There would be stipulations and hundreds of points to consider, such as child file states etc but the idea in principle is something which is lacking in Vault currently.

[YounesYammouri]

Thanks for sharing your Idea. We use this forum to guide product development and help users in the best way we can based on voting. We occasionally merge Ideas or archive old ones to keep the forum working properly- it ensures there is room for people to review new Ideas and that the most relevant and meaningful ones can gain votes.

We’re archiving this Idea because it's been on the board for well over a year and hasn't received many votes from the community and/or not aligned with the current Vault Roadmap. If you want to raise it again and try to gain more support, you're welcome to do so. We’ve found that pictures and mock-ups can help get concepts across and win more votes from other users. If you have questions or see a connection between this Idea and others, let us know.

- Vault product team