Release 24.5

info

In this release ACE has optional support for split API files (see info below), it is recommended to test it on your data as it is going to become mandatory. The migration guide for this feature can be found here.

Configuration changes

See configuration for more details.

Runtime server

Added

• ACE_API_SPLIT_ENABLED

Designer Web

Added

• ACE_API_SPLIT_ENABLED

Deployment server

Added

• ACE_API_SPLIT_ENABLED

Release notes

See docker images below.

ACE 24.5.0

August 16, 2024

API file split

It's now possible to store API operations (and workspace variables) in individual files. It reduces individual file size and merge conflicts, and allows easier workspace merge in multiple workspace setup.

API file split requires migration of existing APIs to the new format. In this release feature is optional (see ACE_API_SPLIT_ENABLED), but will be enabled by default in next release. The migration guide for this feature can be found here..

• DIG2022-33071
  Folder support for Open API import
• DIG2022-33068
  Folder support for Open API export
• DIG2022-37080
  Add UI option to turn on API split in Designer Desktop
• DIG2022-33094
  API write [add API]
• DIG2022-33061
  API write [edit API]
• DIG2022-37077
  Migrate API Base Path to Routes
• DIG2022-35284
  New workspace initialization
• DIG2022-33133
  Old workspace detection on workspace load
• DIG2022-33126
  Text editor for routes.yaml
• DIG2022-42658
  Move routes.yaml to routes/ace.yaml
• DIG2022-39586
  Try it out support for routes
• DIG2022-33746
  Deployed API Open API definition
• DIG2022-30516
  Route support in runtime

File reference debugging

ACE now allows to pass and download files when debugging flow.

• DIG2022-33532
  Debug navigation support for files
• DIG2022-33529
  Display flow output files
• DIG2022-33526
  Pass file as input

Other features

• DIG2022-43153
  Log flow execution time at info level
• DIG2022-38637
  Remove API yaml view
• DIG2022-35611
  Workspace validation during import
• DIG2022-38647
  Create an Endpoint to Respond with Deployed ACE Release Version
• DIG2022-37210
  Add clear functionality to Test result and other textboxes
• DIG2022-37246
  Forwarded Authorization header support for SaaS

Bug Fixes

• DIG2022-42614
  Security: Bull board - express-4.18.2
• DIG2022-42016
  Flow usages are not showing API operations on importing Ace 4 workspace in API split disabled env
• DIG2022-41934
  API response is broken on uploading multiple files at once to one file with multipart/form-data
• DIG2022-41843
  Deployment API merge is not detected by cache invalidation
• DIG2022-39729
  Redis step: UI shows error if user tries to pass doc field using mustache syntax
• DIG2022-38750
  Catch step is not skipping even on setting condition to {{false}}
• DIG2022-38644
  Navigation from Flow to API is slow if workspace has lot of APIs
• DIG2022-38572
  Repository settings are saved with invalid token in Ace desktop

Docker images

Designer Web

Hash: sha256:989240b8f259a13f75dd1bb098d1deb924fa29980d47a8a9fd70a24cef7b4c08

docker pull euadigportalcoredev02acr.azurecr.io/ace-designer:24.5.0

Runtime server

Hash: sha256:2ee419b0a1322b5e94bed0af7a7060a60f58c3477e08f88709ef29c165604ca8

docker pull euadigportalcoredev02acr.azurecr.io/ace-runtime-server:24.5.0

Deployment API server

Hash: sha256:9692b7cca2e69addcf0386367bee92bbeaaaa7c62479d4c66a08536eb5eda521

docker pull euadigportalcoredev02acr.azurecr.io/ace-deployment-server:24.5.0

Scheduled job (BullMQ) administration

Hash: sha256:9428161ebfb06440d96eb8e61e4013d34ef7b903e8cc74836a0f52a44389493a

docker pull euadigportalcoredev02acr.azurecr.io/bull-board:24.5.0

Designer Desktop

info

It is necessary to run ACE runtime server locally via Docker for flow and API testing.

ACE Designer Desktop is available here