Skip to Content

Changes for page 222 - Flee Frustration

Last modified by CarlijnKokkeler on 2024/06/05 09:31
From version 151.1
edited by Erik Bakker
on 2023/09/13 07:02
Change comment: There is no comment for this version
To version 498.1
edited by CarlijnKokkeler
on 2024/05/06 12:56
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -205 - World Explorers
1 +220 - Patch Parade
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.ebakker
1 +XWiki.CarlijnKokkeler
Content
... ... @@ -1,62 +1,55 @@
1 1  {{container}}
2 -{{container layoutStyle="columns"}}(((
2 +{{container layoutStyle="columns"}}
3 +(((
3 3  [[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]]
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.
6 +**Hi there, eMagiz developers!**
6 6  
7 -== ** Mandatory Cloud Template Upgrade - Next-generation models ** ==
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.
10 -
11 11  == **Feedback Items** ==
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.
10 +//__Integration pattern information__//
11 +Integration pattern information of the selected message type has been added to the pop-up that is shown in Capture when creating a new integration.
15 15  
16 -{{info}}Note that when no problem is found, the migration process of that runtime will start automatically.{{/info}}
13 +[[image:Main.Images.Release Blog.WebHome@release-220-integration-pattern.png]]
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.
15 +//__Message queue history__//
16 +All events that relate to message queues (delete message, delete all messages or delete queue) are logged in the Manage phase instead of the Deploy phase.
20 20  
21 -//__"Topic Full" alert restriction changed__//
22 -With this release, we will change the "Topic Full" trigger point in our standard set of alerts once a model uses the Event Streaming functionality. Before, the alert would trigger on 80%, but as we saw, this is too early to make the alert useful in the context of our customers. As a result, the threshold has been raised to 95% to accommodate real-life situations better.
18 +[[image:Main.Images.Release Blog.WebHome@release-220-manage-history.png]]
23 23  
24 -//__Improved performance Manage Dashboards__//
25 -We have improved the efficiency of retrieving the data shown in the Manage Dashboards for the next-generation architecture.
20 +//__Search boxes__//
21 +Search boxes in the properties overview are now shown by default.
26 26  
27 -//__Show values on the runtime level in Deploy Architecture__//
28 -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 +[[image:Main.Images.Release Blog.WebHome@release-220-search-boxes.png]]
29 29  
30 -{{info}}To get to the values we use different calculation methods per type of runtime, as certain runtime types have various reasons for existence.
31 -* JMS - The number of queues in the active release.
32 -* Messaging Container - The number of messaging integrations in the active release.
33 -* Messaging Connector - The number of messaging integrations related to this system in the active release.
34 -* API Gateway Container - The number of operations in the active release.
35 -* Event Streaming Container - The number of event processors in the active release.
25 +//__Set as mapped__//
26 +It is now possible to choose whether to set/unset all attributes of an entity as mapped in design.
36 36  
37 -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}}
28 +[[image:Main.Images.Release Blog.WebHome@release-220-mapped-entity.png]]
38 38  
30 +//__SSL settings__//
31 +Changes can now be deployed on SSL level without creating a new version of a flow in Create.
32 +
39 39  == **Bug Fixes** ==
34 +//__Annotation styling__//
35 +It is now possible to use enters in Annotations, so that multiple line spaces can be added, ensuring better readability.
40 40  
41 -//__Improved information Queue Statistics__//
42 -Given several constraints, it could happen that specific queues needed to be correctly displayed within the Manage phase on your model, making it tough to manage them. This has been resolved with this release.
37 +[[image:Main.Images.Release Blog.WebHome@release-220-edit-annotation.png]]
43 43  
44 -//__Gain the ability again to configure certificates in Deploy Architecture again__//
45 -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.
39 +//__Filter rejection warnings__//
40 +A discard channel is required for filter components when “Throw exception on rejection” value is set to false.
46 46  
47 -//__Ensure that differing container configurations deploy the correct configuration__//
48 -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.
42 +[[image:Main.Images.Release Blog.WebHome@release-220-discard-channel.png]]
49 49  
50 -//__Remove queurying options in Manage__//
51 -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.
52 -
53 53  == **Fancy Forum Answers** ==
54 54  
55 55  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:
56 56  
57 -* [[Getting files from subfolders (FTP)>>https://my.emagiz.com/p/question/172825635703568575||target="blank"]]
48 +* [[Create an overview of DataFlows without any datatraffic>>https://my.emagiz.com/p/question/172825635703811872||target="blank"]]
49 +* [[Flowtest does not work>>https://my.emagiz.com/p/question/172825635703811773||target="blank"]]
50 +* [[Debugger blocks all other traffic>>https://my.emagiz.com/p/question/172825635703812013||target="blank"]]
58 58  
59 -== **Key takeaways** ==
52 +== **Key Takeaways** ==
60 60  
61 61  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:
62 62  
... ... @@ -64,10 +64,9 @@
64 64  * If you have feedback or ideas for us, talk to the Platypus
65 65  * Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
66 66  * Clear your browser cache (Ctrl + Shift + Del)
67 -* Check out the release notes [here]
60 +* Check out the release notes [[here>>doc:Main.Release Information.Portal.219 - Creation Carousel.WebHome||target="blank"]]
68 68  * Start thinking about how the license tracker can aid your development
69 69  * Start thinking about major, minor, and patch
70 -* Upgrade to the latest build number
71 71  * Keep making great integrations
72 72  
73 73  Let's stay in touch and till next time!
... ... @@ -75,6 +75,11 @@
75 75  {{info}}
76 76  ~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
77 77  
78 -~*~* Indicates a next-generation-architecture only feature.
79 -{{/info}})))((({{toc/}}))){{/container}}
70 +{{/info}}
71 +)))
72 +
73 +(((
74 +{{toc/}}
75 +)))
80 80  {{/container}}
77 +{{/container}}