RadiantOne SaaS: Supported Upgrade Paths to v8.1+ (Skipping Intermediate Versions)

Summary

This article explains when RadiantOne SaaS customers can skip intermediate versions while upgrading to v8.1 and later, and when sequential (one‑by‑one) upgrades are still required. It applies only to RadiantOne SaaS environments managed through the Environment Operations Center (EOC), not to self‑managed deployments.

Note on versioning:

RadiantOne IDDM v8 uses two related versioning patterns: the v8.0.x series (for example 8.0.1, 8.0.2, 8.0.3, 8.0.4) and the broader v8.x series (for example 8.1.x, 8.2.x, 8.3.x, 8.4.x, and so on). 

Starting with releases after v8.1.5, RadiantOne follows a more standard semantic-style versioning approach, where the middle digit (example, 8.3.1 vs 8.4.0) identifies the feature line and the last digit identifies maintenance updates/hot fixes within that line. 

This article explains how that impacts supported upgrade paths from early v8.0.x builds to any later v8.x release(for example 8.1.x, 8.2.x, 8.3.x, 8.4.x, and so on).

Can I skip versions when upgrading to v8.1+?

Yes, in many cases you can skip intermediate versions when upgrading to v8.1 or later (for example, directly from v8.0.4 or v8.1.3 to a higher 8.x release). However, there is an important exception for early 8.0.x releases:

• If you are on v8.0.0–v8.0.3, you must upgrade sequentially, one version at a time, until you reach v8.0.4.
• Once you are on v8.0.4 or any later 8.0.x/8.1.x release, you can upgrade directly to a higher supported 8.x target (such as v8.1+, v8.2+, or v8.3+ and so on.) without installing every intermediate version.

Always confirm your exact current version in the EOC before planning your path.

Required upgrade rules

Use the rules below to determine whether you must go version‑by‑version or can skip intermediate versions.

1. Environments on v8.0.0–v8.0.3

For any tenant currently running an early 8.0.x version (v8.0.0, v8.0.1, v8.0.2, or v8.0.3):

• You must apply each 8.0.x update in sequence until you reach v8.0.4.
• Skipping within this range (for example, 8.0.1 → 8.0.3) is not supported.

Once you have successfully upgraded to v8.0.4, you may then select a later 8.x target version (for example, an 8.1+ release) and upgrade directly.

2. Environments on v8.0.4 or later (8.1+)

For tenants on v8.0.4 or any newer 8.1+ release:

• You may skip intermediate versions when upgrading to a later supported 8.x version.
• Example patterns:
  • 8.0.4 → 8.1.x (direct)
  • 8.1.1 → 8.1.5 (direct)
  • 8.1.3 → 8.2.x or 8.3.x (direct), if those versions are enabled for your tenant

When planning a multi‑version jump (for example, 8.1.3 → 8.3.x or higher), ensure you have reviewed the release notes for any functional changes that may affect your deployment.

Example upgrade paths

The table below gives common examples of supported paths to an 8.1+ target while clearly indicating where versions can be skipped.

“8.1.x+” in this table means any supported 8.1 or higher 8.x version that your tenant is allowed to upgrade to.

Why early 8.0.x requires sequential upgrades

During the 8.0.0–8.0.3 releases, specific internal changes and one‑time migrations were introduced that assume each intermediate build has been applied in order. Because of this, skipping directly over those versions could leave certain background processes or data transformations incomplete.

By upgrading sequentially within the 8.0.0–8.0.3 range and finishing at 8.0.4, you ensure:

• All required schema and configuration migrations have been applied.
• The environment is in a consistent, supported state for later multi‑version jumps to 8.1+.

After 8.0.4, those “one‑time” transitions are complete, and version skipping within the 8.x line becomes safe under the conditions described above.

Best practices before skipping versions

Even when skipping intermediate versions is supported, we strongly recommend:

• Full backup before upgrade
  • Take a complete backup or snapshot of your environment (configuration, metadata, and directory data) before starting any multi‑version upgrade.
  • Ensure you have a tested rollback procedure in case of unexpected issues.
• Review release notes across the range you are skipping
  • Even if you are not installing every version, functional or behavioral changes introduced in those versions still apply once you jump to the newer release.
  • Pay special attention to deprecated features, changed defaults, and required post‑upgrade steps.
• Plan maintenance windows and testing
  • Schedule sufficient downtime to complete the upgrade, run smoke tests, and validate critical business flows.
  • Test non‑production environments first when possible, especially for large version jumps.

Controlling visible versions in EOC (Tenant Admin)

As a Tenant Admin, you can simplify operations by only exposing the versions you actually plan to use:

1. Sign in to the Environment Operations Center as a Tenant Admin.
2. Go to Admin → Settings → Version Management.
3. In the Version Management panel, review the list of available RadiantOne versions.
4. Use the Active toggle to disable versions you do not intend to apply (for example, leaving enabled only the required 8.0.x steps plus your final 8.1+ target).
5. Save your changes. The upgrade dialog for your environment will now show only the versions you have marked as active.

This reduces confusion, avoids accidental selection of undesired intermediate versions, and helps streamline multi‑step upgrades where some sequential steps are required (such as 8.0.0–8.0.4).