Skip to Content

Changes for page 222 - Flee Frustration

Last modified by CarlijnKokkeler on 2024/06/05 09:31
From version 527.1
edited by CarlijnKokkeler
on 2024/05/21 11:46
Change comment: There is no comment for this version
To version 145.1
edited by Erik Bakker
on 2023/08/15 11:35
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -221 - Swift Shift
1 +203 - Fast Paced
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.CarlijnKokkeler
1 +XWiki.ebakker
Content
... ... @@ -1,67 +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!** We have processed some early feedback on the release properties in the last few weeks. 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 community well received the release property functionality. However, there was still room for improvement based on some of the early feedback from the community. Some of these early feedback items have been addressed in this release. As a result, we have updated the layout of a property's edit screen and our checks on nested properties to avoid missing properties.
9 +
8 8  == **Feedback Items** ==
9 -//__Q&A search__//
10 -Search results are now persisted when pressing the back button after opening a question in the community Q & A.
11 11  
12 -//__Event catalog__//
13 -For Catalog users, we have significantly improved the Event Catalog overview by introducing a much simpler layout for easier navigation.
12 +//__"All entries" are now cleaned up as part of the migration__//
13 +To avoid problems when removing integrations after migrating toward the next-generation architecture, we now clean up the "all-entries" as part of the migration towards the next-generation architecture.
14 14  
15 -[[image:Main.Images.Release Blog.WebHome@release-221-swift-shift-catalog-2.png]]
15 +//__Trigger ID added to our alerting on the next-generation architecture__//
16 +We added a unique trigger ID to each alert configuration to make the interpretation for our support desk much easier and more manageable.
16 16  
17 -//__Attribute placements__//
18 -Some improvements regarding the placement of attributes have been done:
19 -* A new attribute will be placed right below the attribute that users right-clicked on to open context menu to add new attribute.
20 -* Moving an attribute in the datamodel is now directly shown in the tree structure as well.
21 -* The pop-up that appears when rearranging attributes of an entity will result in a pop-up which text is conditional with respect to the messagetype.
22 -
23 -[[image:Main.Images.Release Blog.WebHome@release-221-swift-shift-rearrange-attribute.png]]
24 -
25 -//__Failover & grouping__//
26 -Some improvements regarding the widgets for failover and grouping have been done:
27 -* When executing a start/stop action on a group, the description of the step now contains the name of the group.
28 -* When stopping a group with the follower status, the description of the popup now correctly describes the purpose of button "Disable failover and stop group".
29 -
30 -[[image:Main.Images.Release Blog.WebHome@release-221-start-stop-flows.png]]
31 -
32 -[[image:Main.Images.Release Blog.WebHome@release-221-stop-groups.png]]
33 -
34 34  == **Bug Fixes** ==
35 -//__XSD import__//
36 -When importing an xsd to a new response or request message, you will not receive a warning message anymore to avoid confusion.
37 37  
38 -[[image:Main.Images.Release Blog.WebHome@release-221-swift-shift-xsd.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.
39 39  
40 -//__Container deletion__//
41 -The delete behaviour of containers in the container overview has been improved to allow deletion of unused containers with broken flows.
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.
42 42  
43 -//__Scope properties__//
44 -We fixed an issue where the generation of scope properties was incorrect for the legacy API gateway runtimes using OAuth 2.0 security scheme.
45 -
46 46  == **Fancy Forum Answers** ==
47 47  
48 48  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:
49 49  
50 -* [[OAuth 2.0, 403 Forbidden>>https://my.emagiz.com/p/question/172825635703837388||target="blank"]]
51 -* [[HTTP request without reply>>https://my.emagiz.com/p/question/172825635703837492||target="blank"]]
52 -* [[All-entry API gateway is not starting>>https://my.emagiz.com/p/question/172825635703837607||target="blank"]]
30 +* [[Issue with mail server dropping messages>>https://my.emagiz.com/p/question/172825635703530232||target="blank"]]
53 53  
54 -== **Key Takeaways** ==
32 +== **Key takeaways** ==
55 55  
56 -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:
57 57  
58 58  * If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
59 59  * If you have feedback or ideas for us, talk to the Platypus
60 -* 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.
61 61  * Clear your browser cache (Ctrl + Shift + Del)
62 -* Check out the release notes [[here>>doc:Main.Release Information.Portal.220 - Patch Parade.WebHome||target="blank"]]
40 +* Check out the release notes [here]
63 63  * Start thinking about how the license tracker can aid your development
64 64  * Start thinking about major, minor, and patch
43 +* Upgrade to the latest build number
65 65  * Keep making great integrations
66 66  
67 67  Let's stay in touch and till next time!
... ... @@ -69,11 +69,6 @@
69 69  {{info}}
70 70  ~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
71 71  
72 -{{/info}}
73 -)))
74 -
75 -(((
76 -{{toc/}}
77 -)))
51 +~*~* Indicates a next-generation-architecture only feature.
52 +{{/info}})))((({{toc/}}))){{/container}}
78 78  {{/container}}
79 -{{/container}}