Skip to main content
Jul 1, 2016 6:41 PM UTC
Delivered

Allow Mapkeys in both config.sup and config.pro

Related products:Creo Parametric

The config.sup is for settings that users (or any other config.pro files) are not allowed to change in Creo and seems like a perfect place for corporate wide mapkeys to create standard processes/toolsets. In Creo 3 M060 as shown in the attached video, the config.sup will allow MANY mapkeys to exist in a Creo session but not let ANY of the mapkeys from the other config.pro files (e.g. a users config.pro) load into Creo. It would be way more flexible if the other config.pro mapkeys would load into session as well. Where two mapkeys have the same name, always use the config.sup mapkey. General user config.pro files often tend to get tons old settings and mapkeys built up over time if edited from Creo so superseding user mapkeys where a naming conflict exists help admins keep users using the latest and greatest processes/mapkeys as things inevitably change.

Several good ideas were shared in Re: Corporate Mapkeys - Superseding User Mapkeys about how to accomplish this but currently require a lot of monkeying around or restructuring of config setup locations to somehow load the desired corporate mapkeys last. The idea above would make this way easier.

21 replies

Feb 15, 2023 12:14 PM UTC

I think PTC has solved the issue of writing all config settings to the user's local config.pro file. Only changed settings get written back to the config.pro.


When did this happen?

Feb 15, 2023 3:21 PM UTC

We're on 7.0.8.0, and users are inadvertently saving ALL mapkeys to their personal config.pro's.  

Feb 15, 2023 3:40 PM UTC

They are doing it wrong then.

When you make a change in Creo to the configuration file and press OK, you get this dialog box:

BenLoosli_0-1676475055680.png

If you press Yes, it will save only what is displayed in the current configuration window to a file of your choice, default is <working directory>\config.pro. 

If you press No and then go back and do an Export Configurations (Notice the 's', plural), you get a new config.pro with ALL of the configuration settings loaded in your Creo session.

If you press No and then go back and do an Options: Inport/Export, Export per current filter, you get only the current displayed configuration settings, but the file is unformatted.

 

 

Feb 15, 2023 3:50 PM UTC

Regardless of how saving works, it would still be helpful to be able to define company mapkeys that could not be overridden by the users, intentionally or unintentionally.  Today the only settings protected are those in the config.sup, and that can't contain mapkeys, hence the product idea.

Feb 15, 2023 4:43 PM UTC

We have literally thousands of users.  If there's a way to do it wrong, despite all warnings, there WILL be a subset of users who WILL do it wrong.  That realization is a way of life in this support business.  Keeps it interesting.  The ability to lock specific mapkeys down in the config.sup would mitigate that,  Now, how difficult, or possible, that would be to get done in the software is a matter for PTC.

Apr 18, 2024 1:13 PM UTC
Status changed to: Delivered

The new Creo 11 enhancement   Enhancement: Separate Mapkeys Configuration will also allow separate mapkey file definitions on admin level

Apr 22, 2024 12:23 PM UTC

@mneumueller Thanks! Glad to see this become a reality.

Apr 22, 2024 12:53 PM UTC
Thank you @lhoogeveen for your idea and @mneumueller for the confirmation!
Apr 23, 2024 6:32 PM UTC

Nice.  This plugs a longstanding hole for us.

3-Newcomer
May 14, 2024 7:39 AM UTC

This new functionality with the mapkeys.pro is disabling the functionality to load mapkeys from your startup directory.
I filed a ticket for this (SPR15300697) and am also in contact with Eyal Chaki from the User Experience lab about it.

 

Currently in Creo 11.0

If you have a config.pro in your startup dir with mapkeys in it, they are copied to a mapkeys.pro file in %APPDATA%\Roaming\PTC\ProENGINEER\Wildfire\.wf\.Settings.
When you have mapkeys in your config.pro in the LOADPOINT\Common Files\text they are copied to the mapkeys.pro file in the text folder as well.

In both cases, you will get a warning until you remove the mapkeys from your config.pro.

 

For me (and I think others is well) this is an issue.

 

Many users will not be able to find the files in %APPDATA%\Roaming\PTC\ProENGINEER\Wildfire\.wf\.Settings, so to me that is like hiding these configuration files from the users. Like something the users should not care about where these files are. Everything is just saved somewhere ...

 

Why should we be able to get the old functionality back?

 

1. Users that need to test new versions of Creo will mix their mapkeys and UI settings, because these are all hidden in the profile directory in the same files. Every change will be reflected back in the earlier release,.

2. 3rd parties using a startup folder to manage the configuration will not be able to use mapkeys anymore. (E.G. My OCUS Benchmark)

 

3. It is not intuitive to have different behavior for the mapkeys.pro vs. the config.pro file

 

4. It removes functionality which has always been there.

 

To Summarize:
Creo 11.0 is now reading .pro .sup .ui configuration files from the following 4 locations

 

1. LOADPOINT\Common Files\text (can be overruled by PTC_CREO_ALT_SETTINGS_PATH environment variable; since 9.0.2.0)
a. config.sup
b. config.pro
c. creo_parametric_admin_customization.ui
d. mapkeys.pro

 

2. %USERPROFILE% (similar to $HOME on Unix)
a. config.pro

 

3. %APPDATA%\Roaming\PTC\ProENGINEER\Wildfire\.wf\.Settings
a. creo_parametric_customization.ui

b. mapkeys.pro

 

4. Startup Dir
a. config.pro
b. creo_parametric_customization.ui (when config load_ui_customization_run_dir is yes)


@mneumueller Please allow for the old behaviour by reading the mapkeys.pro file from the startup folder.
At least with a config option similar to load_ui_customization_run_dir.

 

Olaf

 

Note:

About users being able to manage their own mapkeys I agree.

But for larger companies we surely need the possibility to roll out mapkeys combined with a UI configuration to our user community and don't let users override them.
A non-overridable mapkeys.pro in the first folder (LOADPOINT\Common Files\text (can be overruled by PTC_CREO_ALT_SETTINGS_PATH environment variable)) would fix this.