Changes for page 224 - Summer Sonata

Summary

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

Details

Page properties

Content

...	...	@@ -3,9 +3,14 @@
3	3	(((
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!
	6	+**Hi there, eMagiz developers!**
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, which was not allowed before.
	11	+
	12	+[[image:Main.Images.Release Blog.WebHome@release-222-cron-triggers.png]]
	13	+
9	9	//__Design changes__//
10	10	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.
11	11
...	...	@@ -12,13 +12,8 @@
12	12	[[image:Main.Images.Release Blog.WebHome@release-222-affect-design-architecture.png]]
13	13
14	14	== **Bug Fixes** ==
15		-//__Cron triggers__//
16		-Cron triggers now allow for hours, days and months prepended by a 0, for example 05.
17		-
18		-[[image:Main.Images.Release Blog.WebHome@release-222-cron-triggers.png]]
19		-
20	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.
	21	+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.
22	22
23	23	//__Multiple users deploying__//
24	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.
...	...	@@ -28,7 +28,7 @@
28	28	//__Invalid memory configurations__//
29	29	We have improved machine health calculations to prevent the creation of a machine with invalid memory configurations.
30	30
31		-//__Property value synchronization__//
	31	+//__Invalid memory configurations__//
32	32	Property values displayed in the Flow Designer and property values of your active release are now synchronized correctly.
33	33
34	34	//__JMS number__//
...	...	@@ -40,8 +40,9 @@
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"]]
	43	+* [[OAuth 2.0, 403 Forbidden>>https://my.emagiz.com/p/question/172825635703837388||target="blank"]]
	44	+* [[HTTP request without reply>>https://my.emagiz.com/p/question/172825635703837492||target="blank"]]
	45	+* [[All-entry API gateway is not starting>>https://my.emagiz.com/p/question/172825635703837607||target="blank"]]
45	45
46	46	== **Key Takeaways** ==
47	47
...	...	@@ -51,7 +51,7 @@
51	51	* If you have feedback or ideas for us, talk to the Platypus
52	52	* 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"]]
	55	+* Check out the release notes [[here>>doc:Main.Release Information.Portal.221 - Swift Shift.WebHome||target="blank"]]
55	55	* Start thinking about how the license tracker can aid your development
56	56	* Start thinking about major, minor, and patch
57	57	* Keep making great integrations