I'm trying to roll out corporate wide mapkeys that will supersede users mapkeys if they have the same name to avoid users calling and saying the standard mapkeys aren't working (similar to to config.sup vs .pro but that discussion is closed and written in 2012). We're using Creo 3 M060.
I've created a trail file that for opening Creo and setting the mapkey.pro file I created and have attached it to the icon. After clicking on the icon... Creo opens, mapkeys load fine but it disconnects all the Windchill servers. Normally when starting Creo at our company, Creo prompts users to sign into Windchill (I think b/c our start parts in our config.pro are in Windchill). This Windchill sign-in menu selection doesn't appear in the trail file so I can't have the trail file click ok. The servers are just missing not just 'working offline'. Removing the trail file from the Creo start icon brings the servers right back.
I've tried using long (full start up sequence with loading mapkey.pro) and short (only load mapkey.pro steps) trail files.
Is there a way around this? Or a different method for superseding users mapkeys? I could make a mapkey called 'load' for users but that doesn't work great with the creo_parametric_admin_customization.ui mapkey menu I made on a separate tab and requires users to remember to type 'load'. The config.sup unfortunately isn't a good option for mapkeys (I wish it was) because then users can't create their own mapkeys.
I don't have experience with Windchill, so I'm not 100% certain how this will apply in a WC environment.
That said, Creo loads config files from 3 places (maybe others with WC):
If you place your user's config file in one of the first two and your company file in the 3rd, your company mapkeys will take precedent.
Here, the company files go into #1 and the user files in #3. If a user made a mapkey that overrides one of the company mapkeys, I'd tell them they either have to change theirs or not use the company mapkey (our company mapkeys aren't critical to use, they just make life easier).
Do you have DM_REMEMBER_SERVER set to YES in config.pro or config.sup?
The trail file when starting Creo is doing something to disable Windchill, so it may not be recorded properly.
One method is to name all corporate mapkeys with the same letter or two, then the unique 1/2/3 character mapkey name. this will make the names longer, but insure that all of the corporate ones get loaded.
When I had remote access to users machines, I would examine their config.pro files and comment out lines that conflicted with the system mapkeys or options that we wanted to enforce, yet not put in config.sup.
Config.sup is not the place for any mapkey<period>.
I don't think you are going to find the perfect solution here. If a user wants to override the company mapkeys there is going to be a way to do it.
To piggy back on Doug's idea above the 3rd folder could be a network read only folder which would prevent users from changing the mapkeys. Users could always just change the start in location on the shortcut though (or launch Creo without a shortcut).
Another idea is to have a script that the shortcut launches prior to launching the Creo executable. The script could open the user's config.pro and comment out any mapkeys that are in the company config.pro. I would not advocate this though. There may be a valid reason for the user wanting to override the company mapkeys.
Agreed. There will always be ways to get around it but I was hoping to make it work for the average user.
I really like the network location idea but several plants all over NA and not all of them have spectacular internet connections so we generally have most Creo files local.
CHRISTOPHER REES wrote:
... Users could always just change the start in location on the shortcut though ...
If your launch icon calls a batch file, the start in field in the shortcut is essentially meaningless as whatever the last directory navigated to in the batch file becomes the startup directory. However, that does nothing to prevent this:
CHRISTOPHER REES wrote:
... (or launch Creo without a shortcut). ...
When I install Creo, I make sure no launch icons are created and part of our launch batch file is to copy our launch icons into their Start Manu. Still not foolproof, but they have to work harder to get around our script.
DM_REMEMBER_SERVER set to YES as per Creo's default settings.
The corporate mapkeys method starting with a unique character will work initially... maybe it's me but Creo is quite good at dumping many settings and mapkeys into a users config.pro when changing just one setting from within Creo and save the config.pro from without Creo (I always edit config.pro from a text file to avoid this). I regularly run into people config files that have ancient config setups from 5+ years ago. Eventually, we'll want to update the mapkeys (e.g. when Creo 4 comes out) and our new mapkeys will lose to their old versions. Maybe it's just a training thing about keeping your personal config.pro clean but people aren't usually very good about that.
With several plants, I would hope each one has a dedicated Windchill Replica server locally.
Put the mapkey files on each replica server and load them from there.
Do you run local installations of Creo or server them from a local server at each site. I run all of my users at 2 sites with a single network installation. Since the remote site is only 12 miles away we do not use a replica server.
When any of my users complain about a mapkey not working right, the first place I look is their config.pro. In some cases, I have cut them down to 20% of the original length because they had duplicate lines from saving changes and dumping all their in memory config settings to their config.pro.
It is an education process to get users to cleanup their files and other housekeeping tasks. I remind my users that fewer workspaces are better and try not to modify the same file in multiple workspaces. When doing a Windchill upgrade, I make them delete all of their workspaces and delete the local files behind the workspace cache.
Creo's internal config editor is terrible. I've seen user's config with multiple copies of our configs and theirs inside.
U've added these lines at the start and end of our configs to help sort this out:
!*** START DC CONFIG.PRO ***
!*** END DC CONFIG.PRO ***