Contents x
9.x Breaking Changes
  • 22 Nov 2024
  • 3 Minutes to read
  • Print
  • Dark
    Light
Contents

9.x Breaking Changes

  • Updated on 22 Nov 2024
  • 3 Minutes to read
  • Print
  • Dark
    Light
Article summary

image

Minor Version Upgrade Guide

>
image

Release Notes CSV

>
image

Upgrade Validator

>
image

See What's Changing

>

Overview

As Decisions evolves, minor version releases bring exciting updates, enhancements, and bug fixes that developers eagerly anticipate. However, alongside these advancements, the potential for breaking changes exists – alterations to the platform that may disrupt existing functionalities and lead to compatibility issues. This article provides a detailed description of breaking changes introduced in minor releases. We aim to equip developers with insights to effectively manage and adapt their projects to these updates.

Please contact support at support@decisions.com with any questions or concerns about the following breaking changes.

9.5.x

Breaking ChangeDescription
[DT-041990]Flow Execution Extensions have been deprecated. Current FEEs will work as expected. New ones cannot be created. Users who need new FEEs are recommended to use Case Entities instead.
[DT-042293]Expression Rules can no longer be created. Existing Expression Rules will function as normal.

9.4.x

Breaking ChangeDescription
[DT-042424]
The count of items in the Inbox has been fixed to be less system intensive. Users who want the count to still appear should export the Default Inbox Folder Count Flow before upgrading and then import the Flow after the upgrade is complete.
[DT-041526]
In past versions restarting while in Maintenance Mode would allow Maintenance Mode to keep persisting. Now a restart will turn it off. For users who want a persistent Maintenance Mode, it can be configured in the settings.xml file.
[DT-042384]
Rule Sets created in older versions of Decisions will no longer break upon upgrading. However, in certain situations, upgrading from a version between v6.0 and v8.17 can require that all variables within a Rule Set must be remapped. This also applies to doing database restores from an older version. Note that this only happens in certain, rare, configurations.
[DT-041447]
The mechanism with which JSON is serialized and deserialized has been redesigned, replacing the old binary system with a hybrid style. This will significantly enhance performance. Any users using an SDK to read or write Flows will need to rewrite their SDK because of this change.

9.3.x

Breaking ChangeDescription
[DT-041902]

In older versions the List Builder Step would generate a data type called List Builder Type that has been removed.

Any usage of the of the output of the Step is now confined to the Flow the Step is in. Any builds that require a List Builder Output to enter a Subflow, for instance, will break upon upgrade.

Any Steps that used the List Builder Type as inputs will break and need to be remapped.

N/A

Encryption Key Changes

There are no issues with upgrading an existing installation to v9.3.

If v9.3 or above is being installed on a database backup of a prior version: The Keys.dat file needs to be included as part of the installation process.

If the Keys.dat file is NOT included: The connection strings for External Database Connections will need to be reconfigured. Account passwords, if stored in a recoverable way, will not allow log ins.

If restoring a database backup from a clean install of v9.3 or above: Keys.dat is required to use account passwords and other encrypted data.

[DT-042430]Project icons from previous versions will break if they were uploaded from a file in a version prior to v9.3.

9.2.x

Breaking ChangeDescription
[DT-041834]API access is now configurable within the settings.xml file. This new setting, AllowApiDocAccess,  is set to False by default, so until it is reconfigured services like Swagger will be blocked from functioning. The setting does not appear in the settings.xml file after upgrade and needs to be manually added to the file with a True setting.
[DT-041549]Builds using the Read JSON And Cast To FHIR Type and/or the Cast FHIR Resource to FHIR Type will need to reconfigure the steps after upgrade. Their outputs will be removed upon upgrade because of a change in types.
[DT-041768]The GetDecisionsSettingInfo method was removed from the platform. Any steps belonging to that method will no longer function.

9.1.x

Breaking ChangeDescription
[DT-041764]
Create List Builder steps do not compile correctly. Anyone using these steps should not upgrade to v9.1. Any users who have upgraded from an earlier version should not convert their Legacy Projects containing Create List Builder steps. This issue is resolved in v9.2.

9.0.x

Breaking ChangeDescription
[DT-041156]

For users with PostgreSQL databases, integrated security is not supported. If you are using a custom connection string, the "Integrated Security" parameter needs to be removed from the connection string before upgrade.

This change also impacts all existing PostgreSQL connection strings not set by the installer, for example Containers and Multi-Tenant environments.

For containers, in your env.list file remove 'Integrated Security=False' for upgrades.

If you have any questions about this before upgrading, please contact us at support@decisions.com. We will be happy to help evaluate your environment to determine if this change affects you.

[DT-041764]
Create List Builder steps do not compile correctly. Anyone using these steps should not upgrade to v9.0. Any users who have upgraded from an earlier version should not convert their Legacy Projects containing Create List Builder steps. This issue is resolved in v9.2.



Was this article helpful?
What's Next
Decisions
Resources
Organization
Connect