Release notes
Quick answer
Release notes are the authoritative record of what changed in each IdentityIQ version and patch: new features, deprecated behaviour, fixed defects and any required upgrade actions. Read them before every upgrade so nothing surprises you in production.
Key takeaways
- The authoritative record of each version's changes
- Cover features, deprecations, fixes and upgrade steps
- Read before every upgrade
- Deprecations warn you before removals
- Fixed-issue lists explain changed behaviour
Release notes are the authoritative record of what changed in each SailPoint version, new features, fixes, deprecations and compatibility requirements. Reading them is a core professional habit, because they tell you what you can now do, what you must change, and what will break.
What release notes tell you
- New features and enhancements you can adopt.
- Bug fixes, some of which may change existing behaviour.
- Deprecations and removals to plan around.
- Updated compatibility requirements (Java, app server, database versions).
How to use them
Before any upgrade, read the release notes for every version between your current one and the target. Note behaviour changes and deprecations that affect your customisations, and confirm your platform still meets the compatibility matrix.
Staying current
Even between upgrades, skimming release notes keeps you aware of capabilities worth adopting and security fixes worth prioritising. Treat them as required reading, not optional.
Common pitfalls
- Upgrading without reading the intervening release notes.
- Missing deprecations that affect your customisations.
- Overlooking compatibility changes (e.g. a required newer Java).
Want to learn this properly?
Our live, instructor-led SailPoint Training covers this hands-on, with real projects and a certification path.
Check your understanding
Release notes should be read?
- A. Documented fixes. Check the fixed-issues list before assuming a new bug.
- B. Behaviour will be removed. Deprecations flag behaviour scheduled for removal.
- C. Before every upgrade. They reveal changes and required steps before you upgrade.
Show answer
C. Before every upgrade. They reveal changes and required steps before you upgrade.
Before every upgrade. They reveal changes and required steps before you upgrade.
A deprecation is a warning that?
- A. Before every upgrade. They reveal changes and required steps before you upgrade.
- B. Behaviour will be removed. Deprecations flag behaviour scheduled for removal.
- C. Documented fixes. Check the fixed-issues list before assuming a new bug.
Show answer
B. Behaviour will be removed. Deprecations flag behaviour scheduled for removal.
Behaviour will be removed. Deprecations flag behaviour scheduled for removal.
Post-upgrade behaviour changes are often?
- A. Before every upgrade. They reveal changes and required steps before you upgrade.
- B. Behaviour will be removed. Deprecations flag behaviour scheduled for removal.
- C. Documented fixes. Check the fixed-issues list before assuming a new bug.
Show answer
C. Documented fixes. Check the fixed-issues list before assuming a new bug.
Documented fixes. Check the fixed-issues list before assuming a new bug.