Changes for page 222 - Flee Frustration

Summary

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

Details

Page properties

Title

...	...	@@ -1,1 +1,1 @@
1		-201 - Be Informed
	1	+222 - Flee Frustration

Author

...	...	@@ -1,1 +1,1 @@
1		-XWiki.ebakker
	1	+XWiki.CarlijnKokkeler

Content

...	...	@@ -1,73 +1,44 @@
1	1	{{container}}
2		-{{container layoutStyle="columns"}}(((
	2	+{{container layoutStyle="columns"}}
	3	+(((
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 worked hard on planning the upcoming Q and finishing up features of the previous 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	+**Hi there, eMagiz developers!**
6	6
7		-== **Announcement - Release Properties** ==
8		-As of the next release (202), we will introduce a 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 get in touch with us at [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]].
9		-
10		-== ** Deploy Architecture - Apply To Environment improvements ** ==
11		-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.
12		-
13		-[[image:Main.Images.Release Blog.WebHome@201-release-blog--apply-to-environment-example.png]]
14		-
15		-== ** Breadcrumb navigation in eMagiz ** ==
16		-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.
17		-
18		-[[image:Main.Images.Release Blog.WebHome@201-release-blog--breadcrumb-navigation-example.png]]
19		-
20	20	== **Feedback Items** ==
	9	+//__Trigger activation__//
	10	+Cron triggers now allow for hours, days and months prepended by a 0, for example 05, which was not allowed before.
21	21
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 of several operations.
	12	+[[image:Main.Images.Release Blog.WebHome@release-222-cron-triggers.png]]
24	24
25		-//__Improved layout of "Edit integration" pop-up for API Gateway integrations__//
26		-Currently, the full path of your backend system will be shown when opening the "Edit integration" pop-up on your API Gateway integration.
27		-
28		-//__Additional help texts on Design Architecture__//
29		-We have improved the help texts in Design Architecture concerning the Event Streaming topic storage overview.
30		-
31		-//__Improved Audit Trail on several places__//
32		-In several places in the portal, we have improved the audit trail to specify better who changed what at which point in time.
33		-
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.
36		-
37	37	== **Bug Fixes** ==
	15	+//__Trigger activation__//
	16	+Previously, when you were logged out from eMagiz during the execution of the deployment plan, it seemed that the portal reactived your triggers, but this was not done. From now on, the deployer is blocked from logging out during the deployment execution, so that the triggers are re-enabled after the deployment plan has been executed.
38	38
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.
	18	+//__Trigger activation__//
	19	+Users are blocked from deploying at the same time on the same environment on the [[current runtime>>doc:Main.eMagiz Academy.Fundamentals.fundamental-runtime-generation3||target="blank"]] architecture.
41	41
42		-//__Improved validation feedback in migrating to the next-generation architecture__//
43		-We have improved the validation feedback when migrating to the next-generation architecture.
	21	+[[image:Main.Images.Release Blog.WebHome@release-222-users-deploying.png]]
44	44
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 considered with view rights and not only when having edit rights.
47		-
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.
50		-
51	51	== **Fancy Forum Answers** ==
52	52
53	53	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:
54	54
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"]]
	27	+* [[OAuth 2.0, 403 Forbidden>>https://my.emagiz.com/p/question/172825635703837388||target="blank"]]
	28	+* [[HTTP request without reply>>https://my.emagiz.com/p/question/172825635703837492||target="blank"]]
	29	+* [[All-entry API gateway is not starting>>https://my.emagiz.com/p/question/172825635703837607||target="blank"]]
58	58
59		-== **Key takeaways** ==
	31	+== **Key Takeaways** ==
60	60
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:
	33	+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:
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.
	37	+* 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		-* Check out the release notes [here]
	39	+* Check out the release notes [[here>>doc:Main.Release Information.Portal.221 - Swift Shift.WebHome||target="blank"]]
68	68	* Start thinking about how the license tracker can aid your development
69	69	* Start thinking about major, minor, and patch
70		-* Upgrade to the latest build number
71	71	* Keep making great integrations
72	72
73	73	Let's stay in touch and till next time!
...	...	@@ -75,6 +75,11 @@
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 GEN3-only feature.
79		-{{/info}})))((({{toc/}}))){{/container}}
	49	+{{/info}}
	50	+)))
	51	+
	52	+(((
	53	+{{toc/}}
	54	+)))
80	80	{{/container}}
	56	+{{/container}}