Changes for page 243 - Migration Magic
Last modified by Erik Bakker on 2025/06/02 09:33
From version 30.1
edited by Erik Bakker
on 2022/12/06 16:02
on 2022/12/06 16:02
Change comment:
There is no comment for this version
To version 234.1
edited by Erik Bakker
on 2025/03/24 06:40
on 2025/03/24 06:40
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 -1 89-PrivateEye1 +241 - Wild West - Content
-
... ... @@ -1,24 +1,31 @@ 1 - Thereleasebringsaprivatestoretoourcommunityandmakes thelatestruntime image availableforourcustomersrunningonthe3rd generationarchitecture.Furthermore, weintroduce severalimprovements to our3rdgenerationruntime and itsinteraction with the portal.1 +In the last sprint, we have released a lot in terms of usability improvements both while working within the various phases of eMagiz as well as 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.189 - Private Eye.WebHome||target="blank"]]. 4 -=====New features===== 5 -* A new runtime image for customer models running on the 3rd generation runtime. Please find out more on our [[Release blog>>Main.Release Information.Runtime Images.V1~.1~.0.WebHome||target="blank"]]. 3 +Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.241 - Wild West.WebHome||target="blank"]]. 6 6 7 -==== =Minorchanges=====5 +====Minor Changes==== 8 8 9 -* General: Code mapping is now available for models migrating to the 3rd generation runtime. 10 -* General: Added functionality that allows you to search by pressing "Enter" on various pages across the platform. (#785) 11 -* Store: Renamed several display names across the Store functionality to better clarify what the functionality does for you. 12 -* Deploy - Deployment plan: For 3rd generation runtimes we have changed the restart behavior in case of startup problems. This means that when a runtime is being deployed, which is constantly crashing and thereby causing problems, the restart of the runtime is limited to just five times. (#720) 13 -** After five times, the runtime will remain in the stopped state. 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 not allowed in the technical name anymore. The technical name can only consist of lower case 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 create. 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. 14 14 15 15 ====Bug fixes==== 16 -* Create - Flow designer: Resetting the JMS server sometimes resulted in invalid connection settings for connecting to the failover JMS server. (#717) 17 -* Create - Flow designer: Newly generated flows were configured with incorrect XSD or XLST resource locations under specific circumstances. (#718) 18 -* Deploy - Deployment plan: Before when you tried to deploy a Release via the Deploy functionality the widget could crash randomly. With this fix we ensured the widget will always load correctly. (#362) 19 -* Deploy - Architecture: Prechecks for cloud template upgrades failed unexpectedly under particular circumstances. (#703) 20 -* Manage - Runtime statistics: Data measurements of eMagiz-Mendix Connector runtimes are not missing anymore. 21 -* Manage - Error Dashboard: Solved a problem that caused a user to see a general error when opening the Manage Dashboard while running a 3rd generation runtime architecture. 22 22 23 -====Remarks==== 24 -* Mendix Runtime has been upgraded to Mendix 9.19.0. 16 +* Capture - Add System: When a user tries to creates a system or edits a system, loading bar is displayed before showing the pop-up. (#1228) 17 +* Capture - Edit System: When editing a system, the validation now takes into account that the name cannot be an empty string. (#1562) 18 +* Design - Message Definition: small improvements are introduced: 19 +** the widget can prevent user multiple message attributes on a message entity for the same attribute in datamodel. 20 +** when adding a new message entity to a current message entity, it doesn’t throw exception when user double click to many times in Save button 21 +* Design - Catalog: When exporting swagger json, in case an operation has example in request, the example will be shown correctly in 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 are able to untransfer a flow even when there is a property attached to the flow. (#1590) 24 +* Create - Add Integrations: Flow, flow versions and the corresponding integration in the Deploy phase is cleaned when an integration is utransferred from the Create phase. 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 a property description in place. (#1526) 29 +* Deploy - Environment Template: Fixed a bug where upgrading a fully on-premise environment would incorrectly exclude some machines. 30 +* Manage - Queue Browser: Switching environments when exploring a queue in Manage → Explore now 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 that flows using code mappings may encounter errors when stopping their runtime and messages were still processed. (#1550)