Skip to Content

Changes for page 241 - Wild West

Last modified by Erik Bakker on 2025/03/27 09:08
From version 227.2
edited by Erik Bakker
on 2025/02/10 09:33
Change comment: Update document after refactoring.
To version 234.1
edited by Erik Bakker
on 2025/03/24 06:40
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -238 - Preparation Paradise
1 +241 - Wild West
Content
... ... @@ -1,12 +1,31 @@
1 -In the last sprint, we focused on finishing the first iteration of our new eMagiz Mendix Connector and the first iteration of our new base image. We will first utilize the new eMagiz Mendix Connector to get an even better feeling of its performance, but you will notice a UI change straightaway. Once we have passed that hurdle, we will share more information about it and release it to a broader range of customers. Regarding the base image, we will now introduce this to our flow testing offering to see if anything unexpected happens. This is an additional safety measure we have put in place to reduce the chance of something breaking in your model once the new base image is released. On top of that, we have some minor updates to improve the quality of the platform.
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.238 - Preparation Paradise.WebHome||target="blank"]].
3 +Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.241 - Wild West.WebHome||target="blank"]].
4 4  
5 5  ====Minor Changes====
6 6  
7 -* ILM: We defined the systems labeled as “isMendix” with the “MX“ icon, making it easier to identify the Mendix system.
8 -* Create - Flow Testing: As we are finalizing the new eMagiz runtime image that will update the Spring version to Spring boot 3.4.1 and Java to 17.0.13, we are now bringing these latest updates to flow testing. This means that any flow test you execute will run on the base image your runtimes will run on after the release of the new eMagiz runtime image. If one of your test cases suddenly exhibits weird behavior that you think is due to the update, feel free to contact us via our [[support department>>mailto:support@emagiz.com]].
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.
9 9  
10 10  ====Bug fixes====
11 11  
12 -* Create - Add Integrations: Integrations using the entry/exit connector, using the same message type, can now be untransferred from the create phase. (#1591)
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)