Skip to Content

Changes for page 226 - Alerting Alchemy

Last modified by CarlijnKokkeler on 2024/07/30 16:40
From version 242.1
edited by CarlijnKokkeler
on 2023/11/21 11:09
Change comment: There is no comment for this version
To version 528.1
edited by CarlijnKokkeler
on 2024/05/21 11:57
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -209 - Max Verstappen
1 +221 - Swift Shift
Content
... ... @@ -1,72 +1,58 @@
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 done .....
6 +**Hi there, eMagiz developers!** This release, we have done several improvements for failover and grouping, as well as for the placement of attributes in datamodels. Next to this, we have improved the Event Catalog overview for Catalog users. It is now also possible to use the back button on the eMagiz Q&A without your search being removed. Regarding bug fixes, the delete behaviour for containers has been improved, and scope properties will now be generated correctly. Lastly, the warning message that is given when importing an xsd has now been removed when the request or response message is empty.
6 6  
7 -== **Next Generation Architecture Default** ==
8 -With this release, the next generation architecture will become the default. New models will use this generation as default.
9 -
10 -[[image:Main.Images.Release Blog.WebHome@release-blog-next-gen-default.png]]
11 -
12 -== **Cloud Template R11 - Single Lane** ==
13 -This release introduces a new cloud template for all our customers running in a single-lane setup on the next generation architecture. This cloud template introduces faster machine boot up and improved auto-healing. The complete release notes on the cloud template can be found here
14 -
15 -== **Cloud Template R13 - Double Lane** ==
16 -
17 -
18 18  == **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.
19 19  
20 -//__Unused properties overview__//
21 -In Deploy > Releases, it is now possible to see all unused properties of an environment. This can be viewed by clicking the three dots in the Create phase section. Here it is also possible to quickly delete all or a selection of those unused properties. Unused properties are properties that are:
22 -* Not used by any runtime that is in the Create phase release.
23 -* Not required by a flow that is in the Create phase release.
24 -* If used as nested property, none of its parent properties (checks recursively) are in the Create phase release.
12 +//__Event catalog__//
13 +For Catalog users, we have significantly improved the Event Catalog overview by introducing a much simpler layout for easier navigation.
25 25  
26 -//__Send build requests asynchronously__//
27 -The step in the deployment plan concerning the preparation of runtime images will now be executed more quickly and reliably.
15 +[[image:Main.Images.Release Blog.WebHome@release-221-swift-shift-catalog-2.png]]
28 28  
29 -//__Queue explorer milliseconds__//
30 -The queue browser now displays milliseconds in the timestamps.
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.
31 31  
32 -//__Cancel and next buttons order__//
33 -The order of the cancel and next buttons when creating a new trigger has been changed to increase alignment across the platform. Now, all cancel buttons are placed on the right of a 'next' or 'save' button.
23 +[[image:Main.Images.Release Blog.WebHome@release-221-swift-shift-rearrange-attribute.png]]
34 34  
35 -//__Unused images__//
36 -When a release is removed, the related unused images in the on-premises machines will be removed as well.
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".
37 37  
38 -//__Carwash logging__//
39 -A new logging feature enabling us to make better choices in encryption standards will be released.
30 +[[image:Main.Images.Release Blog.WebHome@release-221-start-stop-flows.png]]
40 40  
41 -//__Static alerts queue consumers__//
42 -Alerting will now only generate alerts for queues that are created and managed by the eMagiz JMS server.
32 +[[image:Main.Images.Release Blog.WebHome@release-221-stop-groups.png]]
43 43  
44 44  == **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.
45 45  
46 -//__Images rebuild__//
47 -We fixed an issue which caused the release preparation step to take longer time than necessary and caused the machine deployment steps to execute when they could be skipped.
38 +[[image:Main.Images.Release Blog.WebHome@release-221-swift-shift-xsd.png]]
48 48  
49 -//__Flow Designer connection line__//
50 -In the Flow Designer an issue has been fixed where the connection line for drawing channels did work well when scrolling or zooming in/out on the canvas.
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.
51 51  
52 -//__Portal for migrated models__//
53 -We fixed a rare case where a runtime could not start, or logging, errors and metrics could not be seen in the portal for a model that had just migrated to the next generation architecture.
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.
54 54  
55 -//__Error channel inbounds__//
56 -We added a migration step, where we set the error channel to “errorChannel” of all inbounds in a flow if the custom error handling is set to false. Before, the error channel would be set to “errorChannel” only for the first inbound in an entry flow.
57 -
58 58  == **Fancy Forum Answers** ==
59 59  
60 60  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:
61 61  
62 -* [[Message Redelivery blank error message>>https://my.emagiz.com/p/question/172825635703619933||target="blank"]]
63 -* [[Timeout error kafka batch creation>>https://my.emagiz.com/p/question/172825635703620012||target="blank"]]
64 -* [[SFTP Connectivity: Transfering a whole folder structure>>https://my.emagiz.com/p/question/172825635703632587||target="blank"]]
65 -* [[Next generation architecture with dynamic file pickup / filedrop>>https://my.emagiz.com/p/question/172825635703632732||target="blank"]]
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"]]
66 66  
54 +== **Key Takeaways** ==
67 67  
68 -== **Key takeaways** ==
69 -
70 70  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:
71 71  
72 72  * If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
... ... @@ -73,10 +73,9 @@
73 73  * If you have feedback or ideas for us, talk to the Platypus
74 74  * Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
75 75  * Clear your browser cache (Ctrl + Shift + Del)
76 -* Check out the release notes [here]
62 +* Check out the release notes [[here>>doc:Main.Release Information.Portal.220 - Patch Parade.WebHome||target="blank"]]
77 77  * Start thinking about how the license tracker can aid your development
78 78  * Start thinking about major, minor, and patch
79 -* Upgrade to the latest build number
80 80  * Keep making great integrations
81 81  
82 82  Let's stay in touch and till next time!
... ... @@ -84,6 +84,11 @@
84 84  {{info}}
85 85  ~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
86 86  
87 -~*~* Indicates a next-generation-architecture only feature.
88 -{{/info}})))((({{toc/}}))){{/container}}
72 +{{/info}}
73 +)))
74 +
75 +(((
76 +{{toc/}}
77 +)))
89 89  {{/container}}
79 +{{/container}}