Skip to Content

Changes for page 208 - Controlled State

Last modified by Carlijn Kokkeler on 2024/04/18 13:10
From version 132.1
edited by Erik Bakker
on 2023/08/01 13:50
Change comment: There is no comment for this version
To version 264.1
edited by Danniar Firdausy
on 2023/11/08 16:19
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -202 - New Equilibrium
1 +208 - Controlled State
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.ebakker
1 +XWiki.dfirdausy
Content
... ... @@ -2,76 +2,68 @@
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 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.
5 +**Hi there, eMagiz developers!** We have done much work to improve the functionality of our state-generation solution so that you can have a better overview of its implementation in your environment. Next to the monitoring for the state generation implementation in your model, several feedback items revolving around user interfacing components in our platform that can improve the user experience are also released. Lastly, some performance improvements and bug fixes have also been implemented.
6 6  
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.
7 +{{warning}}State generation functionality is only accessible for models with an add-on state generation license.{{/warning}}
9 9  
10 -{{info}}For more information please check out the following microlearnings:
9 +== **State Generation - Manage overview~*~*** ==
11 11  
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"]]
11 +The following page has been added:
12 +* State generation statistics: Contains the statistics for state generation implementation in your model. The navigation to this page can be found under Manage->Monitoring page. This page provides you with graphs that explain the retrieve latency, cache size, and successful and failed retrieves, which are coming from flows using state generation components. **Note** that this menu will only show for models that have the add-on license for state generation.
15 15  
16 -Should you have any questions in advance, please get in touch with us at [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]].
17 -{{/info}}
14 +[[image:Main.Images.Release Blog.WebHome@208-release-blog-1.jpg]]
18 18  
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.
21 -
22 -[[image:Main.Images.Release Blog.WebHome@201-release-blog--apply-to-environment-example.png]]
23 -
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.
26 -
27 -[[image:Main.Images.Release Blog.WebHome@201-release-blog--breadcrumb-navigation-example.png]]
28 -
29 29  == **Feedback Items** ==
30 30  
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.
18 +//__Improved information on removing a release version__//
19 +Users are now informed with more comprehensive information about why removing a release version that is still active on all environments (i.e., Test, Acceptance, and Production) fails. Users are now informed in which environment(s) and in which runtime(s) that the release version under deletion is still running.
33 33  
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.
21 +//__Wider and expandable fields for XPath expressions__//
22 +Input fields for XPath expressions located in the Create phase are now made wider and also capable of expanding when the expression registered by the user is too long.
36 36  
37 -//__Additional help texts on Design Architecture__//
38 -We have improved the help texts in Design Architecture concerning the Event Streaming topic storage overview.
24 +//__Old images cleanup mechanism__//
25 +We implemented a functionality that removes related unused images upon removal of a release version for on-premises machines. This prevents eMagiz from taking resources from the customer’s machine due to the unattended old images.
39 39  
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.
27 +//__Consistent toggle switches__//
28 +In this release, we have updated all instances of the toggle switch to have a more consistent performance and look & feel throughout the platform.
42 42  
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.
45 -
30 +//__Consistent triggers naming__//
31 +We noticed that Trigger types have a different name throughout the portal. Therefore, in this release, on the Manage - Alerting page, we have renamed the "Source" column to "Source trigger" so that we have a consistent naming.
32 +
33 +//__Search phrase__//**
34 +We are now enabling users to search for log entries and error messages in the next-generation architecture models based on phrases containing two or more words, instead of only one word or the full sentence. This also means that the user can search for entries with distances of 2 or incomplete search phrases (e.g., “startin engine” to look for “starting servlet engine”).
35 +
36 +//__Improved image building performance__//
37 +We have implemented an improvement on the preparation step of the release at the beginning of the deployment, which leads to a faster deployment process.
38 +
39 +//__Default "errorChannel" on next-generation architecture migration__//**
40 +During a migration of a model to the next-generation architecture, we have introduced a check now for flows that did not have custom error handling to set their error channel to "errorChannel" after the migration if the custom error handling is set to false.
41 +
46 46  == **Bug Fixes** ==
47 47  
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.
44 +//__Incorrect deployed containers__//
45 +A fix has been implemented to address the issue where older containers were deployed while it was shown that the new ones were deployed. This problem was caused by auto-healing that was triggered during a new deployment.
50 50  
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.
47 +//__Log messages in next-generation architecture models__//
48 +We have implemented an improvement in our infra components that is intended to reduce the occurrence of log messages failing to be sent in the next-generation architecture models.
53 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.
50 +//__Random stuck in deployment plan execution__//
51 +We addressed an issue where the execution of the deployment plan would occasionally become stuck or halted unexpectedly.
56 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 -
60 60  == **Fancy Forum Answers** ==
61 61  
62 62  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:
63 63  
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"]]
57 +* [[(Very) large messages via eMagiz>>https://my.emagiz.com/p/question/172825635703645419||target="blank"]]
58 +* [[Existing integration sends message to onramp but they disappear before it reaches the routing>>https://my.emagiz.com/p/question/172825635703658192||target="blank"]]
67 67  
68 68  == **Key takeaways** ==
69 69  
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:
62 +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 73  * If you have feedback or ideas for us, talk to the Platypus
74 -* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
66 +* 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 76  * Check out the release notes [here]
77 77  * Start thinking about how the license tracker can aid your development
... ... @@ -84,6 +84,6 @@
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 GEN3-only feature.
79 +~*~* Indicates a next-generation-architecture only feature.
88 88  {{/info}})))((({{toc/}}))){{/container}}
89 89  {{/container}}