Changes for page 243 - Migration Magic
Last modified by Erik Bakker on 2025/06/02 09:33
From 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
To version 236.1
edited by Erik Bakker
on 2025/03/24 14:42
on 2025/03/24 14:42
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 01 -BeInformed1 +241 - Wild West - Content
-
... ... @@ -1,30 +1,35 @@ 1 -In the last sprint cycle,wefocusedon planningahead,finishingup andworking ontheHackathon to fixseveral smaller items.1 +In the last sprint, we have released a lot in terms of usability improvements while working within the various phases of eMagiz and when deploying your hard work to the environment of your choice. As a result, we have a series of improvements and bug fixes for you to enjoy coming out of the hackathon. On top of that, we release a new [[runtime image>>doc:Main.Release Information.Runtime Images.V330.WebHome||target="blank"]] containing a much-needed improvement regarding deployment executions when working with state generation and code mappings on top of various improvements in our underlying code. 2 2 3 -Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.2 01 -BeInformed.WebHome||target=3 +Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.241 - Wild West.WebHome||target="blank"]]. 4 4 5 -==== =Minorchanges=====5 +====Minor Changes==== 6 6 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). 7 +* Overall - Q&A Forum: When viewing a question, you can now easily copy the link to the question to your clipboard (#1471) 8 +* Capture - Add Integration: Removed the ‘remarks’ field from the ‘New Integration’ screen in Capture because this field was not visible enough in the rest of the portal. (#1608) 9 +* Capture / Design: For new systems, message types, machines, tenants, and models, hyphens are **no longer allowed** in the technical name. The technical name can only consist of lowercase letters and digits and must start with a letter. This also applies to systems, message types, and tenants that have not yet been transferred from design to creation. The portal will give an error message while transferring, and the hyphen has to be removed manually. 10 +* Create - Flow designer: Display name character limitations are visible in the validation feedback when adding new flow components (#1554) 11 +* Create - Resources: When trying to delete a message definition, the portal shows which transformation(s) use this message definition and should be deleted as well (#1616) 12 +* Deploy - Deployment Plan Execution: We have improved the stability of the deployment plan procedure. 17 17 18 18 ====Bug fixes==== 19 19 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) 16 +* Capture - Add System: A loading bar is displayed before showing the pop-up when a user tries to create or edit a system. (#1228) 17 +* Capture - Edit System: When editing a system, the validation now considers that the name cannot be an empty string. (#1562) 18 +* Design - Message Definition: Two minor improvements are introduced: 19 +** The widget prevents users from adding the same message attribute within a message definition multiple times. 20 +** When adding a new message entity within your message definition and expanding the existing message definition, it doesn’t throw an exception when the user presses the Save button multiple times in a short time frame. 21 +* Design - Catalog: When creating the Swagger JSON, all custom examples users add will be shown correctly when displaying the Swagger. (#1597) 22 +* Design - Solution Architecture: When modifying the number of runtimes of a system, the validation will now take into account that the value may not be empty (#1513) 23 +* Create - Add Integrations: Users can untransfer a flow even when there is a property attached to the flow. (#1590) 24 +* Create - Add Integrations: When an integration is transferred from the Create phase, the flow, flow versions, and the corresponding integration in the Deploy phase are cleaned. 25 +* Create - Components: The browser page now displays the correct page title (#1509) 26 +* Create - Flow designer: When removing a wiretap from a channel, confirmation will only be asked once now. (#1549) 27 +* Create - Flow Designer: The default name of the REST template support object generated in passthrough API gateway operations now matches the (technical) name of the integration. (#1560) 28 +* Deploy - Properties: Fixed a bug where property descriptions were not updated when there was already an existing property description. (#1526) 29 +* Deploy - Environment Template: Fixed a bug that caused upgrading a fully on-premise environment to exclude some machines incorrectly. 30 +* Manage - Queue Browser: Switching environments when exploring a queue in Manage → Explore moves the user to the queue browser of the correct environment. (#1408) 31 +* Infra - Runtime Image: The cache used for code mappings is now properly started and stopped with the application. This prevents flows using code mappings from encountering errors when stopping their runtime while messages are still being processed. (#1550) 26 26 27 -==== =Infra and image changes=====33 +====Remarks==== 28 28 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. 35 +* New eMagiz Connector for Queues: The new eMagiz connector has been tested in Mendix with **Java 21**, and functionality works as expected.