Changes for page 213 - Joyful Journeys

Summary

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

Details

Page properties

Title

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

Content

...	...	@@ -2,77 +2,70 @@
2	2	{{container layoutStyle="columns"}}(((
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.
	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.
6	6
7		-== **3rd generation runtime bolstering** ==
	7	+== **Release Properties** ==
	8	+As of this release, we will introduce a new way of handling properties for all our clients. This change intends to solidify the relationship between a release and a property value. Before, in the current generation architecture, timing of changing properties was crucial to avoid costly mistakes on Production. On top of that it was not always clear whether a property value was indeed updated as it was not linked to something that was deployed. These considerations let us to change the property management behavior not only on our next-generation architecture but also on our current generation architecture. Having said that, there are several key changes compared to the current way of managing your properties. Most notably among these are:
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.
	10	+* The current properties tab in Deploy will disappear. The new overview of the properties (and their values) can be found under the "Create phase release" in Deploy -> Releases
	11	+* Property placeholders (i.e. the names of properties as given in Create) are now automatically created for you. This to avoid mistakes when filling them in.
	12	+* When adding or editing a property you can *now* select multiple runtimes for which the property applies. This is mainly beneficial for those running in a double lane setup or having a distributed landscape of containers.
	13	+* A, for most, new concept of a "property release" is introduced. With the help of this functionality you can easily change a property on Production without having to create a completely new release in Test and promote it to the Production environment.
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.
	15	+{{info}}For more information please check out the following microlearnings:
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	+* [[Property Management>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.crashcourse-platform-deploy-property-management-new.WebHome||target="blank"]]
	18	+* [[Actualize properties - current generation architecture>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.crashcourse-platform-deploy-actualize-properties-new.WebHome||target="blank"]]
	19	+* [[Actualize properties - next generation architecture>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.crashcourse-platform-deploy-actualize-properties-gen3-new.WebHome||target="blank"]]
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.
	21	+Should you have any questions in advance, please get in touch with us at [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]].
	22	+{{/info}}
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.
	24	+== ** Manage - Next generation graphs improvements ** ==
	25	+As of this release, we will create a condensed view of your metrics when zooming out in the Manage phase graphs. This will significantly improve the performance of the manage graphs as we retrieve and show less fine-grained information when zooming out.
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.
	27	+[[image:Main.Images.Release Blog.WebHome@202-release-blog--manage-graphs-zoomed-out.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.
	29	+== **Feedback Items** ==
28	28
29		-== **Exportable Release Audit** ~* ==
	31	+//__Improved editability when testing in eMagiz wihout Edit rights in Create__//
	32	+Without having edit rights in the Create phase you could already do a lot on the level of flow tests in eMagiz. However, there were some oversights we missed during the implementation. These have been fixed allowing those without edit rights to now also change the name and description of the test case.
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	+//__Improved auditability on Deploy Architecture__//
	35	+To improve the audtiability on Deploy Architecture we now also log when someone with Admin rights changes specific functions on this level (i.e. Fixed IP).
32	32
33		-[[image:Main.Images.Release Blog.WebHome@187-release-blog--flow-version-restore.png]]
	37	+//__Test your own exported work__//
	38	+We have now made it possible to test your own exported work to the Store before it gets approved. This will increase the quality of store items we have, and our partners, have on offer within the store.
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	+{{info}}In case the concept of the store is new for you please check out this [[Fundamental>>doc:Main.eMagiz Academy.Fundamentals.fundamental-emagiz-store.WebHome||target="blank"]]{{/info}}
40	40
41		-== **Feedback items ** ==
	42	+//__Improved Audit Trail on several places__//
	43	+In several places in the portal, we have improved the audit trail to specify better who changed what at which point in time.
42	42
43		-We have also solved other feedback items besides the flow designer's critical updates.
	45	+//__Removed the erroneous alert on message mapping when having a passthrough API__//
	46	+This release removes the erroneous alert people reported on "errors in message mapping" for a passthrough API.
44	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.
	48	+== **Bug Fixes** ==
47	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	+//__Avoid clicking on other components while deleting another__//
	51	+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.
50	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	+//__Improved validation feedback in migrating to the next-generation architecture__//
	54	+We have improved the validation feedback when migrating to the next-generation architecture.
53	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
	56	+//__Make sure that user credentials can be viewed with view rights__//
	57	+This release makes sure that the user credentials in Deploy can be considered with view rights and not only when having edit rights.
68	68
	59	+//__Refresh behavior within the deployment plan is fixed__//
	60	+This release changes the refresh behavior within the deployment plan to show, once more, the "to be installed" flows before the user presses Execute.
	61	+
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"]]
	66	+* [[Replacing Legacy eMagiz-Mendix Connector: Migration Plan>>https://my.emagiz.com/p/question/172825635703517317||target="blank"]]
	67	+* [[Unknown character(s) does not create error message.>>https://my.emagiz.com/p/question/172825635703517488||target="blank"]]
	68	+* [[Split gateway configuration for local GEN3 gateway>>https://my.emagiz.com/p/question/172825635703517580||target="blank"]]
76	76
77	77	== **Key takeaways** ==
78	78