Naming Convention for Subtypes
The subtypeable capability enables subtypes, which are available in Windchill, in the some domains in Windchill REST Services.
When the subtype is enabled in Windchill REST Services, the following naming convention is used:
• The subtype created in Windchill appears in Windchill REST Services with its internal name.
• The domain name which is added as prefix to the internal name is removed.
• The first character of the internal name is capitalized.
For example, consider a parent entity Part in Windchill. Under Part, add a new subtype with the display name demo. The domain name of the subtype is com.ptc. The internal name of the subtype in Windchill is <DomainName.SubtypeName>. In this example, the internal name of the subtype is com.ptc.demo. When the subtype is available in Windchill REST Services, its name is Demo.
• Naming conventions for any entity name, navigation property name, structural property name with underscore (_), starting with digits, and non-starting digits:
◦ The name with underscore (_) is generated as is. For example, Soft_Attribute is generated as Soft_Attribute.
◦ The first character of the name starting with a digit is converted to a word. For example, attribute name like, 1Attribute is converted to OneAttribute, 2Attribute is converted to TwoAttribute. The soft type, such as, 1SoftType is converted to OneSoftType.
◦ The name that start with a digit is preserved. For example, SoftType1 is generated as SoftType1.
• In Windchill REST Services, if subtypes have duplicate internal names, then any duplicate type is generated with the domain name prepended the entity type name. For example, two subtypes ext.testa.MyPart and ext.testb.MyPart are generated as MyPart and ExttestaMyPart, respectively.
Another example, consider two subtypes are available with the internal names ext.demo.demo_assembly and ext.demo.demo-assembly. In Windchill REST Services, you cannot use characters such as a hyphen (-) and an underscore (_) in internal names. In such cases, the name of both subtypes in WRS would be DemoAssembly. Instead, the first subtype is added with internal name DemoAssembly, while the second subtype is generated as ExtDemoDemoAssembly.
• If you define a subtype with an internal name in the <Entity JSON> file, and create a subtype in Windchill with the same internal name, then Windchill REST Services gives precedence to the subtype created in <Entity JSON> file.