Changes for page 206 - Situational Deployment

Summary

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

Details

Page properties

Title

...	...	@@ -1,1 +1,1 @@
1		-203 - Fast Paced
	1	+188 - Close Encounters

Content

...	...	@@ -2,32 +2,77 @@
2	2	{{container layoutStyle="columns"}}(((
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 processed some of the early feedback on the release properties. On top of that we have improved the scalability of our complete solution and solved various smaller feedback items.
	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	6
7		-== **Release Properties - Early Feedback** ==
8		-The release property functionality was well received by the community. However, there was still room for improvement based on some of the early feedback we received from the community. Some of these early feedback items have been addressed in this release. As a result we have updated the layout of the edit screen of a property and have updated our checks on nested properties to avoid missing properties.
	7	+== **3rd generation runtime bolstering** ==
9	9
10		-== **Feedback Items** ==
	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.
11	11
12		-//__"All entries" are now cleaned up as part of the migration__//
13		-To avoid problems when removing integrations after the migration towards the next-generation architecture we now clean-up the "all-entries" as part of the migration towards the next-generation architecture.
	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	14
15		-//__Trigger ID added to our alerting on the next-generation architecture__//
16		-We have added a unique trigger ID to each alert configuration to make the interpretation for our support desk much easier and better manageable.
	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	17
18		-== **Bug Fixes** ==
	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	19
20		-//__Ensure no flow can be in a release twice__//
21		-We have fixed a bug that could cause one flow to end up in the same release with two different flow versions. As this will break your solution on various occasions we fixed this.
	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.
22	22
23		-//__Ensure no flow can be in a release twice__//
24		-We have fixed a bug that could cause one flow to end up in the same release with two different flow versions. As this will break your solution on various occasions we fixed this.
	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.
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	+
	29	+== **Exportable Release Audit** ~* ==
	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.
	32	+
	33	+[[image:Main.Images.Release Blog.WebHome@187-release-blog--flow-version-restore.png]]
	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	+
26	26	== **Fancy Forum Answers** ==
27	27
28	28	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:
29	29
30		-* [[Issue with mail server dropping messages>>https://my.emagiz.com/p/question/172825635703530232||target="blank"]]
	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"]]
31	31
32	32	== **Key takeaways** ==
33	33
...	...	@@ -48,6 +48,6 @@
48	48	{{info}}
49	49	~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
50	50
51		-~*~* Indicates a next-generation-architecture only feature.
	96	+~*~* Indicates a GEN3-only feature.
52	52	{{/info}})))((({{toc/}}))){{/container}}
53	53	{{/container}}