Skip to Content

Changes for page 237.1 - Fabulous Flow

Last modified by Erik Bakker on 2025/01/31 11:52
From version 98.1
edited by Erik Bakker
on 2023/07/17 21:28
Change comment: There is no comment for this version
To version 114.2
edited by Erik Bakker
on 2023/10/06 13:09
Change comment: Update document after refactoring.

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -201 - Be Informed
1 +2052 - World Explorers
Content
... ... @@ -1,30 +1,15 @@
1 -In the last sprint cycle, we focused on planning the upcoming quarter, finishing up, and working on the Hackathon to fix several smaller items.
1 +This release signifies our efforts to wrap up our quarter. It consists of several much-needed functionalities for specific use cases regarding the next-generation architecture.
2 2  
3 -Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.201 - Be Informed.WebHome||target= "blank"]].
3 +Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.206 - Wrap Up.WebHome||target="blank"]].
4 4  
5 5  =====Minor changes=====
6 6  
7 -* Portal - Menu: The back button is changed to have text on it to make the navigation much clearer. (#949)
8 -* Design-Architecture: Topic Storage detail page contains help text. (#994)
9 -* Design - API Endpoint Specification: Improved UI and added independent scroll functionality. (#832)
10 -* Design - API Gateway: Small styling improvement on the "Edit integration page." (#954)
11 -* Create - Flow Designer: When deleting one or multiple components, you cannot change the selection before confirming or canceling the delete action. (#969)
12 -* Create - Migrate to 3rd Generation: If one or more flows break during migration, a popup will inform the flows containing errors after the migration. (#983)
13 -* Deploy-User management: The user that makes a change is recorded in history instead of the user that applies to the environment. (#979)
14 -* Deploy-Architecture: Upon pressing the “Apply to the environment” button, a confirmation page is shown. All changes made in the portal that will affect your running environment are listed here. These changes can be applied to the environment or reverted. (#828)
15 -** Changes made in Deploy Architecture with an effect on your running environment will only be listed when they are made after this release.
16 -** Changes with a direct effect will not be listed (for example, restarting a machine).
7 +* Deploy - Releases: The related unused images in the on-premises machines will also be removed when the release is removed.
8 +* Create - Transfer settings from Design: Added a migration step. If the custom error handling is set to false, we set the error channel to “errorChannel” for all inbounds in a flow.
9 +* Create - Transfer settings from Design: Added a check in the migration that validates whether every targetNamespace is filled in when a SOAP web service is migrated and split as part of the migration to the next-generation architecture.
10 +* Create - Transfer settings from Design: Added a check in the migration that validates whether a specific old component, the Jetty server support object, remains in a flow after the migration. If so, the user is notified that they need to take action on this.
17 17  
18 -====Bug fixes====
19 -
20 -* Design - Solutions: We fixed an issue that displayed a message mapping error despite having a passthrough API gateway. (#935)
21 -* Design - Settings: The full length of the contract number can now be registered. (#958)
22 -* Create - Migrate to 3rd Generation: Components used in Gen 2 flows that can be used in Gen 3 will not block migration. (#982)
23 -* Deploy - Deployment plan: We fixed an issue that the list of installing flows did not show in the left pane when you deploy a release version to install/start/stop some flows into your runtimes. (#990)
24 -* Deploy - User Management: As a user with view-only rights in Deploy/User management, you can now double-click on a user to open its details. (#972)
25 -* Manage - Manage Dashboards: The screen loading speed is significantly improved for all models. This is most noticeable for larger models. (#964)
26 -
27 27  =====Infra and image changes=====
28 28  
29 -* Changed the endpoint for sending error messages to the eMagiz Control Tower.
30 -* Updated the Spring version of the gateway supporting deploy and manage phase operations.
14 +* New logging feature enabling us to make better choices in deprecating old encryption standards.
15 +* Carwash change to enable our direct connect offering for customers on the next-generation architecture.