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.
| Breaking Changes | Description |
|---|
| [DT-046390] | v9.20.1 will require .NET 10 to be installed before upgrading. |
| [DT-046055] | Users who upgrade to v9.20.1 with the Get Daemon Token step will need to re-map the step since the Tenant Id will no longer be appended to the end of the Auth URL, but will still have a tenant id property. |
| [DT-046381] | Users should note that custom CSS that has been applied to modify the tab header size could potentially break the layout. |
| [DT-045714] | Agent Designer Updates: - Generative AI Features will sometimes not produce data.
- Projects exported before 9.11 containing AI dependencies will not obtain new AI folders on import (Agent and System Prompt, Prompt Group, Execution History).
- Projects exported before 9.20.1 containing AI dependencies will not obtain new AI folders on import (Agent and System Prompt).
Users must make changes to Project Dependencies to populate these new folders (remove/add AI.Common as a dependency)
|
| Breaking Changes | Description |
|---|
| Okta OpenID | Users with Okta OpenID configured will find that single sign-on will not trigger after upgrading to v9.17.0. Please upgrade to v9.17.1 (released on 11/18/25) to resolve this issue. |
| [DT-045977] | Run container as non-root user: Containers will now run as a non-root User by default. Users with existing deployments on v9.16 or earlier that use persistent volumes containing data created by the root user can refer to Securing Decisions Container Environment to apply one of the provided migration strategies. |
| [DT-045903] | Three new steps, Get Address, Get City by Zipcode, and Get Zipcode, have been added to the USPS Module because of USPS's pending API change. Users can refer to this article for more information: Web Tools APIs | USPS. All other steps in the Module are now Deprecated and are marked as such in the platform. These new steps are not a direct replacement for deprecated steps; Flow logic may need to be updated to account for this. Users must utilize the new steps once USPS's API is deprecated. |
| Breaking Changes | Description |
|---|
| [DT-045648] | Remove unsupported modules from Linux containers: R and SolaceMQ Modules have been removed from the module list for container environments and can no longer be installed. It is recommended to uninstall the modules before upgrading to v9.16 in containers. The modules did not function correctly in containers in any earlier version. |
| Breaking Changes | Description |
|---|
| Remove Business Metrics and Client Statistics | Business Metrics and Client Statistics Tables have been removed from the platform. Designers utilizing services, data sources, etc, should check their Flows. |
| Breaking Changes | Description |
|---|
| UpdateAccount method under Account Service | The UpdateAccount method under Account Service in the Internal Service step no longer functions. Attempting to use it will throw an error. Any uses of this step will need to be changed to the Update Entity step to regain functionality. Use the Flow Structure report to find where that step is being used to make it easier to replace. |
| Breaking Changes | Description |
|---|
| [DT-044043] | Constant prompts on the Get Embedding from Text AI Common Step will be wiped after upgrading. Flows utilizing constant prompts on this step will need to be revised, and the constant mapping on the step re-entered. |
| Breaking Changes | Description |
|---|
| [DT-043501] | Fixed a regression that caused errors to appear when creating HL7 interfaces. Interfaces created in v9.11 will not have processing flows. These will need to be created manually. All new interfaces will have the correct processing Flows. |
| [DT-044353] | Breadcrumbs are no longer translatable. Contact support@decisions.com for advice on a workaround. |
| [DT-043850] | Designer Extensions located at the System level will no longer function. They must be moved to the Project that is using them. |
| Breaking Changes | Description |
|---|
| [DT-044294] | JSON Web Tokens that are using the default key will break. Users should modify the key before upgrading. |
| [DT-044310] | The Execute Command step or Execute Command Async step will fail upon upgrade. Users who follow these steps in their builds should contact support@decisions.com before upgrading. |
| [DT-043953] | JavaScript components or SDK modules may break due to a TypeScript compile target upgrade from ES5 to ES6. Users with custom modules should recompile their code using ES6 before upgrading. |
| Breaking Changes | Description |
|---|
| [DT-043977] | Diacritics (symbols that appear above letters in other languages, such as á, à , ä) are being restricted in v9.9. Any Project or Folder names that had those symbols will have them removed - so names are changing slightly. In addition, any data structures with those symbols that were created in older versions will see validations, and steps generated from those data structures will not work. |
| [DT-043908] | The Thread Job Report has been updated to be more descriptive. Any users who have created a Delegate Job via SDK may find that the Report is no longer functional. |
| Breaking Changes | Description |
|---|
| [DT-042006] | Default Reports that have been customized will lose their customization. This will need to be reapplied after upgrade. |
| [DT-041208] | The ability to make system-level constants has been removed. Existing System constants will still function as expected. Users are encouraged to use project-level constants wherever needed. |
| [DT-043680] | Flow annotations have been removed. Existing annotations will still be visible, but new ones will no longer be able to be created. This is not to be confused with Flow Annotation Steps, which are still in the platform. |
| [DT-043492] | Several Page Toolbox controls have been removed: Folder Actions Bar, AppStore, Features, Run Assignment, Entity Scroller, Matrix, Rich Text Report Viewer, and Text Report Viewer. Existing controls will remain functional, but no new ones can be added. |
| Breaking Change | Description |
|---|
| [DT-043308] | v9.7 will require .NET9 to be installed before upgrading. |
| Breaking Change | Description |
|---|
| [DT-043255] | AuthID has been removed from the platform |
| [DT-043288] | Caching has been changed, and there are new cache types and steps that are definable at the Project level. Cache steps in prior versions have been made obsolete and have been replaced. All cache steps now require that a Cache Definition be created and applied to them. Users with older cache steps will receive an error saying they require a defined instance. |
| Breaking Change | Description |
|---|
| [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. |
| Breaking Change | Description |
|---|
| [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. |
| Breaking Change | Description |
|---|
| [DT-041902] | In older versions, the List Builder Step would generate a data type called List Builder Type, which has been removed. Any usage 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 logins. 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. |
| Breaking Change | Description |
|---|
| [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. |
| Breaking Change | Description |
|---|
| [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. |
| Breaking Change | Description |
|---|
| [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. |
