Changes for page 216 - Hack Heaven

Summary

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

Details

Page properties

Title

...	...	@@ -1,1 +1,1 @@
1		-194 - Big Leap
	1	+216 - Hack Heaven

Content

...	...	@@ -1,80 +1,107 @@
1	1	{{container}}
2		-{{container layoutStyle="columns"}}(((
	2	+{{container layoutStyle="columns"}}
	3	+(((
3	3	[[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]]
	5	+
	6	+**Hi there, eMagiz developers!** As part of our alignment week we also had a hackathon event focusing on a wide array of reported feedback on the portal. The majority of the release blog will be focused on this. On top of that we launch new functionality that makes it easier to transform to JSON, to select infra flows in a release, and makes it possible to deploy multiple agents to a single machine that adheres to specific conditions. Furthermore, several announcements will be made via this release blog (and other channels) to better prepare your model for upcoming major changes.
4	4
5		-**Hi there, eMagiz developers!** In the last couple of weeks, we have worked around the clock to release various improvements points within the 3rd generation runtime and elsewhere. Among others we have improved the feedback provided when a flow can't start due to an incorrect transformation. Improved when certain logging is triggerd and improved the stability of our internal infrastructure. On top of that we fixed several bug fixes surrounding other parts of the platform. So without further ado let us take a look at all these improvements.
	8	+== ** Announcement - TLS 1.0 and 1.1 deprecated** ==
6	6
7		-== **3rd generation improvements** ==
	10	+Placeholder for info from Bas
8	8
9		-//__Better feedback in 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.
	12	+{{info}}Text{{/info}}
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 number of alerts you will receive on this topic when your model runs on the 3rd generation monitoring stack.
	14	+== **Announcement - Spring 6** ==
14	14
15		-//__Improved Manage Dashboard__//
16		-This release improves what you can see in the Manage Dashboard after you migrated your model to the 3rd generation runtime architecture.
	16	+Placeholder for info from Jelle
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 now also stop all on-premise runtimes to avoid excessive logging (and alerting) on your models that have this functionality activated. 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.
	18	+{{warning}}Text{{/warning}}
20	20
21		-//__Improved process of deploy preparation__//
22		-With this release we have improved the process through which your deploy action is preparated by eMagiz. As a result the chances of unexpected behavior occuring in your model are drastically reduced.
	20	+== ** Updated release functionality - Infra flow selection** ==
23	23
24		-//__Improved migration of Streaming container__//
25		-When migrating your streaming container we now take into account whether "custom error handling" is used within one of the event processors. Based on that determination specific additional components are added to ensure that the streaming container will work after migrating without any manual intervention.
	22	+This release will include a major update of our release functionality through which you can configure your release. As of now eMagiz will provide you with the option to visually see changes on infra flow level.
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.
	24	+[[image:Main.Images.Release Blog.WebHome@release-216-hack-heaven--infra-flow-comparison.png]]
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 helptexts to clarify what each graph our table displays to you.
	26	+When you are in edit mode you can select a new version via the right-click option as you were used to for other flows.
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.
	28	+[[image:Main.Images.Release Blog.WebHome@release-216-hack-heaven--infra-flow-selection.png]]
35	35
36		-{{warning}}Should you be interested in migrating your model to our new 3rd generation architecture, don't hesistate to contact us at [[productmanagement@emagiz.com>>mailto:productmanagement@emagiz.com]] or read our [[documentation>>doc:Main.eMagiz Academy.Fundamentals.fundamental-runtime-generation3.WebHome||target="blank"]] on the subject.{{/warning}}
	30	+On top of that we have added an title to each context menu that specifies the flow type (i.e. exit connector, container infra, connector infra) for additional clarity while constructing your release.
37	37
38		-== **Feedback items ** ==
	32	+[[image:Main.Images.Release Blog.WebHome@release-216-hack-heaven--context-menu-title.png]]
39	39
40		-//__Removed OData as option for an API Gateway operation__//
41		-With this release, we have removed the OData operation option as it was not used and was not fully supported anymore by the platform.
	34	+== ** Updated deploy functionality on-premise - Multiple environments selection** ==
42	42
43		-//__Changes in API Gateway operation paths is automatically updated in Create__//
44		-When you change your path on a hosted API Gateway we will now automatically update the accompanying component in your Create (all-)entry.
	36	+{{warning}}The following is only applicable under the following conditions:
	37	+ * Windows 2022 server
	38	+ * Atleast one port opened (as a consequence of a hosted web service){{/warning}}
45	45
46		-{{warning}}Make sure to check the changes and create a new version afterward to deploy the changes.{{/warning}}
	40	+When configuring your Deploy Agent you now have an additional option that can be activated by the user. With the help of this checkbox you unlock the possibility of stabily running multiple deploy agents on one machine.
47	47
48		-== **Bug fixes ** ==
	42	+[[image:Main.Images.Release Blog.WebHome@release-216-hack-heaven--multiple-environments.png]]
49	49
50		-//__Prevent endless loop in Deploy -> User Management__//
51		-With this release, we have changed the way we update properties when user management is updated for an API gateway using the API Key security mechanisms. This will prevent the endless loop that could now happen on occasion.
	44	+== **Feedback Items** ==
	45	+//__Easier component selection in flow designer__//
	46	+The area selector through which you can select one or more components has improved to allow for an easier selection of said components when they are displayed closed to the edge of the canvas. By expanding the area you can select the selection of these components will become much easier.
52	52
53		-{{warning}}Any operation that is incorrectly deleted from Deploy while still end up in the logic and could cause issue so pay attention when removing API Gateway operations.{{/warning}}
	48	+//__Improved handling of optionality in JSON on lists__//
	49	+Previously, eMagiz would always create a JSON array if your data model expected a list. This would lead to unexpected and undesirable behavior of the message as empty arrays are not always accepted by external parties. With this release we have changed the way in which we generate the JSON output should there be an empty list in the output. Consequently the empty list will **not** be part of the output anymore as desired.
54	54
55		-//__Update error handling during migration to the 3rd generation runtime__//
56		-As of now the error handling of all flows is correctly updated whilst migrating to the 3rd generation runtime configuration.
	51	+//__Loading bar when searching for log entries__//
	52	+To indicate to the user that eMagiz is still busy retrieving log entries we have now added a loading bar to the log entry overview upon pressing search.
57	57
	54	+//__Improved feedback when deleting elements from Capture__//
	55	+To better specify to the user which integration or system the user intends to delete we have improved the text in the confirmation pop-up. This way we can provide more information to the user to avoid mistakes.
	56	+
	57	+//__Enhanced filter options in Manage__//
	58	+With this release we have added filter options on both the Alerting tab and the Trigger configuration pop-up. This results in being able to filter on Status (Alerting) and Queues, Topics, Recipients, and more (Trigger configuration pop-up) in these places.
	59	+
	60	+//__Copy property names from Create__//
	61	+This release unlocks the possibility to easily copy the name of a property placeholder so it can be used whilst deploying.
	62	+
	63	+//__Improved feedback during migration to the current-runtime architecture__//
	64	+We have improved the feedback should you try to migrate the JMS before any other runtime under Create -> Settings.
	65	+
	66	+//__Block user from making changes to their cloud whilst another upgrade is still in progress__//
	67	+We now block the user from making changes to their cloud configuration when another upgrade is still in progress.
	68	+
	69	+//__Cron trigger validation__//
	70	+We have added a validation check upon saving a cron expression in the Flow Designer to avoid flows not starting due to a misconfigured cron expression.
	71	+
	72	+== **Bug Fixes** ==
	73	+//__Queue name validation__//
	74	+The validation regarding undesired spaces for components that use a queue name has been improved. Specifically, users are now prevented from creating a queue name with a space in the queue name when editing this in the Create phase in the Flow Designer.
	75	+
	76	+[[image:Main.Images.Release Blog.WebHome@release-215-tiny-tales-queue-name-validation.png]]
	77	+
	78	+//__Removal of onramp__//
	79	+An issue has been fixed where removing an onramp that was previously linked to a combined entry was impossible in the Create phase.
	80	+
	81	+//__eMagiz login__//
	82	+In the login screen, users can now press "enter" to log in when the username field is selected. Previously, this was only the case for the password field.
	83	+
58	58	== **Fancy Forum Answers** ==
59	59
60	60	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:
61	61
62		-* [[Access Spring ApplicationContext within Groovy Script>>https://my.emagiz.com/p/question/172825635703325469||target="blank"]]
63		-* [[Configuration problem: Failed to locate '$autoCreateChannelCandidates'>>https://my.emagiz.com/p/question/172825635703312551||target="blank"]]
64		-* [[503 on SOAP Webservice hosted in eMagiz>>https://my.emagiz.com/p/question/172825635703325386||target="blank"]]
	88	+* [[eMagiz Mendix Kafka Module Issue (Mendix 10)>>https://my.emagiz.com/p/question/172825635703748180||target="blank"]]
	89	+* [[SFTP + Privatekey not working>>https://my.emagiz.com/p/question/172825635703760538||target="blank"]]
	90	+* [[Attribute name is not allowed to start with 'xml'>>https://my.emagiz.com/p/question/172825635703760662||target="blank"]]
	91	+* [[How do I change the default content-type from ISO-8859-1 to utf-8>>https://my.emagiz.com/p/question/172825635703760803||target="blank"]]
	92	+* [[Preparing Image for <runtime> failed>>https://my.emagiz.com/p/question/172825635703761022||target="blank"]]
65	65
66		-== **Key takeaways** ==
	94	+== **Key Takeaways** ==
67	67
68		-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:
	96	+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:
69	69
70	70	* If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
71	71	* If you have feedback or ideas for us, talk to the Platypus
72		-* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
	100	+* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
73	73	* Clear your browser cache (Ctrl + Shift + Del)
74	74	* Check out the release notes [here]
75	75	* Start thinking about how the license tracker can aid your development
76	76	* Start thinking about major, minor, and patch
77		-* Upgrade to the latest build number
78	78	* Keep making great integrations
79	79
80	80	Let's stay in touch and till next time!
...	...	@@ -82,6 +82,11 @@
82	82	{{info}}
83	83	~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
84	84
85		-~*~* Indicates a GEN3-only feature.
86		-{{/info}})))((({{toc/}}))){{/container}}
	112	+{{/info}}
	113	+)))
	114	+
	115	+(((
	116	+{{toc/}}
	117	+)))
87	87	{{/container}}
	119	+{{/container}}