Changes for page 213 - Joyful Journeys

Summary

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

Details

Page properties

Title

...	...	@@ -1,1 +1,1 @@
1		-194 - Giant Leap
	1	+209 - Max Verstappen

Author

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

Content

...	...	@@ -2,73 +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 worked around the clock to release various improvement points within the 3rd generation runtime and elsewhere. We have improved the feedback provided when a flow can't start due to an incorrect transformation, improved when specific logging is triggered, and improved the stability of our internal infrastructure. On top of that, we fixed several bugs surrounding other parts of the platform. So without further ado, let us look at all these improvements.
	5	+**Hi there, eMagiz developers!** We have done .....
6	6
7		-== **3rd generation improvements** ==
	7	+== **Next Generation Architecture Default** ==
	8	+With this release, the next generation architecture will become the default. New models will use this generation as default.
8	8
9		-//__Better feedback in the error log when a corrupt stylesheet is encountered__//
10		-We have improved the logging within a 3rd generation runtime that identifies the broken resource by name within a container and informs you to navigate to Create -> Resources to see in which flows the resource is used so you can take the appropriate action.
	10	+[[image:Main.Images.Release Blog.WebHome@release-blog-next-gen-default.png]]
11	11
12		-//__Better internal error handling to avoid unnecessary alerting and notifications__//
13		-We have improved the internal error handling when sending metrics from the runtime to our monitoring stack. This will gravely reduce the alerts you receive on this topic when your model runs on the 3rd generation monitoring stack.
	12	+== **Cloud Template R11 - Single Lane** ==
	13	+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
14	14
15		-//__Improved Manage Dashboard__//
16		-This release improves what you can see in the Manage Dashboard after you migrate your model to the 3rd generation runtime architecture.
	15	+== **Cloud Template R13 - Double Lane** ==
17	17
18		-//__Improved process surrounding "slot standby" and "slot wakeup" for 3rd generation runtimes__//
19		-When a slot is put into standby mode, we also stop all on-premise runtimes to avoid excessive logging (and alerting) on your models with this functionality. The opposite happens when the slot wakeup is triggered. As a result, not only the cloud runtimes are started but also all on-premise runtimes.
20	20
21		-//__Improved process of deploy preparation__//
22		-With this release, we have improved the process through which your deployment action is prepared by eMagiz. As a result, the chances of unexpected behavior occurring in your model are drastically reduced.
	18	+== **Feedback Items** ==
23	23
24		-//__Improved migration of Streaming container__//
25		-When migrating your streaming container, we now consider whether "custom error handling" is used within one of the event processors. Based on that determination, additional components are added to ensure that the streaming container will work after migrating without manual intervention.
	20	+//__Unused properties overview__//
	21	+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:
	22	+* Not used by any runtime that is in the Create phase release.
	23	+* Not required by a flow that is in the Create phase release.
	24	+* If used as nested property, none of its parent properties (checks recursively) are in the Create phase release.
26	26
27		-//__Add History to Notifications in Manage__//
28		-To improve the auditability of our platform, we have introduced an audit trail to the Notification section in Manage for models running on our 3rd generation monitoring stack. This way, it is always visible when the notifications were paused and who paused or unpaused the notifications.
	26	+//__Send build requests asynchronously__//
	27	+The step in the deployment plan concerning the preparation of runtime images will now be executed more quickly and reliably.
29	29
30		-//__Improved Manage phase for Event Streaming__//
31		-Based on the feedback on our first iteration of the Manage phase for Event Streaming, we have improved the graphs and the calculations that fill the graphs with values. On top of that, we have added help texts to clarify what each chart our table displays to you.
	29	+//__Queue explorer milliseconds__//
	30	+The queue browser now displays milliseconds in the timestamps.
32	32
33		-//__Improved help text for network volumes__//
34		-With this release, we have improved the help text that explains network volumes and how to use them within our solution.
	32	+//__Cancel and next buttons order__//
	33	+The order of the cancel and next buttons when creating a new trigger has been changed to increase alignment across the platform. Now, all cancel buttons are placed on the right of a 'next' or 'save' button.
