cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
Showing results for 
Search instead for 
Did you mean: 

Allow constraints on name attribute: upper/lower case, picklists

Allow constraints on name attribute: upper/lower case, picklists

you should be able put a constraint on the name attribute of any subtype, in order to tranform for example the name all to Upper Case, or all to lower case.

it must be able to set the constraint for 1 softtype in particular. For example, for CAD drawings to UPC, and models not, where models and cad drawings are both subtypes of EPMDocument.

this must work for EPMDocument subtypes, WTPart Subtypes and WTDocument Subtypes.

if one saves a model or drawing to the workspace, using the UWGM, it should also consider the constratint placed on the name attribute of the specific softtype created

5 Comments
ywyffels
7-Bedrock
OliverDroop
11-Garnet

Regarding the Name by picklist this is current functionality -> see dynamic enumeration constraint for NAME.

I have recently implemented a complete solution for NAME based on a Naming Catalogue in Windchill.

Main Requirements should be covered ‌

  1. >50K entries should be supported
  2. It should support main and additional description
  3. Only approved entries should be selectable
  4. Users should be able to request a new entry
  5. Standardization Department should review and approve a new request
  6. Users should see Browser local and english during selection of Name
  7. WTPart, WTDoc, EPMDoc should be supported
  8. In reports at least two different languages should be displayable for Name
  9. Different languages should be usable in drawing title blocks for EPMDoc

One requirement was very important to my customer:

Name is a master attribute and if updated it changes for all revisions. After first release this should not happen right away anymore but should update on release if the user had to change this. This is true due to the fact that use cases like workpackages, export to excel, republish, etc would send out changed information. In my opinion it depends on your naming catalogue granularity. The main description most likely will never change but the additional one potentially could.

Graham BirchJeffrey Zemsky‌ let me know if you are interested in this solution since we have the storyboards handy. I think it would complete our GPD solution and will support the latest standards.

OliverDroop
11-Garnet

For example, for CAD drawings to UPC, and models not, where models and cad drawings are both subtypes of EPMDocument.

This can be easy separated by an additional CADDocSoftytype with other constraints. You can use the CAD Parameter in you templates and a preference to pick this Softype during creation.

ywyffels
7-Bedrock

Hi Oliver,

I don't know if I read this correctly, but the issue is not that I can't create softtypes for different types (models <> drawings) but the problem is that you can't put aan UPC constraint on the name attribute with standard configuration.

Your name based catalog seems very interesting to me. one of my customers had a simular functionality in an old system, and is missing this in WT 10.2. In WT11, he will try to solve this with the classification and the autonaming rules.

PTCModerator
Emeritus
Status changed to: Acknowledged