...
Several FlexDeploy screens now leverage WebSocket, as opposed to a traditional poll polling mechanism using REST APIs, to both improve UI responsiveness and reduce network traffic and server load. This change has been made on the following screens:
Project Execution List
Execution Workflow Steps
Execution Plugin Logs
Release Dashboard
If WebSockets are not available, the screens gracefully fall back to the prior method of polling updates.
Projects
Project Security options are separated from Folder for clarity. Security can still be overridden at Folder, Project and Release level, if no overrides are done permissions are inherited from parent folder. Additionally, Folder Security tab will now correctly disable show all groups that inherit READ permissions based on being given from other permissions as disabled so it is clear that they cannot be deleted.
FLEXDEPLOY-3964 - A new checkbox has been added on the Edit Folder Approval popup called "All Tasks Required". When checked it will use the default behavior of each group needing will need to approve the task. If unchecked, only a single group will need to approve, which was the behavior before the checkbox was added.
FLEXDEPLOY-9148: The packages list now includes headers for the latest version and environments. The "Latest Version" column will show the most recent successful build for each package, while the environment-specific columns will display the latest successful deployment for each package in its respective environment. Quick access links to the execution pages are also provided for convenience.
FLEXDEPLOY-12191 - A notes field has been added for users to provide on all workflow execution requests, which can be referenced from project executions and reports. Notes are required for rollback requests and optional for all other request types.
FLEXDEPLOY-13033 - Test configuration stored as YAML in Source Control can now be overridden by Project level Configuration. Override is done using same testName value.
FLEXDEPLOY-13180 - The commit chip card on the Project Execution tab will now disable the View Change Logs button if the user does not have access.
...
FLEXDEPLOY-12722 - Classes not found in a groovy script can now be auto imported via "Quick Actions". Quick Actions are available when hovering an error or by hitting `ctrl+.` while the cursor is in the error range (red squiggles).
FLEXDEPLOY-13040 - The Code Editor now supports suggestions for wildcard imports in Groovy scripts.
Purge
Purge settings have changed with the 9.0 release. Please read this section and update your purge settings as desired after upgrading.
FLEXDEPLOY-12790 - Introduced new Purge Setting Keep Production Count, which must be 1 or higher. Additionally, Keep Count setting can be lowered to 0. Keep Success Count and Keep Failed Count are removed. Customer should use other available Keep Count settings.
FLEXDEPLOY-12145 - Purge settings now allow selection on hour of day when purge would be executed. Additionally, if workflow execution threads are overwhelmed then purge will wait for 5 minutes interval till workflow execution threads free up indicating less load on system. Purge execution either Success or Failed is also recorded on Change History report.
FLEXDEPLOY-12870 - Added a new purge setting to control how many days to keep Webhook and Event messages and logs.
...
FlexDeploy 9.0 application now requires Java 17 and 21 and FlexDeploy Installer 1.0.21 23 or later should be used with FlexDeploy 9 upgrades.
FLEXDEPLOY-11843 - FlexDeploy no longer users Apache Commons Lang. Instead Apache Commons Lang3 is used. This is a potentially breaking change to groovy scripts with custom imports. Use the lang3 import instead if you were importing commons lang.
FLEXDEPLOY-12990 - Deprecated constructor ReleaseProjectsPojo(Long pProjectId, String pPackageName, Boolean pRequestAllFiles) and added ReleaseProjectsPojo(Long pProjectId, String pPackageName)
...
Git Accounts has been removed and Connected Apps has taken its place. Git connected applications will offer the same feature list as Git Accounts and more! However, because Git Accounts were stored only on the users device and not the FlexDeploy server, we are not able to port over existing Git Accounts into Connected Applications. We apologize for this inconvenience.
...