Skip to Content

Changes for page 243 - Migration Magic

Last modified by Erik Bakker on 2025/06/02 09:33
From version 108.1
edited by Carlijn Kokkeler
on 2023/09/18 11:00
Change comment: There is no comment for this version
To version 237.1
edited by Erik Bakker
on 2025/03/24 14:46
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -205 - World Explorers
1 +241 - Wild West
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.CarlijnKokkeler
1 +XWiki.ebakker
Content
... ... @@ -1,71 +1,36 @@
1 -{{container}}
2 -{{container layoutStyle="columns"}}(((
3 -[[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]]
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.
4 4  
5 -**Hi there, eMagiz developers!** We have processed additional feedback on the Manage phase to ensure you can more easily create overviews of your statistics, displaying all information correctly and improving the migration process to the next-generation architecture in the Create phase slightly. On top of that, we have improved the scalability of our new generation monitoring stack and the alerting structure. We will also release a new cloud template for our next-generation infrastructure to comply with technical requirements from our cloud provider.
3 +Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.241 - Wild West.WebHome||target="blank"]].
6 6  
7 -== **Mandatory Cloud Template Upgrade - Next-generation models ** ==
5 +====Minor Changes====
8 8  
9 -As can be seen on our [[status page>>https://status.emagiz.com/incidents/dbh6g9w3ks7q||target="blank"]], we will release a new cloud template for our next-generation models (both single and double lane) that will change a configuration in these templates to comply with technical and operational requirements from our cloud provider. The announcement of the status page itself holds more detail for those to whom it pertains.
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.
13 +* Infra - Security: Improved security by implementing additional safeguards for AWS native services.
10 10  
11 -== **Feedback Items** ==
15 +====Bug fixes====
12 12  
13 -//__Improved Validation when migrating to the next-generation architecture__//
14 -To improve the migration process to the next-generation architecture, we now show a list of all reported problems, allowing the user to resolve them before migrating to the next-generation architecture.
17 +* Capture - Add System: A loading bar is displayed before showing the pop-up when a user tries to create or edit a system. (#1228)
18 +* Capture - Edit System: When editing a system, the validation now considers that the name cannot be an empty string. (#1562)
19 +* Design - Message Definition: Two minor improvements are introduced:
20 +** The widget prevents users from adding the same message attribute within a message definition multiple times.
21 +** 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.
22 +* Design - Catalog: When creating the Swagger JSON, all custom examples users add will be shown correctly when displaying the Swagger. (#1597)
23 +* 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)
24 +* Create - Add Integrations: Users can untransfer a flow even when there is a property attached to the flow. (#1590)
25 +* 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.
26 +* Create - Components: The browser page now displays the correct page title (#1509)
27 +* Create - Flow designer: When removing a wiretap from a channel, confirmation will only be asked once now. (#1549)
28 +* 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)
29 +* Deploy - Properties: Fixed a bug where property descriptions were not updated when there was already an existing property description. (#1526)
30 +* Deploy - Environment Template: Fixed a bug that caused upgrading a fully on-premise environment to exclude some machines incorrectly.
31 +* Manage - Queue Browser: Switching environments when exploring a queue in Manage → Explore moves the user to the queue browser of the correct environment. (#1408)
32 +* 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)
15 15  
16 -{{info}}Note that when no problem is found, the migration process of that runtime will start automatically.{{/info}}
34 +====Remarks====
17 17  
18 -//__Improved HTTP Statistics__//
19 -To improve the filtering and refresh functionality we offer on this overview, we have made several changes in this release that will improve the behavior of this overview.
20 -
21 -//__Show values on the runtime level in Deploy Architecture__//
22 -We have improved the values shown on the runtime (i.e., container) level in Deploy Architecture so you can better assess whether the memory configuration is still suitable for your deployed solution.
23 -
24 -{{info}}To get to the values we use different calculation methods per type of runtime, as certain runtime types have various reasons for existence.
25 -* JMS - The number of queues in the active release.
26 -* Messaging Container - The number of messaging integrations in the active release.
27 -* Messaging Connector - The number of messaging integrations related to this system in the active release.
28 -* API Gateway Container - The number of operations in the active release.
29 -* Event Streaming Container - The number of event processors in the active release.
30 -
31 -There might be multi-tenant and multi-runtime situations that do not always get to the exact number; however, this is a great improvement compared to showing no values.{{/info}}
32 -
33 -== **Bug Fixes** ==
34 -
35 -//__Gain the ability again to configure certificates in Deploy Architecture again__//
36 -In restricting the configuration options on the certificate level in one of our latter releases, it became impossible for normal users to add and edit certificates within Deploy Architecture. To resolve this problem we have now released a fix to resolve this issue, giving people the ability again to add and edit certificates under Deploy Architecture.
37 -
38 -//__Ensure that differing container configurations deploy the correct configuration__//
39 -When you run in a multi-runtime configuration and change the actual flows that need to run on container A vs. container B, it happened before that all flows were still being deployed on all runtimes. With this release, we will feed this information correctly to our infrastructure to ensure the correct and configured flows are deployed on the proper containers.
40 -
41 -//__Remove queurying options in Manage__//
42 -To avoid errors and loading problems when analyzing your statistics in Manage, we have removed the option to select a default time range spanning more than seven days. This is to guarantee the stability of the solution and to avoid users getting unnecessary errors.
43 -
44 -== **Fancy Forum Answers** ==
45 -
46 -As always, this is a gentle reminder to ask questions via the Q&A forum. The Q&A forum is available in the eMagiz iPaaS portal, so we can all benefit from the knowledge within the community. For some inspiration, take a look at these forum answers:
47 -
48 -* [[Getting files from subfolders (FTP)>>https://my.emagiz.com/p/question/172825635703568575||target="blank"]]
49 -
50 -== **Key takeaways** ==
51 -
52 -Thanks to all who helped build and those who tested and gave feedback to improve the product. To end this post, here are some key takeaways for you:
53 -
54 -* If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
55 -* If you have feedback or ideas for us, talk to the Platypus
56 -* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
57 -* Clear your browser cache (Ctrl + Shift + Del)
58 -* Check out the release notes [here]
59 -* Start thinking about how the license tracker can aid your development
60 -* Start thinking about major, minor, and patch
61 -* Upgrade to the latest build number
62 -* Keep making great integrations
63 -
64 -Let's stay in touch and till next time!
65 -
66 -{{info}}
67 -~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
68 -
69 -~*~* Indicates a next-generation-architecture only feature.
70 -{{/info}})))((({{toc/}}))){{/container}}
71 -{{/container}}
36 +* New eMagiz Connector for Queues: The new eMagiz connector has been tested in Mendix with **Java 21**, and functionality works as expected.