1. Review the release notes and upgrade guide
...
The table below lists R4J versions that require preparation. Versions NOT listed here are safe to upgrade or downgrade as needed.
R4J version | Upgrade guide | Supporting articles / Important notes |
|---|---|---|
The following template language is not compatible w/ lower versions:
| ||
The following new features are not compatible w/ lower versions:
| ||
Old permissions are still supported in this version along with new permissions. The new permissions are not compatible to lower versions. | ||
Breaking change: Tree view data after the migration are not compatible to lower versions. R4J 4.6.x vs 4.7.x performance benchmark results Loading issues and errors encountered after tree data migration | ||
“Expand all“ is removed. The feature comes back at 4.8.0. | ||
Breaking change: Revision data from this version are not compatible to lower versions. Summary of functions affected by revisions restructure in R4J 4.5 | ||
Breaking change: Coverage view filters modified and created from this version are not supported in lower versions. Coverage view filter migration. Already EOL. If further support is needed, contact our service desk. |
2. Test the R4J version upgrade using a test or staging instance
...
| Info |
|---|
It is important to do a quick test of the upgrade on your production instance. Based on the results, finalize your decision to remain with the version or roll back to a backward compatible version. |
6. Execute R4J Integrity Checker after upgrading
| Info |
|---|
This is an optional but recommended step. This will help to fix data integrity issues after upgrading, if any. Refer to Checking the Database Integrity. |