Skip to main content
A
acoates1-Visitor
1-Visitor
April 10, 2015
Solved

Description tools on file creation

  • April 10, 2015
  • 2 replies
  • 3327 views

Hi All,

We currently have our Windchill set up to prevent duplicate part numbers from being created. I'm looking to further evolve our systems to remove the need for an external part number database altogether. Are any of the following achievable with Windchill 10.1, please:

  • Preventing duplicate part descriptions;
  • Setting a custom field for an abbreviated description that can also prevent duplicates;
  • Setting both fields up to prevent inputs over a certain length.

Many thanks,

Andy

Best answer by acoates

Thanks Lori and Marco.

I've successfully set the limit for a custom global parameter but I am struggling for an inbuilt PTC one. We use "PTC_COMMON_NAME" for our descriptions. Can this be length limited in a similar manner? If not then I can set up a "ghost" new global parameter called, for example "TITLE" and then have a relation that sets "PTC_COMMON_NAME" = "TITLE".

2 replies

A
acoates1-VisitorAuthor
1-Visitor
April 17, 2015

Quick nudge: can anybody help, please?

L
LoriSood23-Emerald I
23-Emerald I
April 17, 2015

You could achieve the first two using a custom listener/validator that will check whether the description and abbreviated description attribute values are unique when they are updated.

You should be able to set a string-length constraint on the attributes in Type and Attribute Management that can limit the number of characters available for the attribute.

A
acoates1-VisitorAuthor
1-Visitor
April 21, 2015

Thanks Lori. Is a custom listener/validator something easily set up from within the standard GUI or will It require coding please? I've not come across these before.

A
acoates1-VisitorAuthorAnswer
1-Visitor
April 24, 2015

Thanks Lori and Marco.

I've successfully set the limit for a custom global parameter but I am struggling for an inbuilt PTC one. We use "PTC_COMMON_NAME" for our descriptions. Can this be length limited in a similar manner? If not then I can set up a "ghost" new global parameter called, for example "TITLE" and then have a relation that sets "PTC_COMMON_NAME" = "TITLE".

T
23-Emerald IV
TomU23-Emerald IV
23-Emerald IV
April 24, 2015

You can re-map what Creo parameter populates the Windchill "Name" parameter, but I don't think you're going to be able to limit the length. Creo allows 80 characters for parameters and I believe this is hard coded. I'm not sure what would happen if you limited Windchill to less characters that what Creo allows.

By the way, the mapping between Windchill and Creo is handled in Preference Management under Workgroup Manager Client --> Mapping System Attributes and File Properties. Changing this mapping may require you to modify the download service as well.

A
acoates1-VisitorAuthor
1-Visitor
April 28, 2015

Thanks Tom. I'll have a play and see what happens!

Terms & ConditionsCookie settingsAccessibility statement