A new enhancement in R2022x GA release enables users to identify and capture iterative design states between formal releases, through the use of a dedicated Revision counter schema:
This counter, based on admin settings, takes into account the primary and secondary “elements” of the revision and increments them according to the user intention when the revision is revised:
When the content is released:
The revise action will increment the Primary element of the revision
Example: A.1 --> B.1
When the content is not released (In Work, Frozen):
The revise action will increment the secondary element of the revision
Example: A.1 --> A.2
This enhancement brings the following values to the users:
- Better understand how the revision evolves
- Ease of the revision control while strengthen data governance
- Ensure standard and regulation compliance with an extended and flexible revision schema
Prior to R2022x, the evolution of a revision format with a single element (primary), for example, would look like this:
From R2022x GA onward, the evolution of a revision format with the new admin option “Primary and Secondary” (See below) would look like this:
Admin settings required for this new revision format (in “Collaborative Spaces Configuration Center”):
- “Revision Naming Rules”:
Physical Product (3D Part, 3DShape), Drawing and more = A, B, C … (or 1,2,3 ...)
2. Revision Format” :
- Revision format = Primary and secondary
- Classical minor revisions = Disabled
