Changes for page 262 - Good News
Last modified by Erik Bakker on 2026/02/23 08:06
From version 294.2
edited by Erik Bakker
on 2025/11/19 20:31
on 2025/11/19 20:31
Change comment:
Update document after refactoring.
To version 97.1
edited by Erik Bakker
on 2023/07/17 15:25
on 2023/07/17 15:25
Change comment:
There is no comment for this version
Summary
-
Page properties (2 modified, 0 added, 0 removed)
Details
- Page properties
-
- Title
-
... ... @@ -1,1 +1,1 @@ 1 -2 57-ChangingChameleon1 +201 - Be Informed - Content
-
... ... @@ -1,33 +1,30 @@ 1 - Thisrelease featuresvariousupdatesto our platform, withour neweventstreaming broker runningon DSH taking center stage. Withthis release,our latest event streamingfunctionality will be available to everyone (GA). On top of that, we will launchthe previouslyannouncednew[[runtime image>>doc:Main.ReleaseInformation.RuntimeImages.V341.WebHome||target="blank"]] for **all** customers. On topofthat, we haveseveral smallerfeatures and bug fixes for youtoenjoy.1 +In the last sprint cycle, we focused on planning ahead, finishing up and working on the Hackathon to fix several smaller items. 2 2 3 -Please find out more on our [[Release blog>> doc:Main.Release Information.Release Blogs.257-DSHDelight.WebHome||target="blank"]].3 +Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.201 - Be Informed.WebHome||target= "blank"]]. 4 4 5 -==== New features====5 +=====Minor changes===== 6 6 7 -* General - Event Streaming: The KPN DSH event streaming broker has been set as the default event streaming broker for models that start using event streaming for the first time. Please get in touch with your partner manager about the possibilities of using event streaming in your models. 8 -* General - Runtime Image: A new runtime image is introduced that fixes several issues reported by customers, updates the Java version, and prepares all models for migration to our MAM feature if they are ready. 7 +* Portal - Menu: the back button is changed to have text so it shows clearer the navigation target. (#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 improvements to the edit integration page. (#954) 11 +* Create - Flow Designer: When deleting one or multiple components, you will not be able to change the selection before confirming or cancelling the delete action. (#969) 12 +* Create - Migrate to 3rd Generation: In the event one or more flows break during migration, a popup will inform the fows containing errors after migration is finished. (#983) 13 +* Deploy-User management: The user that makes a change is recorded in history instead of the user that applies to environment. (#979) 14 +* Deploy-Architecture: Upon pressing the button “Apply to environment”, a confirmation page is shown. Here all changes made in the portal that will have an effect in your running environment are listed. These changes can be applied to environment or reverted. (#828) 15 +** Changes made in Deploy Architecture with an effect to 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). 9 9 10 -==== Minor changes====18 +====Bug fixes==== 11 11 12 -* Event Streaming -Data Retention: WhenDSH retention timeis changedon the companylevel,deleting thetopicbyexcluding it in Design > Architectureand applyingthechangeinDeploy> Architecture andincluding it again in Design > Architectureand applyingthe changein Deploy > Architecture resultsintheretentiontimebeingupdated in DSH.13 -* *Notethatthis actionwilldeletethetopicand thereforewillresultin **data loss**.14 -* Design-System:Importingan OpenSpecificationV2 hasbeendeprecated,andit’snotsupportedanymoreateMagiz.15 -* De sign-SystemMessage:Userscangofrom Designto theCreatephasefor all messagetypes. (#1607)16 -* Create - Flowtesting: Thepropertiesthatstartwith“emagiz.dsh“ areprovidedwitha valueautomaticallyinthebackground.17 -* Deploy - Releases: Incaseofactivatinganewreleaseandthereistroubleat thestepof creatingnew certificates,thepreviousvalidcertificatewillbe reused.20 +* Design - Solutions: We fixed an issue that a message mapping error is displayed 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 Gen3 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 you 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) 18 18 27 +=====Infra and image changes===== 19 19 20 -==== Bug fixes ==== 21 - 22 -* Create - Flow Designer: Users are correctly redirected to their request/response message based on the XSD they are selecting in the flow. (#1555) 23 -* Create - Transformation - Value mappings for a “string to enumeration” transformer are now visible after reopening the window. (#1715) 24 -* Create - System Message: The navigation from Create to Design has been fixed for event streaming. Additionally, improvements have been made for synchronous messaging so that the currently visualized message (request or response) is correctly considered when using the “Open in Design” button. 25 -* Create - Add Integrations: We fixed an issue where, when your model is migrating or migrated to the new Event streaming broker, you get an error message for security reasons, sometimes when you un-transfer integrations from the Create. 26 -* Create - Processes: We fixed an issue where opening an entry or exit connector with multiple integrations of the eMagiz Mendix connector system did not open the correct flow. The flows are now displayed in the same order as the topics in the center panel when you focus on a system. This ensures that when you select a flow, the correct one opens as expected. 27 -* Deploy - Architecture: We have fixed a bug for DSH-enabled event streaming models, which may have prematurely lost read/write access to deleting topics if the topic was still in use in the active release. 28 -* Deploy - Releases: We have fixed a bug for DSH-event streaming-enabled models, where updating one flow connecting to the DSH event streaming broker would result in containers hosting other such flows to be redeployed unintentionally as well. 29 -* Deploy - Unused Properties: Users can select multiple properties across pages and delete the selections all at once. (#1730) 30 -* Manage - Topic Triggers: All DSH topics have topic triggers. Removing topics without a topic trigger does not result in an error. 31 -* Manage - Triggers: Manage phase access rights have been updated to allow users with the proper access to view and edit correctly. 32 -* Manage - Error Messages: Increased the maximum number of displayed error message headers from 40 to 60. (#1309) 33 - 29 +* Changed the endpoint that is used for sending errormessages to the eMagiz Control Tower. 30 +* Updated the Spring version of the gateway supporting deploy and manage phase operations.