CloudSense Package Version Numbers vs Release Numbers (N-2 Policy)

Symptom

After receiving a CloudSense Platform Support Version Policy notification (e.g., "Beginning 1 March 2026, CloudSense will support releases R36, R37, and R38 under our N-2 policy"), customers identify installed packages with version numbers that appear to be below the minimum supported release.

Common examples of version numbers that cause confusion:
- Messaging showing version 33.x.x
- Product Design Studio showing version 1.10.x

Customers may believe these are R33 or R1 packages and therefore EOL under the N-2 policy.

Cause

CloudSense package version numbers do not directly correspond to release numbers. Each managed package has its own independent versioning scheme. A package with version 33.0.2 does not mean it belongs to CloudSense Release 33 — it may in fact be the R36 version of that package.

The version number displayed in Salesforce Setup > Installed Packages reflects the package's internal version, not the CloudSense platform release it belongs to.

Resolution

Step 1: Check installed package versions

In Salesforce, navigate to:
Setup → Installed Packages

Note the version numbers of all CloudSense managed packages.

Step 2: Cross-reference with the CloudSense Release Matrix

Refer to the CloudSense Platform Support Version Policy document or contact your Technical Account Manager to obtain the mapping between package version numbers and CloudSense release numbers.

Key examples of packages where version numbers differ from release numbers:
| Package | Version Number | Actual Release |
|---------|---------------|----------------|
| Messaging | 33.x.x | R36 |
| Product Design Studio | 1.10.x | R36 |

Step 3: Verify compliance with N-2 policy

Once you have the release mapping, confirm that all installed packages fall within the supported release window (e.g., R36, R37, R38 for the March 2026 policy).

If any packages are genuinely below the minimum supported release, plan an upgrade following the standard CloudSense package upgrade procedure.

Additional Notes

• The N-2 policy means CloudSense supports the current release and two prior releases. Releases older than N-2 reach End of Life (EOL) and are no longer eligible for technical support, security patches, or defect resolution.
• When in doubt about whether a specific package version maps to a supported release, check the CloudSense Support Portal documentation directory or ask your Technical Account Manager.
• Package upgrade procedures and release notes are available on the CloudSense Support Portal under the end-user documentation directory.