It looks like you all have most of it all lined up. Let me try to help with some of the confusing points:
- ES does use the context menu - so if you made a Dashboard that showed that record they could right click there and do the exact same thing. Important point - the concern is not enterprise search it is the context menu
- Those tables in the ICE db… OK so before I was involved the gist of it is someone started to clean this area up unofficially and got as far as creating the tables but their stand alone project died there and has not be renewed - they are currently orphaned tables.
- Context menu. The base context menu ships in a file called ContextMenu.xml yes it is an xml file. You can locate in the Client\Res directory on your box.
- now when you customize the context menu it copies that files contexts into a DB record and applies your modifications to that copy.
- This is a very old pattern that has served Epicor well for decades. And is not how we would do it if we wrote it today in a cloud environment.
If it is tied to a menu item in the normal menu I could see submitting an enhancement request to have it honor the parent menu security. However we would need to be careful because it has worked this way for a very long time and it could spawn a series of - why did I suddenly loose my context menu item from support - that is why I suggest enhancement not bug.
hope this helps with some of the confusion.