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 132.1
edited by Erik Bakker
on 2023/08/01 13:50
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -206 - Situational Deployment
1 +202 - New Equilibrium
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.CarlijnKokkeler
1 +XWiki.ebakker
Content
... ... @@ -2,69 +2,76 @@
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!** In the last few weeks, we have crossed our t's and dotted our i's on the release properties functionality that will impact the day to day life of every user working within the platform. The focus of the release blog will consequently also be on this subject. On top of that we have several additional smaller feedback item coming from our hackathon efforts that are now released to you.
6 6  
7 -== **Deployment Plan** ==
7 +== **Release Properties** ==
8 +As of this release, we will introduce a new way of handling properties for all our clients. There are several key changes compared to the current way of managing your 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.
10 +{{info}}For more information please check out the following microlearnings:
11 11  
12 -//__Editing release properties__//
13 -With this release, it will be possible to change the description of a property by editing the property.
12 +* [[microlearning>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.crashcourse-platform-deploy-property-management-new.WebHome||target="blank"]]
13 +* [[microlearning>>doc:Main.eMagiz Academy.Microlearnings.Novice.eMagiz Store.novice-emagiz-store-merge-store-data-model.WebHome||target="blank"]]
14 +* [[microlearning>>doc:Main.eMagiz Academy.Microlearnings.Novice.eMagiz Store.novice-emagiz-store-merge-store-data-model.WebHome||target="blank"]]
14 14  
15 -//__JMS memory setting check__//
16 -A change in memory settings triggers redeployment of the container now.
16 +Should you have any questions in advance, please get in touch with us at [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]].
17 +{{/info}}
17 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.
19 +== ** Deploy Architecture - Apply To Environment improvements ** ==
20 +As of this release, we will show you a list of all changes about to be changed once you press "Apply to the environment" in Deploy Architecture. This will make it clearer for users, especially those working in teams, what will change when pressing this button.
23 23  
24 -== **Store Improvements** ==
25 -
22 +[[image:Main.Images.Release Blog.WebHome@201-release-blog--apply-to-environment-example.png]]
26 26  
27 -== **Feedback Items** ==
24 +== ** Breadcrumb navigation in eMagiz ** ==
25 +This release introduces the "breadcrumb" navigation in certain parts of eMagiz. This will mostly be noticed and impact the Create phase when you check out your transformation or system message on the flow level. Apart from there, the navigation is implemented consistently across the portal for a unified look and feel.
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.
27 +[[image:Main.Images.Release Blog.WebHome@201-release-blog--breadcrumb-navigation-example.png]]
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).
29 +== **Feedback Items** ==
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.
31 +//__Improved layout of catalog page in Design__//
32 +We have improved the layout of the API Catalog overview in Design for our API Gateway users. Among others, we have introduced a scrollbar to get a better overview of several operations.
37 37  
38 -//__Update flow designer version__//
39 -The framework used in the flow designer has been updated to the latest version.
34 +//__Improved layout of "Edit integration" pop-up for API Gateway integrations__//
35 +Currently, the full path of your backend system will be shown when opening the "Edit integration" pop-up on your API Gateway integration.
40 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.
37 +//__Additional help texts on Design Architecture__//
38 +We have improved the help texts in Design Architecture concerning the Event Streaming topic storage overview.
43 43  
44 -//__Moving channels in the flow designer__//
45 -Moving already attached channels in the flow designer has been made sligthly easier.
40 +//__Improved Audit Trail on several places__//
41 +In several places in the portal, we have improved the audit trail to specify better who changed what at which point in time.
46 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.
43 +//__Removed the erroneous alert on message mapping when having a passthrough API__//
44 +This release removes the erroneous alert people reported on "errors in message mapping" for a passthrough API.
49 49  
50 -
51 -
52 52  == **Bug Fixes** ==
53 53  
48 +//__Avoid clicking on other components while deleting another__//
49 +To avoid unexpected behavior, we now ensure that nothing can be selected once you see the "deletion" pop-up when you want to remove something in the flow designer.
54 54  
51 +//__Improved validation feedback in migrating to the next-generation architecture__//
52 +We have improved the validation feedback when migrating to the next-generation architecture.
53 +
54 +//__Make sure that user credentials can be viewed with view rights__//
55 +This release makes sure that the user credentials in Deploy can be considered with view rights and not only when having edit rights.
56 +
57 +//__Refresh behavior within the deployment plan is fixed__//
58 +This release changes the refresh behavior within the deployment plan to show, once more, the "to be installed" flows before the user presses Execute.
59 +
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"]]
64 +* [[Replacing Legacy eMagiz-Mendix Connector: Migration Plan>>https://my.emagiz.com/p/question/172825635703517317||target="blank"]]
65 +* [[Unknown character(s) does not create error message.>>https://my.emagiz.com/p/question/172825635703517488||target="blank"]]
66 +* [[Split gateway configuration for local GEN3 gateway>>https://my.emagiz.com/p/question/172825635703517580||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:
70 +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.
74 +* 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
... ... @@ -77,6 +77,6 @@
77 77  {{info}}
78 78  ~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
79 79  
80 -~*~* Indicates a next-generation-architecture only feature.
87 +~*~* Indicates a GEN3-only feature.
81 81  {{/info}})))((({{toc/}}))){{/container}}
82 82  {{/container}}