The thing you need to consider is many of the corporate mapkeys are used in the ribbon file. So that brings up the issue of how do you make sure you have your correct system mapkeys for your system ribbon, and also allow your users to customize their ribbon.
So here is the other thing I do. I don't store the ribbon in the load point. This is because on our other network with no hard drives, I don't want to wipe out the ribbon if I load a new maintenance build of Creo on the server. Also I want to use the same method on both networks, So in my startup script I have these lines:
These are from our network where the computers do have hard drives and Creo is loaded normally on the C: drive.
In this case
I actually have a startup script for customizing the users ribbon. It doesn't load any ribbons. This allows them to make a clean ribbon and then store it in their configs folder.
If your going to do this you need this config option:
I can assure you that you don't want any mapkeys in the config.sup. We figured that out in 1989 when we first started on ProE.
I have 3 lines in the sup. This should be a very small file. If you're putting everything including the kitchen sink in that file, you really limit your flexibility.
Here's a video showing multiple mapkeys in the config.sup working in Creo 3 M060. Notice how it disables my add ISO view mapkey from my config.pro (activated by typing ii) but multiple mapkeys from the config.sup work to change the open menu filter. Every mapkey I put in the config.sup seems to work... I've tested the first mapkey and the last mapkey in the config.sup to check for quirks. Now if they could just let mapkeys in the other config.pro's work in addition to this, admins would have a great tool for a standard set of mapkeys for all of their users if desired... And yes, the config.sup should contain very few settings (we have 3 as well).