What Are the Best Practices and Risks When Upgrading between minor versions of Decisions?
Hello,
We’re planning to upgrade from version 9.4 to 9.17, aiming to do this during a low-activity period. I’d like to understand what might break, potential risks, and the impact on end users. Also, what’s the best long-term strategy to keep our environments up to date and minimize disruption? Any advice or steps to ensure a smooth upgrade would be appreciated!
0
Comments
-
Hello,
Great questions! Here’s a recommended approach for upgrading between minor versions of Decisions:
- Review the release notes for all minor versions between 9.4 and 9.17, paying special attention to breaking changes and new features.
- Link to Decisions release notes: https://documentation.decisions.com/v99/docs
- If your server(s) are Decisions hosted and you are particularity concerned about something listed in the release notes, you can submit a support ticket to request a clone a lower environment for upgrade testing.
- If you are self-hosted, please review our Minor Version Update Guide: https://documentation.decisions.com/docs/minor-version-update-guide?highlight=update
- Breaking changes can also be viewed by using the "Upgrade Validator".
- For more details pertaining to release process here at Decisions, please refer to our Release Process Overview.
NOTE! It is always highly recommended that a full database backup and testing is performed on a lower and or test environment prior to upgrading higher / production environments.
Hope this helps!
0
Howdy, Stranger!
Categories
- 1.1K All Categories
- New Decisions Features
- 1 Decisions
- Process Maker
- New Features
- 18 Decisions Designer Entities
- 4 Administration & Security
- 1 Customization
- 244 Integrations
- 73 Repository
- 5 Process Mining
- 13 Training
- 221 Lunch And Learn Questions
- 88 General
- 504 General Q & A
- 3 Designer Extensions
- 47 Example Flows