Changes for page 213 - Joyful Journeys

Summary

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

Details

Page properties

Title

...	...	@@ -1,1 +1,1 @@
1		-188 - Close Encounters
	1	+209 - Deployment Delights

Author

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

Content

...	...	@@ -1,81 +1,54 @@
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!** We have...
6	6
7		-== **3rd generation runtime bolstering** ==
	8	+== **Release Maintenance** ==
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	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.
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.
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	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.
	14	+== **Feedback Items** ==
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.
	16	+//__Harbor port change__//
	17	+The port for which you need to register has been changed ...?
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.
	19	+//__Container version overview__//
	20	+In Deploy > Releases, it is now possible to see the container versions in the release details. This can be viewed by clicking the three dots in the Create phase section.
28	28
29		-== **Exportable Release Audit** ~* ==
	22	+[[image:Main.Images.Release Blog.WebHome@release-blog-209-deployment-delights-container-overview.png]]
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.
	24	+//__Unchanged containers__//
	25	+When deploying a new release, containers that have no changes between the deployed release and the new release will not be deployed and restarted.
32	32
33		-[[image:Main.Images.Release Blog.WebHome@188-release-blog--exportable-release-audit.png]]
	27	+//__Rebuilding of images__//
	28	+Changing the list of flows that should run on a container will now trigger the rebuilding of images.
34	34
35		-{{warning}}Note that the following restrictions apply when exporting an audit document:
36		- * Works **only** for releases that are promoted and made active on Production
37		- * You will **only** see changes made during the **current** calendar year{{/warning}}
38	38
39		-== **Feedback items ** ==
	31	+== **Bug Fixes** ==
40	40
41		-We have also solved other feedback items besides the flow designer's critical updates.
	33	+//__Runtime metrics processing__//
	34	+The collection and publishing of runtime metrics is no longer synchronized across containers, which improves their processing.
42	42
43		-//__Improved naming convention on Store related pages__//
44		-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.
	36	+//__Deployment plan__//
	37	+We solved a bug where a deployment step in the deployment plan could randomly get stuck.
45	45
46		-//__Press "Enter" to search on multiple pages__//
47		-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.
48		-
49		-* Deploy → Deployment Plan
50		-* Deploy → Properties → History
51		-* Deploy → User Management → Roles
52		-* Manage → Error Messages → Error Messages
53		-* Manage → Error Messages → Flows with Error Messages
54		-* Manage → Error Messages → Exceptions of Error Messages
55		-* Manage → Log Entries
56		-* Manage → Alerts
57		-* Manage → Triggers
58		-* Manage → Tags – Cant find (only Gen2)
59		-* Manage → Notifications
60		-* Manage → Notification Settings
61		-* Manage → Data Usage → History
62		-* Manage → Code mappings → All tabs
63		-
64	64	== **Fancy Forum Answers** ==
65	65
66	66	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:
67	67
68		-* [[Synchronous file pick-up>>https://my.emagiz.com/p/question/172825635703197660||target="blank"]]
69		-* [[Receiving e-mail via IMAP or POP3 - Set up>>https://my.emagiz.com/p/question/172825635703197881||target="blank"]]
70		-* [[Best way of Receiving and Sending Mail>>https://my.emagiz.com/p/question/172825635703210149||target="blank"]]
	43	+* [[JSONPath in SpEL expressions>>https://my.emagiz.com/p/question/172825635703415034||target="blank"]]
71	71
72	72	== **Key takeaways** ==
73	73
74		-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:
	47	+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:
75	75
76	76	* If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
77	77	* If you have feedback or ideas for us, talk to the Platypus
78		-* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
	51	+* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
79	79	* Clear your browser cache (Ctrl + Shift + Del)
80	80	* Check out the release notes [here]
81	81	* Start thinking about how the license tracker can aid your development
...	...	@@ -88,6 +88,12 @@
88	88	{{info}}
89	89	~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
90	90
91		-~*~* Indicates a GEN3-only feature.
92		-{{/info}})))((({{toc/}}))){{/container}}
	64	+~*~* Indicates a next-generation-architecture only feature.
	65	+{{/info}}
	66	+)))
	67	+
	68	+(((
	69	+{{toc/}}
	70	+)))
93	93	{{/container}}
	72	+{{/container}}