Skip to main content
Jun 26, 2024 7:11 PM UTC
Acknowledged

Creo 11 Mapkey UI - Enhancements and Usability

Related products:Creo Parametric

1. Describe the Problem

Reference:

Ticket - 17405204 

Article - CS421194

 

The New Creo Mapkey UI has some room for improvement:

  1. It defaults to showing all of the Admin Mapkeys first. We have hundreds of Admin mapkeys that 'flood' the list and make it hard for the user to manage their personal mapkeys. If a regular user wants to manage their mapkeys, they shouldn't have to scroll all of the way to the bottom or collapse every time they go into the menu.
  2. With the old method, where the mapkeys were stored in the config.pro, you were able to see syntax errors with mapkeys. Specifically, if there were lines in a mapkey that didn't end in a semicolon, then all following lines would show as an error in the config menu. Having some indication in the new UI that there are broken mapkey lines would be helpful when developing and debugging mapkeys.


2. Are you using a workaround?
Collapsing or scrolling each time I needed to edit a personal mapkey.

3. What is the use case for your organization?
A regular user wants to create or edit their mapkey.

4. What impact does this problem currently have on your organization?
It makes the new workflow more tedious than it was before.

3 replies

Community Manager
Jun 27, 2024 2:38 PM UTC
Status changed to: Acknowledged

Thank you @jwagh  for your idea. Based on the information you provided, we are acknowledging it as the Community management team. This is not a commitment from the Product team. Other users may comment and vote your idea up.

Apr 18, 2025 3:34 AM UTC

The old mapkey GUI just shows all the admin and user mapkeys in one giant list.   Did you have a company convention to include certain characters in the mapkey to drive sorting before?   (Some rule like, All admin mapkeys start with a "z")

 

At a minimum, if the GUI doesn't allow it, the user should be able to collapse the admin list.

Oct 29, 2025 9:29 AM UTC

We are currently in the process of upgrading from CREO 3 to CREO 11 and only now learned about the change the mapkey. We have over 30 000 lines of mapkey data that we are now testing on CREO 11. The fact that we cannot see errors on mapkeys like we can in CREO 3 is very frustrating.

mbarrows_0-1761730042429.png

 

I would also support being able to see this validation step on later versions of CREO again.