Skip to Content

Changes for page 220 - Patch Parade

Last modified by Carlijn Kokkeler on 2024/05/22 13:30
From version 242.1
edited by Carlijn Kokkeler
on 2024/05/06 14:23
Change comment: There is no comment for this version
To version 108.1
edited by Carlijn Kokkeler
on 2023/09/18 11:00
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -220 - Patch Parade
1 +205 - World Explorers
Content
... ... @@ -1,25 +1,71 @@
1 -In the last sprint cycle, we have worked on a new [[runtime image>>doc:Main.Release Information.Runtime Images.V306.WebHome||target="blank"]] that contains a fix for an issue regarding SFTP sessions. Furthermore, we did several small improvements and many bug fixes.
1 +{{container}}
2 +{{container layoutStyle="columns"}}(((
3 +[[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]]
2 2  
3 -Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.220 - Patch Parade||target="blank"]].
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.
4 4  
5 -===== New features =====
7 +== **Mandatory Cloud Template Upgrade - Next-generation models ** ==
6 6  
7 -* Capture - Integrations: Information about the integration pattern of a selected message type has been added to the new integration pop-up. (#1214)
8 -* Design - Architecture: When trying to delete a machine that still has containers linked to it, the user will be presented with a pop-up explaining why the machine cannot be deleted. (#1296)
9 -* Create - Flow designer: A discard channel is required for filter components when “Throw exception on rejection” value is set to false.
10 -* Deploy - Architecture: Changes can now be deployed on SSL level without creating a new version of a flow in Create.
11 -* Deploy - Releases: Search boxes in the properties overview are now shown by default. (#1325)
12 -* Manage - Explore: We fixed an issue where navigating to the “Explore” tab in “Manage” phase would sometimes redirect users to the homepage.(#1237)
13 -* Manage - History: All events that relate to message queues (delete message, delete all messages or delete queue) are now logged in the Manage phase instead of the Deploy phase. (#1278)
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.
14 14  
15 -===== Bug fixes =====
11 +== **Feedback Items** ==
16 16  
17 -* Design - Message mapping: It is now possible to choose whether to set/unset all attributes of an entity as mapped in design. (#1179)
18 -* Create - Flow designer: It is now possible to use enters in Annotations, so that multiple line spaces can be added, ensuring better readability. (#852)
19 -* Create - Flow designer: The copy to clipboard button now copies the actual value of passwords instead of the masked value of them. (#1303)
20 -* Deploy - Architecture: Machines deleted in Design are excluded from the memory health check. (#1282)
21 -* Deploy - Architecture: Kafka outbound channel adapters can now also parse jms_destination and jms_replyTo headers. For this fix, a new [[runtime image>>doc:Main.Release Information.Runtime Images.V306.WebHome||target="blank"]] has been released.
22 -* Deploy- Deployment plan: We have implemented changes that should prevent the overview of runtimes to be deployed shown at the beginning of a deployment plan (or at individual machine-type steps) to not correspond with the actual execution of relevant steps. (#1315)
23 -* Manage - Explore: Switching between environments refreshes the Queue browser and Redelivery pages correctly for the selected environment. (#1287)
24 -* Manage - Overview pages: We fixed an issue that you could not navigate to the last page of some overview pages in Manage phase. (#1122)
25 -* Manage - Redelivery: We fixed an issue where a large message would be shown at the bottom of the Redelivery page instead of the right side of the page. (#1290)
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.
15 +
16 +{{info}}Note that when no problem is found, the migration process of that runtime will start automatically.{{/info}}
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}}