Changes for page 206 - Situational Deployment

Summary

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

Details

Page properties

Title

...	...	@@ -1,1 +1,1 @@
1		-202 - New Equilibrium
	1	+188 - Close Encounters

Content

...	...	@@ -2,68 +2,76 @@
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 crossed our t's and dotted our i's on the release properties functionality that will impact the day to day life of every user working within the platform. The focus of the release blog will consequently also be on this subject. On top of that we have several additional smaller feedback item coming from our hackathon efforts that are now released to you.
	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** ==
8		-As of this release, we will introduce a new way of handling properties for all our clients. There are several key changes compared to the current way of managing your properties.
	7	+== **3rd generation runtime bolstering** ==
9	9
10		-{{info}}For more information please check out the following microlearnings:
	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		-* [[microlearning>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.crashcourse-platform-deploy-property-management-new.WebHome||target="blank"]]
13		-* [[microlearning>>doc:Main.eMagiz Academy.Microlearnings.Novice.eMagiz Store.novice-emagiz-store-merge-store-data-model.WebHome||target="blank"]]
14		-* [[microlearning>>doc:Main.eMagiz Academy.Microlearnings.Novice.eMagiz Store.novice-emagiz-store-merge-store-data-model.WebHome||target="blank"]]
	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.
15	15
16		-Should you have any questions in advance, please get in touch with us at [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]].
17		-{{/info}}
	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.
18	18
19		-== ** Deploy Architecture - Apply To Environment improvements ** ==
20		-As of this release, we will show you a list of all changes about to be changed once you press "Apply to the environment" in Deploy Architecture. This will make it clearer for users, especially those working in teams, what will change when pressing this button.
	17	+//__Autogenerated exits can be deployed at once__//
	18	+This release has fixed a bug that prevented you from deploying an exit flow correctly.
21	21
22		-[[image:Main.Images.Release Blog.WebHome@201-release-blog--apply-to-environment-example.png]]
	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	23
24		-== ** Breadcrumb navigation in eMagiz ** ==
25		-This release introduces the "breadcrumb" navigation in certain parts of eMagiz. This will mostly be noticed and impact the Create phase when you check out your transformation or system message on the flow level. Apart from there, the navigation is implemented consistently across the portal for a unified look and feel.
	23	+//__Failing runtimes won't be restarted indefinitely anymore__//
	24	+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.
26	26
27		-[[image:Main.Images.Release Blog.WebHome@201-release-blog--breadcrumb-navigation-example.png]]
	26	+== **Exportable Release Audit** ~* ==
28	28
29		-== **Feedback Items** ==
	28	+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.
30	30
31		-//__Improved layout of catalog page in Design__//
32		-We have improved the layout of the API Catalog overview in Design for our API Gateway users. Among others, we have introduced a scrollbar to get a better overview of several operations.
	30	+[[image:Main.Images.Release Blog.WebHome@188-release-blog--exportable-release-audit.png]]
33	33
34		-//__Improved layout of "Edit integration" pop-up for API Gateway integrations__//
35		-Currently, the full path of your backend system will be shown when opening the "Edit integration" pop-up on your API Gateway integration.
	32	+{{warning}}Note that the following restrictions apply when exporting an audit document:
	33	+ * Works **only** for releases that are promoted and made active on **Production**
	34	+ * You will **only** see changes made during the **current** calendar year
	35	+ * On the first of April all objects of the **last** calendar year will be **removed**.
	36	+ ** As a consequence you cannot download this information anymore **after** the first of April{{/warning}}
36	36
37		-//__Additional help texts on Design Architecture__//
38		-We have improved the help texts in Design Architecture concerning the Event Streaming topic storage overview.
	38	+== **Feedback items ** ==
39	39
40		-//__Improved Audit Trail on several places__//
41		-In several places in the portal, we have improved the audit trail to specify better who changed what at which point in time.
	40	+We have also solved other feedback items besides the flow designer's critical updates.
42	42
43		-//__Removed the erroneous alert on message mapping when having a passthrough API__//
44		-This release removes the erroneous alert people reported on "errors in message mapping" for a passthrough API.
	42	+//__Improved naming convention on Store related pages__//
	43	+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.
45	45
46		-== **Bug Fixes** ==
	45	+//__Press "Enter" to search on multiple pages__//
	46	+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.
47	47
48		-//__Avoid clicking on other components while deleting another__//
49		-To avoid unexpected behavior, we now ensure that nothing can be selected once you see the "deletion" pop-up when you want to remove something in the flow designer.
	48	+* Deploy → Deployment Plan
	49	+* Deploy → Properties → History
	50	+* Deploy → User Management → Roles
	51	+* Manage → Error Messages → Error Messages
	52	+* Manage → Error Messages → Flows with Error Messages
	53	+* Manage → Error Messages → Exceptions of Error Messages
	54	+* Manage → Log Entries
	55	+* Manage → Alerts
	56	+* Manage → Triggers
	57	+* Manage → Tags – Cant find (only Gen2)
	58	+* Manage → Notifications
	59	+* Manage → Notification Settings
	60	+* Manage → Data Usage → History
	61	+* Manage → Code mappings → All tabs
50	50
51		-//__Improved validation feedback in migrating to the next-generation architecture__//
52		-We have improved the validation feedback when migrating to the next-generation architecture.
	63	+== **Bug fixes ** ==
53	53
54		-//__Make sure that user credentials can be viewed with view rights__//
55		-This release makes sure that the user credentials in Deploy can be considered with view rights and not only when having edit rights.
	65	+//__Loading problems of Deployment plan execution overview__//
	66	+We have fixed a problem that could cause issues when trying to show the deployment plan execution overview after pressing the Deploy button in Deploy -> Releases.
56	56
57		-//__Refresh behavior within the deployment plan is fixed__//
58		-This release changes the refresh behavior within the deployment plan to show, once more, the "to be installed" flows before the user presses Execute.
59		-
60	60	== **Fancy Forum Answers** ==
61	61
62	62	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:
63	63
64		-* [[Replacing Legacy eMagiz-Mendix Connector: Migration Plan>>https://my.emagiz.com/p/question/172825635703517317||target="blank"]]
65		-* [[Unknown character(s) does not create error message.>>https://my.emagiz.com/p/question/172825635703517488||target="blank"]]
66		-* [[Split gateway configuration for local GEN3 gateway>>https://my.emagiz.com/p/question/172825635703517580||target="blank"]]
	72	+* [[Synchronous file pick-up>>https://my.emagiz.com/p/question/172825635703197660||target="blank"]]
	73	+* [[Receiving e-mail via IMAP or POP3 - Set up>>https://my.emagiz.com/p/question/172825635703197881||target="blank"]]
	74	+* [[Best way of Receiving and Sending Mail>>https://my.emagiz.com/p/question/172825635703210149||target="blank"]]
67	67
68	68	== **Key takeaways** ==
69	69