Remove the 80 Character Barrier for String Parameters

[DHLewis]

Please remove the 80 Character barrier/limit in STRING Parameters.  If a String Parameter is allowed to be entered in PDMLink then it should be able to be as long as required.  Also Word Wrapping in Tables allows for longer text to be effectively entered but now the limiting factor is the 80 characters that is a max in Parameters.

[saw]

I would also like to have the capability to restrict the length of parameters.  I know this can be done in MC, but having something that prevents it in the first place allows quicker reaction times from the designer. 

I am mostly considering parameters that may have downstream limits and since we send some parameter values to wt.Parts from CAD then those limits may or may not be imposed based on Business Rules at release.  If we can stop the cut from happening in the first place, we don't have to worry about applying the bandage, whether big or small.

[LawrenceS]

This is also a problem for the Creo Table Repeat Region Filters when you want to do an OR statement.  E.g.

• &asm.mbr.DESCRIPTION==*O-RING*,*BACK*UP*,*D*RING*,*SOLO*SEAL*,*PAR*BA*,*D*SEAL*,*P*SEAL

[mfischer]

Currently, Creo Parametric does not support file and feature names greater than 31 characters (Unite supports up to 75 characters), white spaces, special characters and mixed cases.   This limitation also impacts areas within Creo; such as dialogs, relations, family tables, model tree, etc.  As a result of this limitation, names are truncated, or not allowed, which presents a major usability issue raised by users.

PTC is aware of these limitation and is currently researching efforts to remove the naming restrictions in a future release. 

As part of this effort, PTC will hope to deliver a solution that will support names up to 179 characters, spaces and special characters.  The plan will be to remove these restrictions in file names, model names, features, parameters, Model Tree, dialogs, family tables, layers, toolkit, Unite and all other areas impacted by this limitation.

Regards,

Mark Fischer

Sr. Director, CAD Product Management

[LawrenceS]

@mfischer, this is great to hear!  I would give your response a thumbs up but unfortunately that option is missing for some reason.

[mezell]

We are using common name for part and assembly descriptions in drawing BOMs. It is very common for a components to require more than 80 characters, and Windchill allows more than 80 characters for for Name.

[Michael_Martin]

@mfischer, do you have an update on this?

[mfischer]

PTC understands the strong interest for this enhancement in Creo.  As such, the implementation for supporting long names, special characters and spaces is underway.  Our hope will be to deliver the support in a future release of Creo. 

[kermitstang86]

Revival-

I see the note category in the Creo Parameter type selection.

If we would get the Note category for a Reusable Attribute to map against, that would be VERY helpful.

I am under a requirement to include my security statements on every model, and being able to set that via OIR for a custom attribute, and designated into Creo Parametric would be IDEAL.

Ironically, a competitor software property is more flexible than the native CAD here, and that's very disappointing.

[lbai]

@mfischer, do you have an update on this? is there a plan to add into Creo 11.0, 12.0 or 13.0?

[mfischer]

Hi @lbai,

As stated above, PTC understands the strong interest for this enhancement in Creo, as reflected by the high volume of votes.  We have been actively working on this improvement and will be targeting to finally introduce this capability as part of our Creo 12 release.  I appreciate the groups patience with the delivery of this enhancement and want to assure you all that this is something we hope to bring to Creo in the near future.  

Regards,

mark