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,136 @@
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!** 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.
	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, select infra flows in a release, and deploy multiple agents to a single machine that adheres to specific conditions. But before we dive into all that has changed, we will publish several announcements via this release blog (and other channels) to prepare your model for upcoming major changes.
6	6
7		-== **3rd generation improvements** ==
	8	+== ** Announcement - TLS versions deprecated** ==
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.
	10	+Placeholder for info from Bas
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.
	12	+{{info}}Text{{/info}}
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.
	14	+== **Announcement - Spring 6** ==
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.
	16	+In the next release, we expect to release a major version of our current runtime base image for all our clients running on the **current runtime** architecture. This image moves the eMagiz stack from Java 8 to Java 17, and from Spring Framework 5 to Spring Framework 6. Although eMagiz will try to make the transition as smooth as possible, we recommend that you start with the following preparations.
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.
	18	+{{warning}}
	19	+* Make sure that your release is running on the **latest** flow versions. After the release of the new image, eMagiz will push new flow versions of components that have changes. These new flow versions must be included in the subsequent release. Having your release already on the **latest** flow versions makes this less affecting
	20	+* To help you identify which flow versions are especially important here, you can consider all flows that contain any of the following components:
	21	+** Simple job launcher (data pipelines)
	22	+** Job explorer (data pipelines)
	23	+** HTTP components message sender (support object)
	24	+** Web service outbound gateway (with a 'message sender' attribute specified)
	25	+** SFTP session factory (support object)
	26	+** API gateways with OAuth2 as security mechanism.
	27	+* We recommend identifying flows with (advanced) custom Groovy scripts. As our Java version changes and the Spring version changes, this may affect the availability of the libraries on the classpath, and therefore the validity of import statements. You can already test the Groovy script using the flow testing functionality as flow testing is already running on the Java 17 and Spring Framework 6 baseline.
	28	+** In addition, the groovy version used has been moved from version 3.0.19 to 4.0.18. These changes may affect your scripts as well. These release notes outline the major changes
	29	+* The code handling SFTP file transfer has been overhauled completely. Although this should not affect you, we encourage you to test your SFTP integrations before deploying to Production.{{/warning}}
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.
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.
	32	+== **Infra flow selection** ==
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.
	34	+This release will include a significant update to our release functionality, which allows you to configure your release. Presently, eMagiz will allow you to see changes on the infra-flow level visually.
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.
	36	+[[image:Main.Images.Release Blog.WebHome@release-216-hack-heaven--infra-flow-comparison.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||target="blank"]] on the subject.{{/warning}}
	38	+In edit mode, you can select a new version via the right-click option, which you already use for other flows.
37	37
38		-== **Feedback items ** ==
	40	+[[image:Main.Images.Release Blog.WebHome@release-216-hack-heaven--infra-flow-selection.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.
	42	+We have also added a title to each context menu that specifies the flow type (e.g., exit connector, container infra, connector infra) for additional clarity while constructing your release.
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.
	44	+[[image:Main.Images.Release Blog.WebHome@release-216-hack-heaven--context-menu-title.png]]
45	45
46		-{{warning}}Make sure to check the changes and create a new version afterward to deploy the changes.{{/warning}}
	46	+== **Multiple environments selection** ==
47	47
48		-== **Bug fixes ** ==
	48	+{{warning}}The following is only applicable under the following conditions:
	49	+ * Windows 2022 server
	50	+ * At least one port opened (as a consequence of a hosted web service){{/warning}}
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.
	52	+When configuring your Deploy Agent, you now have an additional option that the user can activate. This checkbox unlocks the possibility of stability when running multiple deploy agents on one machine.
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}}
	54	+[[image:Main.Images.Release Blog.WebHome@release-216-hack-heaven--multiple-environments.png]]
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.
	56	+== **Feedback Items** ==
	57	+//__Easier component selection in flow designer__//
	58	+The area selector through which you can select one or more components has improved to allow for an easier selection of said components when displayed close to the edge of the canvas. Expanding the area allows you to select these components, which will become much easier.
