Versions of Component Objects
Oracle Life Sciences Data Hub implicitly increments and tracks the version number of components of object definitions such as Source Code, Planned Outputs, Table Descriptors, and Columns that are not contained directly in a Domain or Application Area but only in other defined objects such as Programs or Tables.
To modify these objects you must check out their containing object. The system automatically increments their version number behind the scenes when you modify them within the containing object. When you check in the containing object, the system applies a new version number to the modified component object as well as the containing object. If you uncheck the container, you effectively uncheck the component object as well and the system does not save the new version of either object.
The system increments the component's version number only if you modify it, so the version number of the component object may not match the version number of the containing object definition. Oracle Life Sciences Data Hub uses the information it stores about component versions to reconstruct past versions of the definition as a whole.
Component object definitions that are contained directly in a Domain or Application Area (Variables, Parameters, Parameter Sets, Notifications, and Overlay Templates) can have version labels (see Version Labels). They can also have classifications and user group assignments.
Parent topic: Understanding Object Versions and Checkin/Checkout