Skip to Content

Changes for page 207 - Aligned State

Last modified by Carlijn Kokkeler on 2024/04/18 13:10
From version 157.1
edited by Carlijn Kokkeler
on 2023/10/10 14:06
Change comment: There is no comment for this version
To version 148.1
edited by Erik Bakker
on 2023/08/15 13:54
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -206 - Situational Deployment
1 +203 - Fast Paced
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.CarlijnKokkeler
1 +XWiki.ebakker
Content
... ... @@ -2,69 +2,43 @@
2 2  {{container layoutStyle="columns"}}(((
3 3  [[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]]
4 4  
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.
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.
6 6  
7 -== **Deployment Plan** ==
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.
8 8  
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.
11 -
12 -//__Editing release properties__//
13 -With this release, it will be possible to change the description of a property by editing the property.
14 -
15 -//__JMS memory setting check__//
16 -A change in memory settings triggers redeployment of the container now.
17 -
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.
23 -
24 -== **Store Improvements** ==
25 -
26 -
27 27  == **Feedback Items** ==
28 28  
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.
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.
31 31  
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).
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.
34 34  
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.
18 +//__Improved performance Manage Dashboards__//
19 +We have improved the efficiency with which we retrieve the data that is shown in the Manage Dashboards for the next-generation architecture.
37 37  
38 -//__Update flow designer version__//
39 -The framework used in the flow designer has been updated to the latest version.
40 -
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.
43 -
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 -
51 -
52 52  == **Bug Fixes** ==
53 53  
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.
54 54  
26 +//__Sped up adding a new operation to the API Gateway solution__//
27 +We have fixed a bug that slowed down the addition of new operations to the API Gateway solution.
28 +
55 55  == **Fancy Forum Answers** ==
56 56  
57 57  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:
58 58  
59 -* [[Getting files from subfolders (FTP)>>https://my.emagiz.com/p/question/172825635703568575||target="blank"]]
33 +* [[Issue with mail server dropping messages>>https://my.emagiz.com/p/question/172825635703530232||target="blank"]]
60 60  
61 61  == **Key takeaways** ==
62 62  
63 -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:
37 +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:
64 64  
65 65  * If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
66 66  * If you have feedback or ideas for us, talk to the Platypus
67 -* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
41 +* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
68 68  * Clear your browser cache (Ctrl + Shift + Del)
69 69  * Check out the release notes [here]
70 70  * Start thinking about how the license tracker can aid your development