35	35
36		-{{warning}}Should you be interested in migrating your model to our new 3rd generation architecture, don't hesitate to contact us at [[productmanagement@emagiz.com>>mailto:productmanagement@emagiz.com]] or read our [[documentation>>doc:Main.eMagiz Academy.Fundamentals.fundamental-runtime-generation3||target="blank"]] on the subject.{{/warning}}
	35	+//__Unused images__//
	36	+When a release is removed, the related unused images in the on-premises machines will be removed as well.
37	37
38		-== **Feedback items ** ==
	38	+//__Carwash logging__//
	39	+A new logging feature enabling us to make better choices in encryption standards will be released.
39	39
40		-//__Generation of security logic API Gateway in case of API Key as security method is improved__//
41		-With this release, we have improved the generation of security logic within the Create phase related to API Gateways that use the API Key method as their security mechanism.
	41	+//__Static alerts queue consumers__//
	42	+Alerting will now only generate alerts for queues that are created and managed by the eMagiz JMS server.
42	42
43		-//__User Roles are sorted alphabetically__//
44		-All user roles under User Management are now also sorted alphabetically.
	44	+== **Bug Fixes** ==
45	45
46		-//__Name of keystore for user management now includes the environment__//
47		-To improve the naming of the downloaded keystore that needs to be distributed to external parties, we have added the name of the environment to the filename. You can distinguish between the various environments by looking at the filename.
	46	+//__Images rebuild__//
	47	+We fixed an issue which caused the release preparation step to take longer time than necessary and caused the machine deployment steps to execute when they could be skipped.
48	48
49		-== **Bug fixes ** ==
	49	+//__Flow Designer connection line__//
	50	+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.
50	50
51		-//__Consolidated upgrade process cloud template__//
52		-With this release, we have removed some specific update options that could cause mismatches between what was visually displayed and what was happening in the cloud.
	52	+//__Portal for migrated models__//
	53	+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.
53	53
54		-//__Ensure users can deploy release on environments they have edit rights on__//
55		-Currently, users with limited rights in Deploy, for example, only edit rights in Test, can now activate and deploy releases ready for other environments but need to be deployed on the environment for which they have the rights to do so.
	55	+//__Error channel inbounds__//
	56	+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.
56	56
57	57	== **Fancy Forum Answers** ==
58	58
59	59	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:
60	60
61		-* [[API Security not updated in all entry flow>>https://my.emagiz.com/p/question/172825635703363718||target="blank"]]
62		-* [[Preventing exceptions triggering on HTTP 400 status code>>https://my.emagiz.com/p/question/172825635703351155||target="blank"]]
63		-* [[Deployment of 3rd gen runtimes to Azure Kubernetes Service (AKS containers)>>https://my.emagiz.com/p/question/172825635703350980||target="blank"]]
	62	+* [[Message Redelivery blank error message>>https://my.emagiz.com/p/question/172825635703619933||target="blank"]]
	63	+* [[Timeout error kafka batch creation>>https://my.emagiz.com/p/question/172825635703620012||target="blank"]]
	64	+* [[SFTP Connectivity: Transfering a whole folder structure>>https://my.emagiz.com/p/question/172825635703632587||target="blank"]]
	65	+* [[Next generation architecture with dynamic file pickup / filedrop>>https://my.emagiz.com/p/question/172825635703632732||target="blank"]]
64	64
	67	+
65	65	== **Key takeaways** ==
66	66
67		-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:
	70	+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:
68	68
69	69	* If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
70	70	* If you have feedback or ideas for us, talk to the Platypus
71		-* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
	74	+* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
72	72	* Clear your browser cache (Ctrl + Shift + Del)
73	73	* Check out the release notes [here]
74	74	* Start thinking about how the license tracker can aid your development
...	...	@@ -81,6 +81,6 @@
81	81	{{info}}
82	82	~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
83	83
84		-~*~* Indicates a GEN3-only feature.
	87	+~*~* Indicates a next-generation-architecture only feature.
85	85	{{/info}})))((({{toc/}}))){{/container}}
86	86	{{/container}}