When creating a naming standard, you will need to resolve naming standard attribute conflicts between existing attributes and those in the naming standard.
You will also need to ensure that each naming standard is unique.
A naming standard is unique if it differs to other naming standards in terms of any of the following:
For example for an existing naming standard with naming convention attributes: Project - Originator - Type and Related attributes: Status.
Naming convention | Related attributes | Uniqueness |
---|---|---|
Project - Originator - Number | Status | ![]() |
Project - Originator - Status | Number | ![]() |
Project - Originator - Type | Status, Revision | ![]() |
Project - Originator - Type - Number | Status | ![]() |
Project - Type - Originator | Status | ![]() |
Project . Originator . Type | Status | ![]() |
When you are creating or importing a naming standard, you need to resolve any conflicts between existing custom attributes and those in the naming standard. A conflict arises when:
An attribute in the imported naming standard has the same name as an existing attribute but a different description, type, constraints, or values.
An imported naming standard attribute is set as Uniclass and an existing attribute is already set as Uniclass (even if the attributes have different names)
Use existing attribute: Use the attribute which already exists in the project instead of the conflicting attribute in the new naming standard.
Overwrite existing attribute: Overwrite the existing attribute with the details and values of the new naming standard attribute.
Create and use new attribute: Create a new attribute by copying the new naming standard attribute and giving it a modified name.
Merge existing and template attribute: Add the values from the new naming standard attribute to the existing attribute.