Use case type versioning in Review Center
Review Center supports semantic versioning for use case types by using the Major.Minor.Patch format. Administrators can create and manage multiple versions of a use case type configuration, define the active version that processes submitted documents, and deploy versioned configurations across tenants through Global Packages.
Use case type versioning
A use case type can include multiple versions of the same configuration, such as categories, filters, table schemas, and document entities. Each version follows the semantic versioning format: Major.Minor.Patch. For example, 1.0.0, 1.1.0, and 2.0.0 are valid version numbers.
Active and inactive versions
- Each version has an Active or Inactive status.
- Only one version of a use case type can be Active at a time.
- The Active version provides the configuration for submitted documents.
- When an administrator activates a version, the previously Active version automatically changes to Inactive.
Identifiers
- The parent use case type retains the existing GUID for external systems and document submissions.
- Each version has an internal GUID for version-specific operations and API calls.