As of this writing, we are still in the implementation phase. I have built a nice solution that allows us to store “canned” Comments text “blurbs” in the UD04 table. There is only Key1 which is a four digit integer. In Menu Maintenance I assigned it the ID CustCmnt.
Next, I modified the Comments tab on the Customer Maintenance screen to have UD fields to store up to five comment numbers to any given Customer.record. There are other bells and whistles, but this is sufficient to understand what is needed to introduce an “Open with” option on the context menu when right-clicking any of the five UD field text box values. The text boxes are named tbxComment1 through tbxComment5.
tbxComment1 has an EpiBinding of Customer.CmntCode1_c. The Like property and EpiContextMenuKey property is “UD04.Key1”. EpiKeyField is False. The other four are only different in their EpiBinding and Name properties. I would also like to add that I created a nice Quick Search tied to a BAQ which shows up correctly on the context menu when right-clicking.
Like many others, I found Context Menu Maintenance afterwards. Of course, since the above modifications did not provide the Open with option, I was excited to learn about this program. I created entries for Customer.CustCmnt1_c through Customer.CustCmnt5_c, each with a Base Form Process ID of CustCmnt.
Unfortunately, I still have no Open with option on the context menus.
Context Menus options are driven by the “Like” value and not by the Column reference of the field. Consider the Context menu for Part (Part.PartNum) - it is driven by the Like value on any field that stores Part IDs and we do not have a separate Context Menu reference for each PartNum field in the system. Based on your writeup, you should create an entry in Context Menu Maint for UD04.Key1.
Now, that said, launching UD04 Entry from the Context menu may not do what you expect as the UD Forms are wired for 5 Keys.
BINGO! Thanks Rich, that straightened everything out. It’s good to see you’re still in the Epicor family.
To Summarize, I deleted all Context Menu Maintenance records for Customer.CustCmnt1_c through Customer.CustCmnt5_c, then created a new record for UD04.Key1 specifying CustCmnt as the Base Form Process ID. I then verified via Screen Customization that the five Text Boxes for Customer.CustCmnt1_c through Customer.CustCmnt5_c had UD04.Key1 as the Like property.
Once that was done, right-clicking any of the five text boxes does not show “Open with…” but it does show Customer Comment Maintenance as the top option. I suspect that this is because there is only one Form specified for UD04.Key1, and is definitely more efficient.
Ha - you have opened the door for a discussion on a usability option defined in the Client Sysconfig file: ContextMenuNestingLevel.
By default, the ContextMenuNestingLevel is set to 0 which means that if there is only one option in the Context Menu for a Like, we will display it in the initial Context Menu. If there is more than one option, we will add the “Open With” and all options will be in a secondary “overflow” list. If you set the Nesting Level to a value of 4, we will display up to 4 Context Menu options in the initial Context Menu. If there are more than 4 Context Menu options, we will display the top 3 in the initial Context Menu with a fourth option of “More…” which then opens the secondary overflow option list with the remaining options.
As you noted, having some of the more commonly used Options available on the initial Context Menu can provide a minor productivity gain for the user with the minor downside of making the initial Context Menu deeper. I suggest a ContextMenuNestingLevel of 3 or 4 will give your users the most commonly used Options on the initial Context Menu while not extending that list too much.
Is it possible to add modifications to Context Menu Maintenance to a Solution? We have to manually re-enter the two Base menu options whenever we refresh our Sandbox account.