In OpenText Documentum, version management is a core feature that allows organizations to track, control, and manage multiple versions of a document throughout its lifecycle.

---

What is Version Management?

Version management ensures that:

• Changes to documents are tracked over time
• Previous versions are preserved
• Multiple users can collaborate without conflicts

This enables a complete audit trail and prevents accidental overwrites.

---

Check-In / Check-Out Mechanism

The foundation of versioning in Documentum is the check-in / check-out process:

• Check-out
  • Locks the document for editing
  • Prevents other users from modifying it
• Check-in
  • Saves changes as a new version
  • Releases the lock for others

This mechanism ensures controlled and consistent updates.

---

Version Labels

The r_version_label attribute is the core of Documentum’s versioning system.

Each version of a document is assigned labels that identify its state.

Types of Version Labels:

1. Implicit Labels (System-generated)

• Assigned automatically by the Content Server
• Examples:
  • 1.0, 1.1, 2.0
• Represent version progression

2. Symbolic Labels (User-defined)

• Assigned manually by users
• Examples:
  • CURRENT
  • APPROVED
  • FINAL

These labels help users quickly identify important versions.

---

Version Tree Concept

Every document maintains a version tree, where:

• Each check-in creates a new node (version)
• All versions are linked together
• Users can navigate between versions

---

Significance of i_chronicle_id

The i_chronicle_id is a crucial attribute in version management.

Key points:

• It is common across all versions of a document
• It acts as a unique identifier for the entire version series
• It binds all versions together

Important distinction:

• Each version has a unique r_object_id
• But all versions share the same i_chronicle_id

👉 This allows Documentum to:

• Track the full history of a document
• Retrieve all versions easily

---

Summary

• Versioning is enabled through check-in / check-out
• r_version_label identifies each version
  • Implicit (system) + Symbolic (user)
• i_chronicle_id links all versions together
• Each version has a unique r_object_id

---

Conclusion

Documentum’s version management system provides a robust and flexible way to track document changes, ensuring data integrity, collaboration control, and full historical traceability across the enterprise.

Implicit vs Symbolic Version Labels in Documentum

In OpenText Documentum, version management relies heavily on the r_version_label attribute, which stores labels that identify different versions of a document.

There are two types of version labels: Implicit and Symbolic.

---

Implicit Version Labels

Implicit labels are system-generated numeric labels assigned automatically by the Content Server.

Key characteristics:

• Always numeric (e.g., 1.0, 1.1, 1.2, 2.0)
• Assigned automatically by the server
• Stored in the first position of r_version_label (r_version_label[0])
• Represent the version sequence

Behavior:

• First save → 1.0
• Each check-in → increments version:
  • 1.0 → 1.1 → 1.2 → 2.0

👉 Used for tracking the technical progression of versions.

---

Symbolic Version Labels

Symbolic labels are user-defined or system-defined meaningful labels.

Key characteristics:

• Not numeric (e.g., CURRENT, APPROVED, FINAL)
• Assigned manually or by workflows
• Stored starting from the second position (r_version_label[1])
• Multiple symbolic labels can exist for a version

Purpose:

• Provide business meaning to versions
• Help users quickly identify important states

👉 Used for functional or business-level identification.

---

Key Differences

---

Conclusion

• Implicit labels track the version history numerically
• Symbolic labels provide meaningful context for users

Together, they make Documentum’s version management both technically precise and user-friendly.