Breaking Changes
Blacklisting System Tables
For security reasons, some system tables are blacklisted in the context of referenced tables and workflow conditions starting with Therefore™ 2026 or Therefore™ Online v35 respectively.
In addition, specific columns of some system tables are blacklisted.
Furthermore, the process of how workflow conditions are checked has become more restrictive and conditions are much more limited.
This means that some configurations that could be made before will not be possible in the future. Existing configurations will still work but they cannot be saved anymore. For that reason, changes to these existing configurations may not be possible.
It is recommended to clean up existing configurations that may be problematic. To assist administrators with encountering invalid workflow conditions, a new Therefore™ Console tool, 'Check Workflow Conditions' has been added. See our help page about the different console tools for further information regarding the steps to clean up existing configurations.
Therefore™ On-Premises users can disable workflow condition validation in case a configuration that was made before these changes needs to keep working. To do so, right-click on the Workflow node in the Therefore™ Solution Designer > select 'Settings' > go to the 'Advanced' tab > set 'Disable Workflow Condition Validation' to 'True'.
Credentials Store Upgrade
If certain configuration patters exist for REST tasks in Therefore™ workflows they may stop working after the upgrade to Therefore™ 2026.
Detailed information and instructions can be found in the Credentials Store Upgrade white paper on the Therefore™ Extranet, located in the Therefore™ Online category:
https://extranet.therefore.net/downloads/white-papers/
Endless Loops in Workflow Configurations
For Create Document tasks that start a workflow a check was implemented to match the functionality in the Copy Document workflow task.
This check confirms if the workflow started by creating the document would be the same workflow that is currently running.
If that is the case, the workflow is not started.
For administrators that have a configuration dependent on the aforementioned scenario it is recommended to move the Create Document task into a sub workflow that starts the main workflow again.