Breaking Changes

• Removed deprecations from flow API
• The following flow API methods were removed:
  • execution.task is now fully deprecated. Use execution.connect instead.
  • record.set is now fully deprecated. Use record.save instead.
  • record.load  is now fully deprecated. Use record.get instead.
  • identity.roles  is now fully deprecated. Use identity.get_roles instead.
  • file.save is now fully deprecated. Use file.save_text_content, file.save_bytes_content, file.save_base64_content, file.save_json_content, and file.save_yaml.content instead.
• The following flow API arguments were removed:
  • execution.run_async(wait_for) is now fully deprecated. Use execution.run_async(*args) instead.
  • setting.acquire(timeout) is now fully deprecated. Use setting.acquire(wait_timeout) instead.
• Ref: #861mwgmek

• Removed request retry logic from REST connector
  The retry logic within the REST connector was removed in favour of the more flexible retry wrapper.
  Ref: #26pxnmd
• REST connector returns headers as list 
  
  Previously headers were returned as a dictionary. This did not support multiple headers sharing the same name. Now, headers are returned as a list of lists.
   
  Example previous:

  Content-Type: application/json
  Set-Cookie: foobar
  

  Now:

  - - Content-Type
    - application/json
  - - Set-Cookie
    - foobar
  - - Set-Cookie
    - another cookie

  Ref: #30ykz00

• Flow API call record.export returns a base64 encoded zip file
  Previously record.export returned a dictionary. Now the export might be split up into several files and is returned as a base64 encoded zip file.
  Ref: #861mcc3ex
• Reduced logging of flow API save and get calls
  The flow API methods record.save and record.get will now only log the content when the debug flag is set to True.
  Ref: #861n63bv6
• Removed deprecated execution fields
  The fields “protect_inputs” and “protect_outputs” were removed. It is possible to hide sensitive information in inputs and outputs via the input/output schema.
  Ref: #861mc7pf4

Deprecations

• Some fields of Cloudomation exports were deprecated
  • project.version is now ignored on import
  • record.extension_id is renamed to record.bundle_id on import
  • record.repository_path is ignored on import
  • Update existing exports to avoid using deprecated fields. Use of deprecated fields might fail an import in a future version.
• Ref: #861mjr0a7

New Features

• New Name, new Logo, new Favicon
  Cloudomation is now called Cloudomation Engine to more clearly distinguish the different products available under the Cloudomation umbrella brand.

• Generated forms from schema
  Connector inputs and wrappers can now be configured using a form. Custom schema forms can be attached to flows.
  Ref: #861mc7pf4

• Intellisense
  The online-editor now supports intellisense of flow API modules as well as supported third-party modules.
  Ref: #26pyam4

• Optimised native git integration
  Cloudomation projects and bundles can be configured to be backed by a git repository. You can pull and push changes directly from and to Cloudomation.
  Ref: #26pxtc5
• Debugger
  It is now possible to debug flows using breakpoints.
  Ref: #26pxp7b

• 
  
  

  Horizontal Scalability for on-premise workspaces
  It is not possible to choose how many background processes which process automations should run. This ensures optimum performance at higher loads. As a result, the recommended system requirements have changed:

  	Minimum	Recommended
  CPU	4 Cores	Number of background processes x 2
  Memory	8 GiB	Number of background processes x 4
  Disk space	50 GiB	Aligned with size of data to be processed

  Ref: #86bx3jkm1

• New connector type OPENAI
  Access openai APIs.
  Ref: #863fw04fb
• New connector type AZURE
  Access Microsoft Azure APIs.
  Ref: #862kdtp5j
• New connector type AZUREAI
  Access Microsoft Azure AI APIs.
  Ref: #862kf4gx7
• Add support for pdf2image and pillow third-party libraries
  Manipulate pdf files and images in flows.
  Ref: #862kf22nk
• Add autocommit parameter to MSSQL connector
  It is now possible to disable autocommit to execute queries which cannot run in a transaction, for example “CREATE DATABASE”.
  Ref: #861n22nbx
• Execution message field is now rendered as markdown
  Executions can use markdown in their status message.
  Ref: #861mf7h17
• Deleted is renamed to “Trash”
  To better fit user expectations the deleted section is now called “Trash”.
  Ref: #861n539rc

Bug Fixes

• Number of parallel running executions in one process are now limited
  To avoid overloading the database with too many concurrent connections it is now possible to limit the number of parallel running executions. The default value is 20 and can be increased or decreased according to your database.
  Ref: #861mukm68
• REST connector can send and receive multiple headers with the same name
  Previously the REST connector was unable to send multiple headers with the same name. Also if multiple headers with the same name were received, only the last one would be returned.
  Ref: #30ykz00
• Database keepalive uses a dedicated connection
  The periodic database keepalive now uses a dedicated connection in order to avoid side-effects when the database pool is exhausted.
  Ref: #861n74v2t
• Fixed handling of execution options of statically wrapped resources
  Previously several execution options were improperly applied:
  •  run
  • roles
  • is_productive
• Ref: #861n8z2mr, #861n2kz30, #862kgzpyh

• Hide SMTP credentials in workspace configuration
  The SMTP password value is now not shown any more in the workspace configuration screen.
  Ref: #862kdntud
• Removed limit to only display the first 20 users
  Previously there was a hardcoded limit to only show the first 20 users. Now the user list features a pagination.
  Ref: #861n8p669
• Fix block comment shortcut in Firefox
  The keyboard shortcut Ctrl + # to apply a block comment now also works in Firefox.
  Ref: #865bb7qvp
• Fix logging out of user when entering wrong password when enabling a webhook
  The user is now not logged out any more.
  Ref: #862kdfery
• Fix workspace shutdown
  In some cases the workspace could get stuck while shutting down.
  Ref: #861n74mvq
• Fix connection may be executed multiple times
  In some cases a connection would execute again if it is interrupted during execution.
  Ref: #861narthb