Skip to Content

Changes for page 241 - Wild West

Last modified by Erik Bakker on 2025/03/27 09:08
From version 234.1
edited by Erik Bakker
on 2025/03/24 06:40
Change comment: There is no comment for this version
To version 238.1
edited by Erik Bakker
on 2025/03/27 09:08
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -1,31 +1,41 @@
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.
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 3  Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.241 - Wild West.WebHome||target="blank"]].
4 4  
5 +====New Features====
6 +
7 +* Deploy - Releases: A comparison feature for the Deploy phase is added. The comparison feature allows users to compare releases to track the differences in property values of those releases. The feature also provides information on who made the changes. The differences are categorized by “InRelease” and “NotInRelease,” which means that the additional property value is either in the first selected release (InRelease) or the second selected release (NotInRelease).
8 +** This functionality only works for releases created **after** this release.
9 +
5 5  ====Minor Changes====
6 6  
7 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.
13 +* 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)
14 +* 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 10  * Create - Flow designer: Display name character limitations are visible in the validation feedback when adding new flow components (#1554)
11 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 12  * Deploy - Deployment Plan Execution: We have improved the stability of the deployment plan procedure.
18 +* Infra - Security: Improved security by implementing additional safeguards for AWS native services.
13 13  
14 14  ====Bug fixes====
15 15  
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 +* Capture - Add System: A loading bar is displayed before showing the pop-up when a user tries to create or edit a system. (#1228)
23 +* Capture - Edit System: When editing a system, the validation now considers that the name cannot be an empty string. (#1562)
24 +* Design - Message Definition: Two minor improvements are introduced:
25 +** The widget prevents users from adding the same message attribute within a message definition multiple times.
26 +** 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.
27 +* Design - Catalog: When creating the Swagger JSON, all custom examples users add will be shown correctly when displaying the Swagger. (#1597)
22 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.
29 +* Create - Add Integrations: Users can untransfer a flow even when there is a property attached to the flow. (#1590)
30 +* 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 25  * Create - Components: The browser page now displays the correct page title (#1509)
26 26  * Create - Flow designer: When removing a wiretap from a channel, confirmation will only be asked once now. (#1549)
27 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)
34 +* Deploy - Properties: Fixed a bug where property descriptions were not updated when there was already an existing property description. (#1526)
35 +* Deploy - Environment Template: Fixed a bug that caused upgrading a fully on-premise environment to exclude some machines incorrectly.
36 +* Manage - Queue Browser: Switching environments when exploring a queue in Manage → Explore moves the user to the queue browser of the correct environment. (#1408)
37 +* 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)
38 +
39 +====Remarks====
40 +
41 +* New eMagiz Connector for Queues: The new eMagiz connector has been tested in Mendix with **Java 21**, and functionality works as expected.