Last April I was at the Creo beta event and got to play with the software.
The issue of standard company mapkeys/menus was one of the issues I brought up with the developers.
To date nothing has change in this regard.
There's two basic problem as I see it.
1. You cannot add menus to the file menu.
2. You cannot add menus that are available regardless of the type of active file.
For example, let's say you have a mapkey that creates a new drawing based on a drawing template. Logically I would add a pick to create a new file, to the file menu and it would be available regardless of the mode you are currently in.
Plotting is another example. I don't create a plotting mapkey for every printer we have, however I do create plotting mapkeys for various types of output and where I want it. For example if you want to output a jpg, by default it will end up in your PDMLink workspace, I have a mapkey that puts it in the file the plot files directory. The print command is under the File menu, so that seems a logical place to place my mapkeys. Once again you want these to be available regardless of the mode you are in.
Creo 1.0 doesn't allow you to add anything to the file menu. Also everything you add to the ribbons is dependent on the mode you are currently in. So a mapkey/menu can't work for both a part and an assembly. Which means you can't have a single consistent pick that loads a model tree config file to change the columns displayed in the model tree.
I applaud PTC effort to reduce the need for users to create their own mapkeys/menus. However let's face it, no matter how easy you make some tasks, there are going to be things for which a user needs or wants a mapkey, and they would like a consistent location to access it in the menus or ribbions.
David Haigh