Skip to Content

Changes for page 222 - Flee Frustration

Last modified by CarlijnKokkeler on 2024/06/05 09:31
From version 505.1
edited by CarlijnKokkeler
on 2024/05/06 13:38
Change comment: There is no comment for this version
To version 144.1
edited by Erik Bakker
on 2023/08/15 10:23
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -220 - Patch Parade
1 +203 - Fast Paced
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.CarlijnKokkeler
1 +XWiki.ebakker
Content
... ... @@ -1,88 +1,46 @@
1 1  {{container}}
2 -{{container layoutStyle="columns"}}
3 -(((
2 +{{container layoutStyle="columns"}}(((
4 4  [[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]]
5 5  
6 -**Hi there, eMagiz developers!**
5 +**Hi there, eMagiz developers!** In the last few weeks, we have processed some of the early feedback on the release properties. On top of that we have improved the scalability of our complete solution and solved various smaller feedback items.
7 7  
7 +== **Release Properties - Early Feedback** ==
8 +The release property functionality was well received by the community. However, there was still room for improvement based on some of the early feedback we received from the community. Some of these early feedback items have been addressed in this release. As a result we have updated the layout of the edit screen of a property and have updated our checks on nested properties to avoid missing properties.
9 +
8 8  == **Feedback Items** ==
9 9  
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.
12 +//__"All entries" are now cleaned up as part of the migration__//
13 +To avoid problems when removing integrations after the migration towards the next-generation architecture we now clean-up the "all-entries" as part of the migration towards the next-generation architecture.
12 12  
13 -[[image:Main.Images.Release Blog.WebHome@release-220-integration-pattern.png]]
15 +//__Trigger ID added to our alerting on the next-generation architecture__//
16 +We have added a unique trigger ID to each alert configuration to make the interpretation for our support desk much easier and better manageable.
14 14  
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.
17 -
18 -[[image:Main.Images.Release Blog.WebHome@release-220-manage-history.png]]
19 -
20 -//__Search boxes__//
21 -Search boxes in the properties overview are now shown by default.
22 -
23 -[[image:Main.Images.Release Blog.WebHome@release-220-search-boxes.png]]
24 -
25 -//__Set as mapped__//
26 -It is now possible to choose whether to set/unset all attributes of an entity as mapped in design.
27 -
28 -[[image:Main.Images.Release Blog.WebHome@release-220-mapped-entity.png]]
29 -
30 -//__SSL settings__//
31 -Changes can now be deployed on SSL level without creating a new version of a flow in Create.
32 -
33 -//__Machine deletion__//
34 -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.
35 -
36 -[[image:Main.Images.Release Blog.WebHome@release-220-machine-deletion.png]]
37 -
38 38  == **Bug Fixes** ==
39 -//__Annotation styling__//
40 -It is now possible to use enters in Annotations, so that multiple line spaces can be added, ensuring better readability.
41 41  
42 -[[image:Main.Images.Release Blog.WebHome@release-220-edit-annotation.png]]
20 +//__Ensure no flow can be in a release twice__//
21 +We have fixed a bug that could cause one flow to end up in the same release with two different flow versions. As this will break your solution on various occasions we fixed this.
43 43  
44 -//__Filter rejection warnings__//
45 -A discard channel is required for filter components when “Throw exception on rejection” value is set to false.
23 +//__Ensure no flow can be in a release twice__//
24 +We have fixed a bug that could cause one flow to end up in the same release with two different flow versions. As this will break your solution on various occasions we fixed this.
46 46  
47 -[[image:Main.Images.Release Blog.WebHome@release-220-discard-channel.png]]
48 -
49 -//__Manage Explore__//
50 -An issue has been fixed where navigating to the Explore tab in Manage would sometimes redirect users to the homepage.
51 -
52 -//__Page refreshing__//
53 -Switching between environments refreshes the Queue browser and Redelivery pages correctly for the selected environment.
54 -
55 -//__Message redelivery__//
56 -An issue has been fixed where large messages would be shown at the bottom of the page instead of the right side of the page.
57 -
58 -//__Deployment plan__//
59 -We have implemented changes that should prevent a discrepantion between the overview of runtimes to be deployed shown at the beginning of a deployment plan (or at individual machine-type steps) and the actual execution of relevant steps.
60 -
61 -//__Overview pages__//
62 -We fixed an issue that you could not navigate to the last page of some overview pages in Manage phase.
63 -
64 -//__Memory check__//
65 -Machines deleted in Design are excluded from the memory health check in Deploy, so that no unnecessary memory changes have to be done to delete machines.
66 -
67 67  == **Fancy Forum Answers** ==
68 68  
69 69  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:
70 70  
71 -* [[Create an overview of DataFlows without any datatraffic>>https://my.emagiz.com/p/question/172825635703811872||target="blank"]]
72 -* [[Flowtest does not work>>https://my.emagiz.com/p/question/172825635703811773||target="blank"]]
73 -* [[Debugger blocks all other traffic>>https://my.emagiz.com/p/question/172825635703812013||target="blank"]]
30 +* [[Issue with mail server dropping messages>>https://my.emagiz.com/p/question/172825635703530232||target="blank"]]
74 74  
75 -== **Key Takeaways** ==
32 +== **Key takeaways** ==
76 76  
77 -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:
34 +Thanks to all that helped build and those who tested and gave feedback to improve the product. To end this post, here are some key takeaways for you:
78 78  
79 79  * If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
80 80  * If you have feedback or ideas for us, talk to the Platypus
81 -* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
38 +* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
82 82  * Clear your browser cache (Ctrl + Shift + Del)
83 -* Check out the release notes [[here>>doc:Main.Release Information.Portal.219 - Creation Carousel.WebHome||target="blank"]]
40 +* Check out the release notes [here]
84 84  * Start thinking about how the license tracker can aid your development
85 85  * Start thinking about major, minor, and patch
43 +* Upgrade to the latest build number
86 86  * Keep making great integrations
87 87  
88 88  Let's stay in touch and till next time!
... ... @@ -90,11 +90,6 @@
90 90  {{info}}
91 91  ~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
92 92  
93 -{{/info}}
94 -)))
95 -
96 -(((
97 -{{toc/}}
98 -)))
51 +~*~* Indicates a next-generation-architecture only feature.
52 +{{/info}})))((({{toc/}}))){{/container}}
99 99  {{/container}}
100 -{{/container}}