Removing/Adding action buttons from VR Workspaces

[Joe Kline]

I attempted this in the SecOps forum post, and recieved a link to this forum to maybe get a more direct assist ... thanks in advance if anybody can boil it down for me.

I tried searching for previous questions and answers related to customizing the Action buttons on the Workspaces within VR (I want to remove "Close", "Mark as False Positive", "Rescan", and "Request Exception" for the moment - then will want to add our own "Defer" and "Request an Exception" where our customization that sends the user to a Catalog Item to submit RITM's to our group) .  Found one over in SecOps forum that seemed to match my issue exactly, but the solution was self-found that we need to adjust UX Actions rather than UI Actions, with no details.  I have attempted to deactivate the Mark as False Positive button on the VIT list page within the Vulnerability Management Workspace, within the UX Form Actions, however the buttons are still visible and active on the workspace.  I have also since deactivated in the UX Form Action Layouts related lists.  The same did not work for me on the Request Exception button.

Any advice on which documentation clearly shows how to do this, or training module that clearly shows how to adjust this, or advice from those that have actually tried and succeeded doing the same?

We are trying to turn on these workspaces now but need to match the deferral processes and button choices to match the customizations we made in the UI16 mode our users and approvers use today.

Thanks, in advance, for any definitions of steps or reference to the documents that show how to do what I thought would be an easy turn off, and turn on buttons.

Appreciate your time,

Joe 

[Nick Erkens]

For removing buttons in a workspace, got to the All menu: Now Experience Framework -> Declarative actions -> Form actions.

In the list, search for the Button you want removed and set "Enabled" to false.

[Dibyaratnam]

you have to check List Actions, Related List Actions , Form Actions and accrodingly as per your requirement you can hide those by deactivating them. Also make sure you clear the cache of the instance after doing the changes. In some cases this resolve the issue.