How to restrict access to individual arguments?
Example:
If you just want to remove the ability to snooze on all Managed Entities rather than the whole 'Until severity changes' snooze command, you need to remove the permission to the AllMe options and re-instate the new command which will execute the single instance option.
The example in figure 1 contains a User account with the AllMe options removed and a new commandGroup which re-instates their single instance equivalents onto the xpaths where they didn't exist before. The only exception to this is the /SNOOZE:untilValueChanges command where there doesn't appear to be a single instance option, so this one selection still throws up the option for all managed entities.
Removing the popups
You can improve on this further by removing the popup which appears each time (if this is undesirable). It works on all snooze commands including the /SNOOZE:untilValueChanges. The solution is basically the same in that the User permissioning section applies none to all the AllMe commands, but instead of creating your own commands which invoke the single instance option, you create your own commands that invoke the same ALLMe ones again, but this time provide the answer to the argument as 'this' i.e it forces it to use the first 'this managed entity only' argument. If you have tried this already you will notice that an annoying pop up output window appears. This can also be prevented by ticking 'silent'.
An example for the snooze manual can be found in figure 2.
You need to go to the GSE help and look at "Appendix: Internal Commands" to check which argument number to provide the selection of 'this' to as it isn't always argument 5 (e.g snooze timeAllMe takes 'this' as argument 6)
Related articles:
Can commands be disabled or restricted for certain users?
Comments
0 comments
Please sign in to leave a comment.