Changes for page 222 - Flee Frustration

Summary

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

Details

Page properties

Title

...	...	@@ -1,1 +1,1 @@
1		-188 - Close Encounters
	1	+222 - Flee Frustration

Author

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

Content

...	...	@@ -1,91 +1,59 @@
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!** This release is characterized mainly by our efforts to bolster our 3rd generation runtime and all its interactions. Furthermore, some minor fixes and beta features will be released to the community.
	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 read about the details and the rest of our bug fixes!
6	6
7		-== **3rd generation runtime bolstering** ==
	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.
8	8
9		-This release will introduce various improvements for our 3rd generation runtime. Below you will find the most noteworthy enhancements we made to the 3rd generation runtime and its interaction with the portal.
	12	+[[image:Main.Images.Release Blog.WebHome@release-222-cron-triggers.png]]
10	10
11		-//__Migration of JMS backup configuration improved__//
12		-With this release, the configuration of the JMS backup configuration is improved to prevent potential connectivity issues after migrating to the 3rd generation runtime.
	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		-//__Prechecks on Upgrade option made available for 3rd generation runtime__//
15		-As with the current runtime architecture, you can now also execute the prechecks before automatically upgrading to the latest cloud template on the 3rd generation runtime architecture.
	17	+[[image:Main.Images.Release Blog.WebHome@release-222-affect-design-architecture.png]]
16	16
17		-//__Autogenerated exits can be deployed at once__//
18		-This release has fixed a bug that prevented you from deploying an exit flow correctly.
	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.
19	19
20		-//__Code mapping functionality available on 3rd generation runtime__//
21		-As of this release, code mapping functionality is also available for the 3rd generation runtime. This removes the restriction on migrating to the new 3rd generation runtime for our clients that use the code mapping functionality.
	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	22
23		-//__Improved the performance when activating a release__//
24		-With this release, the performance of activating a release has improved considerably. This means less waiting time when activating a release.
	26	+[[image:Main.Images.Release Blog.WebHome@release-222-users-deploying.png]]
25	25
26		-//__Failing runtimes won't be restarted indefinitely anymore__//
27		-We have put a cap on this behavior to prevent your logs from exploding due to a failing runtime being restarted indefinitely. As of this release, five attempts will be made to restart a failing runtime. If the runtime can not start correctly after these attempts, the runtime will be stopped.
	28	+//__Invalid memory configurations__//
	29	+We have improved machine health calculations to prevent the creation of a machine with invalid memory configurations.
28	28
29		-== **Exportable Release Audit** ~* ==
	31	+//__Property value synchronization__//
	32	+Property values displayed in the Flow Designer and property values of your active release are now synchronized correctly.
30	30
31		-On top of that, we will also launch a new Beta feature to the community that allows you to export an audit document of your (Production) release.
	34	+//__JMS number__//
	35	+The number on the JMS container correctly displays the amount of queues present in Design.
32	32
33		-[[image:Main.Images.Release Blog.WebHome@187-release-blog--flow-version-restore.png]]
	37	+[[image:Main.Images.Release Blog.WebHome@release-222-jms.png]]
34	34
35		-{{warning}}Note that the following restrictions apply when exporting an audit document:
36		- * Changes made on definition and transformation level are **not** restored
37		- * You will **not** be able to restore to any flow version that was created before October 17th, 2022
38		- * You will **not** be able to restore your flow to the original version created by eMagiz. You can use the reset function if you want this state back
39		- * Your restored flow version will **not** be automatically committed to Deploy{{/warning}}
40		-
41		-== **Feedback items ** ==
42		-
43		-We have also solved other feedback items besides the flow designer's critical updates.
44		-
45		-//__Data Sink Refactor__//
46		-We have made some infrastructural changes to how data sink messages are stored and can be retrieved from the portal. Should there be changes needed on your end, we will contact you separately.
47		-
48		-//__Improved naming convention on Store related pages__//
49		-We have improved various display names to ensure that it is clear from the naming that store content can be implemented in all integration patterns.
50		-
51		-//__Press "Enter" to search on multiple pages__//
52		-In our Daemon Switch release, we added functionality that allowed you to press **Enter** to search on the property overview page. This release has added this functionality to many more pages across the portal. The complete list is as follows.
53		-
54		-* Deploy → Deployment Plan
55		-* Deploy → Properties → History
56		-* Deploy → User Management → Roles
57		-* Manage → Error Messages → Error Messages
58		-* Manage → Error Messages → Flows with Error Messages
59		-* Manage → Error Messages → Exceptions of Error Messages
60		-* Manage → Log Entries
61		-* Manage → Alerts
62		-* Manage → Triggers
63		-* Manage → Tags – Cant find (only Gen2)
64		-* Manage → Notifications
65		-* Manage → Notification Settings
66		-* Manage → Data Usage → History
67		-* Manage → Code mappings → All tabs
68		-
69	69	== **Fancy Forum Answers** ==
70	70
71	71	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:
72	72
73		-* [[Synchronous file pick-up>>https://my.emagiz.com/p/question/172825635703197660||target="blank"]]
74		-* [[Receiving e-mail via IMAP or POP3 - Set up>>https://my.emagiz.com/p/question/172825635703197881||target="blank"]]
75		-* [[Best way of Receiving and Sending Mail>>https://my.emagiz.com/p/question/172825635703210149||target="blank"]]
	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"]]
76	76
77		-== **Key takeaways** ==
	46	+== **Key Takeaways** ==
78	78
79		-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:
	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:
80	80
81	81	* If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
82	82	* If you have feedback or ideas for us, talk to the Platypus
83		-* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
	52	+* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
84	84	* Clear your browser cache (Ctrl + Shift + Del)
85		-* Check out the release notes [here]
	54	+* Check out the release notes [[here>>doc:Main.Release Information.Portal.221 - Swift Shift.WebHome||target="blank"]]
86	86	* Start thinking about how the license tracker can aid your development
87	87	* Start thinking about major, minor, and patch
88		-* Upgrade to the latest build number
89	89	* Keep making great integrations
90	90
91	91	Let's stay in touch and till next time!
...	...	@@ -93,6 +93,11 @@
93	93	{{info}}
94	94	~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
95	95
96		-~*~* Indicates a GEN3-only feature.
97		-{{/info}})))((({{toc/}}))){{/container}}
	64	+{{/info}}
	65	+)))
	66	+
	67	+(((
	68	+{{toc/}}
	69	+)))
98	98	{{/container}}
	71	+{{/container}}