57	57
	60	+//__Improved handling of optionality in JSON on lists__//
	61	+Previously, eMagiz always created a JSON array if your data model expected a list. This led to unexpected and undesirable behavior of the message, as empty arrays are not always accepted by external parties.
	62	+
	63	+With this release, we have changed the way in which we generate the JSON output should there be an empty list. Consequently, the empty list will **not** be part of the output anymore, as desired.
	64	+
	65	+//__Loading bar when searching for log entries__//
	66	+To indicate to the user that eMagiz is still busy retrieving log entries, we have added a loading bar to the log entry overview upon pressing search.
	67	+
	68	+//__Improved feedback when deleting elements from Capture__//
	69	+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.
	70	+
	71	+//__Enhanced filter options in Manage__//
	72	+With this release, we have added filter options on both the Alerting tab and the Trigger configuration pop-up. This allows users to filter on Status (Alerting) and Queues, Topics, Recipients, and more (Trigger configuration pop-up) in these places.
	73	+
	74	+//__Copy property names from Create__//
	75	+This release unlocks the possibility of easily copying the name of a property placeholder so it can be used while deploying.
	76	+
	77	+//__Improved feedback during migration to the current runtime architecture__//
	78	+Should you try to migrate the JMS before any other runtime under Create -> Settings, we have improved the feedback. This feedback will tell you why you cannot migrate in this order.
	79	+
	80	+//__Block user from making changes to their cloud while another upgrade is still in progress__//
	81	+We now block users from changing their cloud configuration when another upgrade is ongoing.
	82	+
	83	+//__Cron trigger validation__//
	84	+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.
	85	+
	86	+== **Bug Fixes** ==
	87	+//__Making Edit (and View) the default action when configuring parameters__//
	88	+We have made the Edit (and View) button the default action when configuring parameters in a transformation.
	89	+
	90	+//__Property configuration pop-up resized__//
	91	+We have resized the property configuration overviews to make the property value better readable.
	92	+
	93	+//__Alphabetically sorted components in the flow designer__//
	94	+As of this release, we now sort the components alphabetically in the flow designer.
	95	+
	96	+//__Improved sorting on runtime overview__//
	97	+As of this release, we now sort the runtimes in the runtime overview correctly by time. This means that the runtime with a changed status, closest to the current date and time, is shown at the top of the list. This should reduce the chance of overlooking a critical mistake.
	98	+
	99	+//__Improved sorting on catalog overview__//
	100	+As of this release, we now sort the topics in the catalog by name.
	101	+
	102	+//__Styling fix on rich text editors__//
	103	+Rich text editors are used in various parts of the portal. This release fixes a broken styling configuration that made it difficult to fill in information in these editors.
	104	+
	105	+//__Styling fix on release edit__//
	106	+As of this release, the correct icon (green) will be shown when wanting to add a second API operation under the same "header."
	107	+
	108	+//__Removed false-positive alerts on transformations__//
	109	+When transforming a string to a non-empty string, eMagiz would also show an alert even if the user made a check to avoid an empty string as output. This behavior is now corrected. This will significantly reduce the number of alerts you will see as a user within the context of your transformation.
	110	+
	111	+//__Event Streaming Graphs - view thirty days back__//
	112	+Just like the other views, we now also provide the user with a default thirty-day window to analyze relevant statistics related to event streaming further.
	113	+
	114	+//__Improved helptext__//
	115	+We have improved various help texts across the portal to indicate better what should be filled in for specific fields.
	116	+
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"]]
	121	+* [[XSD is only partially imported into eMagiz (xmlStat.xsd)>>https://my.emagiz.com/p/question/172825635703773349||target="blank"]]
65	65
66		-== **Key takeaways** ==
	123	+== **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:
	125	+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.
	129	+* 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}}
	141	+{{/info}}
	142	+)))
	143	+
	144	+(((
	145	+{{toc/}}
	146	+)))
87	87	{{/container}}
	148	+{{/container}}