Changes for page 243 - Migration Magic

Last modified by Erik Bakker on 2025/06/02 09:33

From version 13.1
edited by Erik Bakker
on 2022/10/24 13:35
Change comment: There is no comment for this version
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 -186 - Daemon Switch
1 +241 - Wild West
Content
... ... @@ -1,35 +1,31 @@
1 -The release brings the new monitoring stack to fruition and various updates to handling multiple namespaces. On top of that, we have released a sleuth of smaller feedback items and bug fixes.
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.186 - Daemon Switch.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 -=====New features=====
6 -* Generic - New monitoring stack: As of this release, you can run on the new monitoring stack. For more information on becoming an early adopter, don't hesitate to get in touch with us at productmanagement@emagiz.com
5 +====Minor Changes====
7 7  
8 -=====Minor changes=====
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 -* Create - Flow designer: You can now see who/when a resource was changed on a resource view page.
11 -* Design - Solution: You will see a warning in the Solution view on operation if it is not connected to a backend API operation or in "Transformation" mode.
12 -* Create - Flow designer: You can see all related configurations that use a specific resource when viewing the details of the resource.
13 -* Design - API Gateway: Changes in your Gateway messages are reflected directly in your OpenAPI JSON document.
14 -* Model Dashboard - Going to manage from the model dashboard now loads the error message dashboard without having to click on the error messages dashboard explicitly
15 -* Create - Flow testing: The name of the starting point in the flow testing result tab is matched with the component type.
16 -* Deploy - Releases: The automated flow test pop-up can now be closed by pressing "Enter."
17 -* Deploy - Properties: Password-type properties are masked in the unused properties pop-up.
18 -* Deploy - User management: "Generate Keystore" button is renamed "Download Keystore," and the file name contains environment information.
19 -* Create - Flow Testing: Added a button to display the content of a selected trace message in a pop-out.
20 -* Deploy - Properties: You can use enter key to search on the property overview page.
21 -* Create - Flow designer: Increased size of the SpEL expression input field of standard transformer component.
22 -* Create - Flow Designer: Show generated resources toggle is not disabled by default; your preference for showing or hiding generated resources will be saved.
23 -* Administration - Licenses: Added event streaming storage usage of your models.
24 -* Store: Compatibility check is added, which prevents importing G3 store items into G2 flow/integration
25 -* General: Improved help texts explaining options and screens related to the new runtime architecture or the migration towards it.
26 -
27 27  ====Bug fixes====
28 -* Deploy - Properties: Improved the layout of the cron trigger generator page
29 -* Deploy - Properties: Generating a password or CRON trigger will not reset the runtime field
30 -* Create - Flow designer: While editing an exit flow, the system message is not editable.
31 -* Design - Integration designer: For event streaming integrations, switching between Design Mapping and Create Transformation sometimes did not work.
32 -* Create - Transformation: For event streaming integrations, the 'Start editing' button sometimes did not work.
33 -* Create - Flow designer: Comparing two flow versions works again.
34 -* Create- Flow Designer: When creating my initial version of a flow, the notification pop-up shows the correct information.
35 -* Create - Flow Designer: All relevant support objects will be highlighted when selecting a support object.
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 +* 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)