Specification types and item types can be versioned in QPPD.
Intended use
There are very different approaches and justifications for the use of versioning.
It may be necessary to use old data even after years for long-running orders, although there is already more current data for the same object.
Or there is the desire to be able to trace the history of an object with all changes without gaps.
Also, two versions of an object can be compared relatively easily.
Sometimes very similar specifications should be kept under one specification for ease of searching and administration.
Versioning types
There are five possible settings for the versioning type, which can be assigned to the specification type and/or the item types.
No. | internal representation | Versioning type |
|---|---|---|
1 | ' ' (blank) | Version management inactive / no versioning |
2 | W | Weak versioning |
3 | G | Versioning as a copy |
4 | C | Versioning as copy, consistent validity area |
5 | X | Consistent versioning |
The ascending numbering is an indication of the functional diversity of the different versioning types. The highest versioning type with the most functions and the greatest complexity is "Consistent versioning".
Example
An object can be versioned by triggering versioning in the context menu via "Change status → Create version".
