Changes for page 224 - Summer Sonata

Summary

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

Details

Page properties

Title

...	...	@@ -1,1 +1,1 @@
1		-212 - Failover Fiesta
	1	+222 - Flee Frustration

Content

...	...	@@ -3,36 +3,46 @@
3	3	(((
4	4	[[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]]
5	5
6		-**Hi there, eMagiz developers!** This release contains single and double lane cloud template updates, both non-service affecting. Moreover, work has been done to better support a failover setup. Lastly, some bug fixes were done regarding the message merging tool and catalog topic defintions.
	6	+**Hi there, eMagiz developers!**
7	7
8		-== **Cloud Template R20 - Double Lane** ==
	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.
9	9
10		-This release introduces a new non-service affecting cloud template for all our customers running in a double-lane setup. This cloud template introduces improved auto-healing. The complete release notes on the cloud template can be found [[here>>doc:Main.Release Information.Cloud Templates.R20 - Double lane.WebHome||target="blank"]].
	12	+[[image:Main.Images.Release Blog.WebHome@release-222-cron-triggers.png]]
11	11
12		-== **Cloud Template R27 - Single Lane** ==
	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.
13	13
14		-This release introduces a new non-service affecting cloud template for all our customers running in a single-lane setup. This cloud template introduces improved auto-healing. The complete release notes on the cloud template can be found [[here>>doc:Main.Release Information.Cloud Templates.R27 - Single lane.WebHome||target="blank"]].
	17	+[[image:Main.Images.Release Blog.WebHome@release-222-affect-design-architecture.png]]
15	15
16		-== **Feedback Items** ==
	19	+== **Bug Fixes** ==
	20	+//__Trigger activation__//
	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.
17	17
18		-//__Failover setup__//
19		-New components have been created to support a failover setup. Moreover, two new deployment step types are introduced to incorporate failover actions during deployment. More information can be found [[here>>https://docs.emagiz.com/bin/view/Main/Release%20Information/Runtime%20Images/V2.1.0/||target="blank"]].
	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.
20	20
21		-== **Bug Fixes** ==
	26	+[[image:Main.Images.Release Blog.WebHome@release-222-users-deploying.png]]
22	22
23		-//__Message merging tool__//
24		-We have improved our merging functionality within our Store offering to avoid unexpected results after merging. These unexpected results would lead to a broken Design phase on the data model level. If you have encountered this issue, you can manually clean your CDM message by removing the entities from the tree view and the canvas and correcting the CDM itself accordingly.
	28	+//__Invalid memory configurations__//
	29	+We have improved machine health calculations to prevent the creation of a machine with invalid memory configurations.
25	25
26		-//__Catalog topic definitions__//
27		-Before, an error would occur in the Catalog page when generating an example JSON message of a topic definition that has nested elements. This issue is now fixed and generating a sample JSON message for such topic definition is possible.
	31	+//__Invalid memory configurations__//
	32	+Property values displayed in the Flow Designer and property values of your active release are now synchronized correctly.
28	28
	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	+
29	29	== **Fancy Forum Answers** ==
30	30
31	31	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:
32	32
33		-* [[What is the eMagiz control tower?>>https://my.emagiz.com/p/question/172825635703696612||target="blank"]]
34		-* [[Deleting connector without flows gives error>>https://my.emagiz.com/p/question/172825635703696657]]
35		-* [[How to use a flowtest with path properties>>https://my.emagiz.com/p/question/172825635703696835||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"]]
36	36
37	37	== **Key Takeaways** ==
38	38
...	...	@@ -42,7 +42,7 @@
42	42	* If you have feedback or ideas for us, talk to the Platypus
43	43	* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
44	44	* Clear your browser cache (Ctrl + Shift + Del)
45		-* Check out the release notes [here]
	55	+* Check out the release notes [[here>>doc:Main.Release Information.Portal.221 - Swift Shift.WebHome||target="blank"]]
46	46	* Start thinking about how the license tracker can aid your development
47	47	* Start thinking about major, minor, and patch
48	48	* Keep making great integrations