Changes for page 222 - Flee Frustration

Summary

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

Details

Page properties

Title

...	...	@@ -1,1 +1,1 @@
1		-222 - Flee Frustration
	1	+204 - Found It

Author

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

Content

...	...	@@ -1,59 +1,49 @@
1	1	{{container}}
2		-{{container layoutStyle="columns"}}
3		-(((
	2	+{{container layoutStyle="columns"}}(((
4	4	[[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]]
5	5
6		-**Hi there, eMagiz developers!** This release, we have worked to allow cron trigggers for hours, days and months prepended by a 0. Moreover, changes in Design that will create or delete runtimes, or impact your model architecture, will trigger a warning before being put into effect in Design Architecture. We have also done several bug fixes, for example, users are not logged out from the portal anymore while deploying. Furthermore, users are now blocked from deploying at the same time on the same environment. Dive into our release blog to find out about the details and the rest of our bug fixes!
	5	+**Hi there, eMagiz developers!** We have processed additional feedback on the release properties in the last few weeks. On top of that, we have improved the error handling and manageability of our new generation monitoring stack.
7	7
8	8	== **Feedback Items** ==
9		-//__Cron triggers__//
10		-Cron triggers now allow for hours, days and months prepended by a 0, for example 05.
11	11
12		-[[image:Main.Images.Release Blog.WebHome@release-222-cron-triggers.png]]
	9	+//__Improved check on nested property placeholders__//
	10	+To avoid problems when using nested property placeholders in your configuration, we have added additional checks to identify these nested properties as missing if they are indeed missing.
13	13
14		-//__Design changes__//
15		-If a user makes changes in Design that will create or delete runtimes, or impact your model architecture, that user will be warned about this before it is put into effect in Design Architecture.
	12	+//__Removed outdated properties when deploying on the new generation architecture stack__//
	13	+We have removed two specific outdated properties from the configuration when deploying on the new generation architecture stack. The properties in question were necessary before connecting to a Kafka cluster but have become obsolete once you migrate.
16	16
17		-[[image:Main.Images.Release Blog.WebHome@release-222-affect-design-architecture.png]]
	15	+{{warning}}Should you still use the properties called "emagiz.runtime.name" and "emagiz.runtime.environment" **after** successfully migrating the flow in question to the next generation, please get in touch with us before deploying.{{/warning}}
18	18
	17	+//__Improved performance Manage Dashboards__//
	18	+We have improved the efficiency of retrieving the data shown in the Manage Dashboards for the next-generation architecture.
	19	+
19	19	== **Bug Fixes** ==
20		-//__Trigger activation__//
21		-Previously, when users were logged out from eMagiz during the execution of the deployment plan, it seemed that the portal reactived triggers, but this was not done. From now on, users are blocked from being logged out during deployment execution, so that triggers are re-enabled after the deployment plan has been executed.
22	22
23		-//__Multiple users deploying__//
24		-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.
	22	+//__Errors with long stack traces or long message histories will now also show in eMagiz__//
	23	+We have fixed a bug that could cause an error message to be lost between the flow and the Manage phase of eMagiz. This happened in situations where either the stack trace or the message history was very long. To ensure this new functionality is applied to your flows, create a new release and deploy it to your environment(s).
25	25
26		-[[image:Main.Images.Release Blog.WebHome@release-222-users-deploying.png]]
	25	+//__Moving runtimes from on-premise to the cloud will not result in a broken container anymore__//
	26	+We have fixed a bug that caused specific runtimes to deploy on-premises but later migrated to the cloud, not to start up. By fixing this bug, you have more flexibility in moving containers around when running in a hybrid configuration.
27	27
28		-//__Invalid memory configurations__//
29		-We have improved machine health calculations to prevent the creation of a machine with invalid memory configurations.
30		-
31		-//__Property value synchronization__//
32		-Property values displayed in the Flow Designer and property values of your active release are now synchronized correctly.
33		-
34		-//__JMS number__//
35		-The number on the JMS container correctly displays the amount of queues present in Design.
36		-
37		-[[image:Main.Images.Release Blog.WebHome@release-222-jms.png]]
38		-
39	39	== **Fancy Forum Answers** ==
40	40
41	41	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:
42	42
43		-* [[SunCertPathBuilderException using a Keystore>>https://my.emagiz.com/p/question/172825635703850115||target="blank"]]
44		-* [[Name of User in header>>https://my.emagiz.com/p/question/172825635703850290||target="blank"]]
	32	+* [[XSLT Extension Gateway with JSON message>>https://my.emagiz.com/p/question/172825635703543227||target="blank"]]
	33	+* [[eMagiz property migration>>https://my.emagiz.com/p/question/172825635703543395||target="blank"]]
45	45
46		-== **Key Takeaways** ==
	35	+== **Key takeaways** ==
47	47
48	48	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:
49	49
50	50	* If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
51	51	* If you have feedback or ideas for us, talk to the Platypus
52		-* 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.
53	53	* Clear your browser cache (Ctrl + Shift + Del)
54		-* Check out the release notes [[here>>doc:Main.Release Information.Portal.222 - Flee Frustration.WebHome||target="blank"]]
	43	+* Check out the release notes [here]
55	55	* Start thinking about how the license tracker can aid your development
56	56	* Start thinking about major, minor, and patch
	46	+* Upgrade to the latest build number
57	57	* Keep making great integrations
58	58
59	59	Let's stay in touch and till next time!
...	...	@@ -61,11 +61,6 @@
61	61	{{info}}
62	62	~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
63	63
64		-{{/info}}
65		-)))
66		-
67		-(((
68		-{{toc/}}
69		-)))
	54	+~*~* Indicates a next-generation-architecture only feature.
	55	+{{/info}})))((({{toc/}}))){{/container}}
70	70	{{/container}}
71		-{{/container}}