Ability to dynamically disable custom commands

[thomas_jamnik]

Hello

Ability to dynamically disable custom commands based on the entity selected in the Vault Client. For the user experiance it is not possible to disable custom commands if the selected entity does not fulfill criteria necessary so the command can run.

example: A custom command that wants to edit an entity cannot run if this entity is locked for editing.

example: A custom command may not be able to run if certain UDPs don't have required values.

Interesting thing: The Vault client's build in command Change State is disabled if the selected entity is locked for editing.

BR, Thomas

[ihayesjr]

@thomas_jamnik , Did you post this question in our customization forum? If you are developing custom commands, I believe you can already do this.

[thomas_jamnik]

Hello @ihayesjr 

I did not but I have created an API ticket round about two months ago and I got there the answer that it is not possible. casd-id: 15574683

Of courxe it is possible to deactivate or activate a command during Vault start. But it is still no possible to do this during work flow.

BR, Thomas

[thomas.behrendY5FX4]

That feature would be great. I.e. our Custom Commands has to check if the file is checked-out, if yes from the user and so on.

Pro:

We could show am MessageBox with the exact reason a command is unable to run

Contra:

The same code as before and maybe slow runtimes for the Context Menu because the code has to check stuff and contact the API.

In another Software I´ve created in our company, I´ve used the CommandBinding MVVC concept and the "Validator" if a command is active was a method.

The Commandstyle was pretty easy:

cmdSave = new DelegatedCommand(save, canSave);

public void save(object obj) {}

public bool canSave(object obj) {  }

and the Button has normal Command Binding in the DataContext.

Just an idea how simple it could be and the canXXX Method is optional.

[AttilaFarkas]

Great idea. This important function is still missing from the API 😞