Skip to Content

Changes for page 222 - Flee Frustration

Last modified by CarlijnKokkeler on 2024/06/05 09:31
From version 530.1
edited by CarlijnKokkeler
on 2024/05/21 12:11
Change comment: There is no comment for this version
To version 158.1
edited by CarlijnKokkeler
on 2023/10/10 14:19
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -221 - Swift Shift
1 +206 - Situational Deployment
Content
... ... @@ -1,57 +1,64 @@
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!** 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.
5 +**Hi there, eMagiz developers!** In the last few weeks, we have done much work for the Deploy phase. On top of that, we have worked on several store functionalities. Next to this, we have several smaller feedback items from our hackathon efforts that are now released to you.
7 7  
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.
7 +== **Deployment Plan** ==
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.
9 +//__Improved deployment plan to make the process better and more predictable__//
10 +The algorithm for genarating a default deployment plan is improved to keep jms downtime and alerting to a minimum. Next to this, the start/stop/restart machine deployment steps are now also executed correctly for aws and on-premises machines.
14 14  
15 -[[image:Main.Images.Release Blog.WebHome@release-221-swift-shift-catalog-2.png]]
12 +//__Editing release properties__//
13 +With this release, it will be possible to change the description of a property by editing the property.
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 a 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.
15 +//__JMS memory setting check__//
16 +A change in memory settings triggers redeployment of the container now.
22 22  
23 -[[image:Main.Images.Release Blog.WebHome@release-221-swift-shift-rearrange-attribute.png]]
18 +//__Properties tab__//
19 +We have removed the deprecated tab Properties in the Deploy phase.
20 +
21 +//__Cleanup old images__//
22 +When a release is removed, the related unused images in the on-premises machines will be removed as well.
24 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".
24 +== **Store Improvements** ==
25 +
29 29  
30 -[[image:Main.Images.Release Blog.WebHome@release-221-start-stop-flows.png]]
27 +== **Feedback Items** ==
31 31  
32 -[[image:Main.Images.Release Blog.WebHome@release-221-stop-groups.png]]
29 +//__Alerting manual pause__//
30 +A few releases ago we changed the behavior of alerting in the deployment plan. Now each time when a deployment plan is executed the alerting will be automatically re-enabled when the deployer closes the deployment plan or closes the web browser. The majority of the users are happy with the new behavior, but there are some use cases that you do not want start the alerting immediately. With this release, if alerting has been paused manually, this will not be activated automatically after a release deployment.
33 33  
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.
32 +//__Ordering of graphs in Manage__//
33 +The graphs in Manage are now ordered according to importance. This means that runtime statistics are sorted by "Process CPU usage" (highest first), queue statistics are sorted by "Messages in queue" (highest first), and HTTP statistics are sorted by "Unsuccessful requests" (highest first).
37 37  
38 -[[image:Main.Images.Release Blog.WebHome@release-221-swift-shift-xsd.png]]
35 +//__UTC times in Grafana panels__//
36 +All Grafana panels now show UTC times, which are normally used in eMagiz, instead of local (browser) time zones. This way, it is easier to match graphs with logging events or alerts.
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.
38 +//__Update flow designer version__//
39 +The framework used in the flow designer has been updated to the latest version.
42 42  
43 -//__Scope properties__//
44 -We fixed an issue where the generation of scope properties was incorrect for legacy API gateway runtimes using OAuth 2.0 security scheme.
41 +//__Carwash track TLS versions in logging__//
42 +A new logging feature will be released, enabling us to make better choices in deprecating old encryption standards.
45 45  
44 +//__Moving channels in the flow designer__//
45 +Moving already attached channels in the flow designer has been made sligthly easier.
46 +
47 +//__Topic sizes description change__//
48 +In the change description (and History) when altering the topic size of a topic the new and old value were switched around creating confusion, this has been resolved.
49 +
50 +//__Topic sizes description change__//
51 +
52 +== **Bug Fixes** ==
53 +
54 +
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"]]
59 +* [[Getting files from subfolders (FTP)>>https://my.emagiz.com/p/question/172825635703568575||target="blank"]]
53 53  
54 -== **Key Takeaways** ==
61 +== **Key takeaways** ==
55 55  
56 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:
57 57  
... ... @@ -59,9 +59,10 @@
59 59  * If you have feedback or ideas for us, talk to the Platypus
60 60  * 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"]]
69 +* 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
72 +* 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 -)))
80 +~*~* Indicates a next-generation-architecture only feature.
81 +{{/info}})))((({{toc/}}))){{/container}}
78 78  {{/container}}
79 -{{/container}}