Changes for page 213 - Joyful Journeys

Summary

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

Details

Page properties

Title

...	...	@@ -1,1 +1,1 @@
1		-213 - Joyful Journeys
	1	+209 - Max Verstappen

Content

...	...	@@ -3,80 +3,69 @@
3	3	(((
4	4	[[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]]
5	5
6		-**Hi there, eMagiz developers!** In this release, several improvements for pop-ups have been made so that more user friendly messages are shown that reflect actual behaviour. Moreover, formatting and alignment improvements have been made to improve the user journey. Lastly, we have worked on some more feedback items and several more bug fixes have been done.
	6	+**Hi there, eMagiz developers!** We have improved the performance of our deployment plan, it should be finished much quicker now. Next to this, we have released new Docker Single Lane and Docker Double Lane cloud templates. Moreover, several feedback items have been processed and some bug fixes have been made. Lastly, as of this release, the next generation architecture will be our default.
7	7
8		-== **Pop-up Improvements** ==
	8	+{{warning}}
	9	+Please be aware that for this release, because of the duration of the deployment, we advise you to check your TEST and ACCP cloud slots status, since you might need to start them manually in case your model is using the automatic wake up functionality. For following releases we will set the automatic wake up time to 6:00 AM UTC instead of 5:00 AM UTC.
	10	+{{/warning}}
9	9
10		-//__Property releases__//
11		-When a new property release is created, this property release can now not only be viewed but also release properties can be deleted.
	12	+== **Quicker Deployment Plan Execution** ==
12	12
13		-[[image:Main.Images.Release Blog.WebHome@release-blog-213-joyful-journeys-property-release.png]]
	14	+We sped up the process of preparing runtime images in executing the deployment plan. The step in the deployment plan concerning the preparation of runtime images will now be executed more quickly and reliably. Moreover, we fixed an issue of the release preparation step taking longer than necessary which is caused by the machine deployment steps to be executed when they could have been skipped. So, the deployment plan will be finished much quicker now!
14	14
15		-//__Runtime deletion__//
16		-When deleting a runtime, the error message that is displayed is more descriptive. The error messages will now include the names of the flows that run on the container.
	16	+== **Next Generation Architecture Default** ==
17	17
18		-//__Wiretap & debug error messages__//
19		-The error messages that may be displayed when using wiretaps and the debugger have been improved, these are now more user friendly.
	18	+With this release, the next generation architecture will become the default. New models will use this generation as default.
20	20
21		-//__Action messages__//
22		-The formatting of action messages regarding changes in retention bytes/hours has been improved. The action message will now display the correct, actual behaviour.
	20	+[[image:Main.Images.Release Blog.WebHome@209-release-blog-next-gen-default.png]]
23	23
24		-== **Formatting & Alignments** ==
	22	+== **Cloud Template R11 Docker - Single Lane** ==
25	25
26		-//__Input fields__//
27		-Multiple input fields have been updated such that they expand when the amount of characters exceeds the default size. These updates were done to cater to large expressions.
	24	+This release introduces a new cloud template for all our customers running in a single-lane setup on the next generation architecture. This cloud template introduces faster machine boot up and improved auto-healing. The complete release notes on the cloud template can be found [[here>>doc:Main.Release Information.Cloud Templates.R11 Docker - Single Lane.WebHome||target="blank"]].
28	28
29		-//__UI improvements__//
30		-UI improvements for static input components have been done and the tooltip for optional/required toggles has been improved.
	26	+== **Cloud Template R13 Docker - Double Lane** ==
31	31
32		-//__Component changes reversion__//
33		-In the flow designer a bug could occur where the changes to a component would be reverted if the editing pop-up would be kept open for some minutes without having saved the changes yet. This has been fixed.
	28	+This release introduces a new cloud template for all our customers running in a double-lane setup on the next generation architecture. This cloud template introduces faster machine boot up and improved auto-healing. The complete release notes on the cloud template can be found [[here>>doc:Main.Release Information.Cloud Templates.R13 Docker - Double Lane.WebHome||target="blank"]].
34	34
35		-//__State generation statistics__//
36		-The state generation graphs will now show the correct number of cache hits and misses.
	30	+== **Feedback Items** ==
37	37
38		-//__Queue browser timestamps__//
39		-All timestamp formatting in the queue browser is now aligned to yyyy-MM-dd HH:mm:ss.SSS.
	32	+//__Unused properties overview__//
	33	+In Deploy > Releases, it is now possible to see all unused properties of an environment. This can be viewed by clicking the three dots in the Create phase section. Here it is also possible to quickly delete all or a selection of those unused properties. Unused properties are properties that are:
40	40
41		-//__Addition and deletion of internal recipients__//
42		-Internal recipients are now added and deleted correctly. Before, an internal recipient could be added and thereafter deleted automatically when refreshing the page.
	35	+* Not used by any runtime that is in the Create phase release.
	36	+* Not required by a flow that is in the Create phase release.
	37	+* If used as nested property, none of its parent properties (checks recursively) are in the Create phase release.
43	43
44		-== **Feedback Items** ==
	39	+//__Queue explorer milliseconds__//
	40	+The queue browser now displays milliseconds in the timestamps.
45	45
46		-//__Update flows__//
47		-In Create > Resources, a button "Update flows" has been added to update versions of all flows in which a resource is used.
	42	+//__Unused images__//
	43	+When a release is removed, the related unused images in the on-premises machines will be removed as well.
48	48
49		-//__Q&A forum search__//
50		-The option to search by pressing the Enter key has been added to the Q&A forum.
	45	+//__Carwash logging__//
	46	+A new logging feature enabling us to make better choices in encryption standards will be released.
51	51
52		-//__Memory settings__//
53		-It is now possible to change the memory settings of a newly added container before pressing "Apply to environment".
54		-//__Runtime validation__//
55		-Validation for runtimes that are moved from on premises to the cloud or vice versa has been improved.
	48	+//__Static alerts queue consumers__//
	49	+Alerting will now only generate alerts for queues that are created and managed by the eMagiz JMS server.
56	56
57		-//__Runtime overview image versions__//
58		-Insight into intended and actual deployments has been improved. If the release version number on runtimes is different compared with the release, this is shown in the runtime overview.
59		-
60	60	== **Bug Fixes** ==
61	61
62		-//__Removal of onramp__//
63		-We fixed an issue where it was not possible to remove the last onramp linked to a splitted entry (that was an all-entry before).
	53	+//__Flow Designer connection line__//
	54	+In the Flow Designer an issue has been fixed where the connection line for drawing channels did work well when scrolling or zooming in/out on the canvas.
64	64
65		-//__Runtime statistics details__//
66		-We fixed an issue where heap memory usage data was accumulating when zooming out in the runtime statistics details dashboards.
	56	+//__Portal for migrated models__//
	57	+We fixed a rare case where a runtime could not start, or logging, errors and metrics could not be seen in the portal for a model that had just migrated to the next generation architecture.
67	67
68		-//__Deployment prechecks__//
69		-During deployments, prechecks can be executed on runtimes level for runtimes that still have to be deployed. These prechecks can be executed via Deploy > Architecture.
	59	+//__Error channel inbounds__//
	60	+We added a migration step, where we set the error channel to “errorChannel” of all inbounds in a flow if the custom error handling is set to false. Before, the error channel would be set to “errorChannel” only for the first inbound in an entry flow.
70	70
71	71	== **Fancy Forum Answers** ==
72	72
73	73	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:
74	74
75		-* [[Changing filename based on attribute>>https://my.emagiz.com/p/question/172825635703696968||target="blank"]]
76		-* [[Payload must be an instance of a Map>>https://my.emagiz.com/p/question/172825635703709401||target="blank"]]
77		-* [[Promoting a system to a split gateway>>https://my.emagiz.com/p/question/172825635703722185||target="blank"]]
	66	+* [[JSONPath in SpEL expressions>>https://my.emagiz.com/p/question/172825635703415034||target="blank"]]
78	78
79		-== **Key Takeaways** ==
	68	+== **Key takeaways** ==
80	80
81	81	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:
82	82
...	...	@@ -87,6 +87,7 @@
87	87	* Check out the release notes [here]
88	88	* Start thinking about how the license tracker can aid your development
89	89	* Start thinking about major, minor, and patch
	79	+* Upgrade to the latest build number
90	90	* Keep making great integrations
91	91
92	92	Let's stay in touch and till next time!
...	...	@@ -94,6 +94,7 @@
94	94	{{info}}
95	95	~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
96	96
	87	+~*~* Indicates a next-generation-architecture only feature.
97	97	{{/info}}
98	98	)))
99	99