Changes for page 207 - Aligned State

Summary

• Page properties (2 modified, 0 added, 0 removed)

Details

Page properties

Title

...	...	@@ -1,1 +1,1 @@
1		-205 - World Explorers
	1	+201 - Be Informed

Content

...	...	@@ -2,67 +2,67 @@
2	2	{{container layoutStyle="columns"}}(((
3	3	[[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]]
4	4
5		-**Hi there, eMagiz developers!** We have processed additional feedback on the Manage phase to ensure you can more easily create overviews of your statistics, displaying all information correctly and improving the migration process to the next-generation architecture in the Create phase slightly. On top of that, we have improved the scalability of our new generation monitoring stack and the alerting structure. We will also release a new cloud template for our next-generation infrastructure to comply with technical requirements from our cloud provider.
	5	+**Hi there, eMagiz developers!** In the last few weeks, we have worked hard on planning the upcoming Q and finishing up features of the last Q. More on that later. On top of that we have several smaller items as a result of our hackathon efforts to present to you.
6	6
7		-== ** Mandatory Cloud Template Upgrade - Next-generation models ** ==
	7	+== **Announcement - Release Properties** ==
	8	+As of the next release (202) we will introduce a completely new way of handling properties for all our clients. In the upcoming weeks we will publish additional information on the process, what changes, and how you best manage your properties as of then within the documentation portal. Should you have any questions in advance please contact us at [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]].
8	8
9		-As can be seen on our [[status page>>https://status.emagiz.com/incidents/dbh6g9w3ks7q||target="blank"]], we will release a new cloud template for our next-generation models (both single and double lane) that will change a configuration in these templates to comply with technical and operational requirements from our cloud provider. The announcement of the status page itself holds more detail for those to whom it pertains.
	10	+== ** Deploy Architecture - Apply To Environment improvements ** ==
	11	+As of this release we will show you a list of all change that are about to be changed once you press "Apply to environment" in Deploy Architecture. This will ensure that it becomes clearer for users, especially those working together in teams, what will change when pressing this button.
10	10
11		-== **Feedback Items** ==
	13	+[[image:Main.Images.Release Blog.WebHome@201-release-blog--apply-to-environment-example.png]]
12	12
13		-//__Improved Validation when migrating to the next-generation architecture__//
14		-To improve the migration process to the next-generation architecture, we now show a list of all reported problems, allowing the user to resolve them before migrating to the next-generation architecture.
	15	+== ** Breadcrumb navigation in eMagiz ** ==
	16	+With this release we introduce the "breadcrumb" navigation in certain parts of eMagiz. This will mostly be noticed, and have impact, in the Create phase when you are checking out your transformation or system message on flow level. Apart from there the navigation is implemented consistently across the portal for a unified look and feel.
15	15
16		-{{info}}Note that when no problem is found, the migration process of that runtime will start automatically.{{/info}}
	18	+[[image:Main.Images.Release Blog.WebHome@201-release-blog--breadcrumb-navigation-example.png]]
17	17
18		-//__Improved HTTP Statistics__//
19		-To improve the filtering and refresh functionality we offer on this overview, we have made several changes in this release that will improve the behavior of this overview.
	20	+== **Feedback Items** ==
20	20
21		-//__"Topic Full" alert restriction changed__//
22		-With this release, we will change the "Topic Full" trigger point in our standard set of alerts once a model uses the Event Streaming functionality. Before, the alert would trigger on 80%, but as we saw, this is too early to make the alert useful in the context of our customers. As a result, the threshold has been raised to 95% to accommodate real-life situations better.
	22	+//__Improved layout of catalog page in Design__//
	23	+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 when having several operations.
23	23
24		-//__Improved performance Manage Dashboards__//
25		-We have improved the efficiency of retrieving the data shown in the Manage Dashboards for the next-generation architecture.
	25	+//__Improved layout of "Edit integration" pop-up for API Gateway integrations__//
	26	+As of now the full path of your backend system will be shown when opening the "Edit integration" pop-up on your API Gateway integration.
26	26
27		-//__Show values on the runtime level in Deploy Architecture__//
28		-We have improved the values shown on the runtime (i.e., container) level in Deploy Architecture so you can better assess whether the memory configuration is still suitable for your deployed solution.
	28	+//__Additional help texts on Design Architecture__//
	29	+We have improved the help texts in Design Archicture in relation to the Event Streaming topic storage overview.
29	29
30		-{{info}}To get to the values we use different calculation methods per type of runtime, as certain runtime types have various reasons for existence.
31		-* JMS - The number of queues in the active release.
32		-* Messaging Container - The number of messaging integrations in the active release.
33		-* Messaging Connector - The number of messaging integrations related to this system in the active release.
34		-* API Gateway Container - The number of operations in the active release.
35		-* Event Streaming Container - The number of event processors in the active release.
	31	+//__Improved Audit Trail on several places__//
	32	+In several places in the portal we have improved the audit trail to better specify who changed what at which point in time.
36	36
37		-There might be multi-tenant and multi-runtime situations that do not always get to the exact number; however, this is a great improvement compared to showing no values.{{/info}}
	34	+//__Removed the erroneous alert on message mapping when having a passthrough API__//
	35	+This release removes the erroneous alert people reported on "errors in message mapping" for a passthrough API.
38	38
39	39	== **Bug Fixes** ==
40	40
41		-//__Improved information Queue Statistics__//
42		-Given several constraints, it could happen that specific queues needed to be correctly displayed within the Manage phase on your model, making it tough to manage them. This has been resolved with this release.
	39	+//__Avoid clicking on other components while deleting another__//
	40	+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.
43	43
44		-//__Gain the ability again to configure certificates in Deploy Architecture again__//
45		-In restricting the configuration options on the certificate level in one of our latter releases, it became impossible for normal users to add and edit certificates within Deploy Architecture. To resolve this problem we have now released a fix to resolve this issue, giving people the ability again to add and edit certificates under Deploy Architecture.
	42	+//__Improved validation feedback in migrating to the next-generation architecture__//
	43	+We have improved several things with regards to the validation feedback when migrating to the next-generation architecture.
46	46
47		-//__Ensure that differing container configurations deploy the correct configuration__//
48		-When you run in a multi-runtime configuration and change the actual flows that need to run on container A vs. container B, it happened before that all flows were still being deployed on all runtimes. With this release, we will feed this information correctly to our infrastructure to ensure the correct and configured flows are deployed on the proper containers.
	45	+//__Make sure that user credentials can be viewed with view rights__//
	46	+This release makes sure that the user credentials in Deploy can be viewed with view rights and not only when having edit rights.
49	49
50		-//__Remove queurying options in Manage__//
51		-To avoid errors and loading problems when analyzing your statistics in Manage, we have removed the option to select a default time range spanning more than seven days. This is to guarantee the stability of the solution and to avoid users getting unnecessary errors.
	48	+//__Refresh behavior within the deployment plan is fixed__//
	49	+This release changes the refresh behavior within the deployment plan to show, once more, the "to be installed" flows before the user presses Execute.
52	52
53	53	== **Fancy Forum Answers** ==
54	54
55	55	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:
56	56
57		-* [[Getting files from subfolders (FTP)>>https://my.emagiz.com/p/question/172825635703568575||target="blank"]]
	55	+* [[Replacing Legacy eMagiz-Mendix Connector: Migration Plan>>https://my.emagiz.com/p/question/172825635703517317||target="blank"]]
	56	+* [[Unknown character(s) does not create error message.>>https://my.emagiz.com/p/question/172825635703517488||target="blank"]]
	57	+* [[Split gateway configuration for local GEN3 gateway>>https://my.emagiz.com/p/question/172825635703517580||target="blank"]]
58	58
59	59	== **Key takeaways** ==
60	60
61		-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:
	61	+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	62
63	63	* If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
64	64	* If you have feedback or ideas for us, talk to the Platypus
65		-* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
	65	+* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
66	66	* Clear your browser cache (Ctrl + Shift + Del)
67	67	* Check out the release notes [here]
68	68	* Start thinking about how the license tracker can aid your development
...	...	@@ -75,6 +75,6 @@
75	75	{{info}}
76	76	~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
77	77
78		-~*~* Indicates a next-generation-architecture only feature.
	78	+~*~* Indicates a GEN3-only feature.
79	79	{{/info}})))((({{toc/}}))){{/container}}
80	80	{{/container}}