IssueTracker

Hi,

I am encountering an issue with Vault and Vault API. It is in relation to how Vault deals with the existing matters. Previously, Vault API did not allow two matters with the exact same name, which was great as the entire thing from user perspective is running on unique names and that worked, but recently I noticed that this changed for some reason and it is allowing multiple matters with the exact same name to be created.

This causes a lot of problems when trying to manage these matters using the automation. This is because Vault API sees multiple matters, whether they are in Open, Closed or Deleted state, and comes to an expected problem of not knowing which matter to deal with since there is more then one and it is not unique anymore. I experienced the same issue using the GAM tool that utilizes the Vault API.

I understand that running matters with the a unique ID makes some kind of sense for backed engineering, however, this makes no sense to anyone else using Vault, as all companies are running holds and matters using unique names for recognition, not unique backend IDs only recognizable on one system.

Is it possible to fix this to how it was running before and having Vault API checking if the Matter name is unique amongst matters, and if the Hold name is unique in the specified matter? This would make Vault API utilization a lot easier.

Please let me know if you need any further information to help with this.

Thank you for your time on this in advance!

Kind regards,, Ivan