MOB explorer won't help as the context action are not registered in the MOB. The initial list of actions is hard-coded in the plug-in, and once you do some modifications (eg. add or remove a context action), the changed list is persisted locally on the machine where the Web Client is deployed/running.
There are several ways to get rid of such orphaned context action, some of them easy, other a lot harder. Below are the easier ones.
If you have a copy of the workflow on some other vRO instance, the easiest way would be to export it from there, import it on vRO instance you use with the Web Client, and remove the context action binding from the UI.
If you don't have a copy of the workflow, you can try the following:
- SSH to vSphere Web Client appliance and stop vsphere-client service
- Delete the file /storage/vsphere-client/SerenityDB/serenity/ALL/applications/vco-plugin/context.menu.actions (you may make a copy of it just in case)
- Start vsphere-client service (or reboot vSphere Web Client appliance)
After these steps, all custom context action mappings should be gone, including the orphaned ones.
