How to disable an openwith menu specific to tab panel within the Salesperson workbench tracker screen

Epicor ERP 10
1

Is there a way to disable the Openwith pop-up menu using C# code or/and a specific sub-menu item on the Openwith pop-up ?

Sales workbench3
Sales workbench3.png774×775 70.3 KB

I know how to lookup the main menu items for the target tracker screen and disable the action menu but not the Openwith menu and sub-items:

	// Examine display main key for all Menus:
	var obj= MainController.GetType().InvokeMember("ToolManager", BindingFlags.Instance | BindingFlags.GetField | BindingFlags.NonPublic, null, MainController, null);
	var tools = (Infragistics.Win.UltraWinToolbars.UltraToolbarsManager)obj;

	// Commented out because this only need to explore all the menu key IDs.
	
	string toolnames = "";
	foreach(var t in tools.Tools)
	{
	    toolnames += t.Key +" , ";
	}
	
	MessageBox.Show(toolnames);
2

The end goal is if possible to disable open with on an order using a define security group on order entry or the process context menu. But disallowing the order entry menu item using a security group is not the same on the calling process menu?

3

I think I figured this out. I will update the post with snapshots just incase someone needs it in the future.

4

During my initial testing for the Salesperson Workbench, the Action menu item and Openwith Order Entry traced process calling Menu ID does respect the assigned security group. I tested this from the EpicorTraining DB. I will proceed with this method and keep you posted. I should note this method does not required any code customization within the target form. I think as long as a defined MenuID associated with a SEC code is called by the parent process, and not a business object (DLL or others) , the security group method should work.

Openwith sales order:
menu1

Actions menu Order Entry:
menu2

Menu security:

menu3
menu3.png1054×692 82.7 KB

5

Just curious why wouldn’t you just remove access to the Order Entry program for these users and then the Open With option will not get them anywhere.

6

As you can see from the earlier snapshots, the OpenWith will utilize a different Menu ID than the Action Menu or possible the Add button. However, in this case they both Menu IDs share the same security code. As this MAY NOT be the case all the time. You need to make sure all referenced MenuIDs are sharing the same security code so when you make the change to disallow/allow by security group it will apply to all appropriate MenuIDs sharing the same security code. .

Note, this method will only work if the parent form is calling a MenuID process and not a direct business object (BO). Furthermore, after clicking on the still visible Button, Openwith menu item, or Action menu item, the user will notice the pop-up message “Your account does not have access to this Menu ID”.

7

Using C# code method allows mea bit more control. I can make the Menu ID or button invisible based on a granted security group to the user account. As a result, the user will not see the button or menu id to click on it.