Changes for page 216 - Hack Heaven

Summary

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

Details

Page properties

Title

...	...	@@ -1,1 +1,1 @@
1		-209 - Max Verstappen
	1	+216 - Hack Heaven

Author

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

Content

...	...	@@ -3,75 +3,118 @@
3	3	(((
4	4	[[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]]
5	5
6		-**Hi there, eMagiz developers!** We have done .....
	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.
7	7
	8	+== ** Announcement - TLS versions deprecated** ==
	9	+
	10	+Placeholder for info from Bas
	11	+
	12	+{{info}}Text{{/info}}
	13	+
	14	+== **Announcement - Spring 6** ==
	15	+
	16	+In the next release, we expect to release a major version of our current runtime base image. 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.
	17	+
8	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}}
	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: Simple job launcher (data pipelines), Job explorer (data pipelines), HTTP components message sender (support object), Web service outbound gateway (with a 'message sender' attribute specified), SFTP session factory (support object), API gateways with OAuth2 as security mechanism.
	21	+* 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.
	22	+* 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
	23	+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}}
11	11
12		-== **Quicker Deployment Plan** ==
13	13
14		-We fixed an issue which caused the release preparation step to take longer than necessary and caused the machine deployment steps to execute when they could be skipped. So, the deploynment plan will be finished much quicker now!
	26	+== **Infra flow selection** ==
15	15
16		-== **Next Generation Architecture Default** ==
	28	+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.
17	17
18		-With this release, the next generation architecture will become the default. New models will use this generation as default.
	30	+[[image:Main.Images.Release Blog.WebHome@release-216-hack-heaven--infra-flow-comparison.png]]
19	19
20		-[[image:Main.Images.Release Blog.WebHome@209-release-blog-next-gen-default.png]]
	32	+In edit mode, you can select a new version via the right-click option, which you already use for other flows.
21	21
22		-== **Cloud Template R11 Docker - Single Lane** ==
	34	+[[image:Main.Images.Release Blog.WebHome@release-216-hack-heaven--infra-flow-selection.png]]
23	23
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"]].
	36	+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.
25	25
26		-== **Cloud Template R13 Docker - Double Lane** ==
	38	+[[image:Main.Images.Release Blog.WebHome@release-216-hack-heaven--context-menu-title.png]]
27	27
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"]].
	40	+== **Multiple environments selection** ==
29	29
	42	+{{warning}}The following is only applicable under the following conditions:
	43	+ * Windows 2022 server
	44	+ * At least one port opened (as a consequence of a hosted web service){{/warning}}
	45	+
	46	+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.
	47	+
	48	+[[image:Main.Images.Release Blog.WebHome@release-216-hack-heaven--multiple-environments.png]]
	49	+
30	30	== **Feedback Items** ==
	51	+//__Easier component selection in flow designer__//
	52	+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.
31	31
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:
	54	+//__Improved handling of optionality in JSON on lists__//
	55	+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.
34	34
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.
	57	+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.
38	38
39		-//__Send build requests asynchronously__//
40		-The step in the deployment plan concerning the preparation of runtime images will now be executed more quickly and reliably.
	59	+//__Loading bar when searching for log entries__//
	60	+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.
41	41
42		-//__Queue explorer milliseconds__//
43		-The queue browser now displays milliseconds in the timestamps.
	62	+//__Improved feedback when deleting elements from Capture__//
	63	+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.
44	44
45		-//__Cancel and next buttons order__//
46		-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.
	65	+//__Enhanced filter options in Manage__//
	66	+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.
47	47
48		-//__Unused images__//
49		-When a release is removed, the related unused images in the on-premises machines will be removed as well.
	68	+//__Copy property names from Create__//
	69	+This release unlocks the possibility of easily copying the name of a property placeholder so it can be used while deploying.
50	50
51		-//__Carwash logging__//
52		-A new logging feature enabling us to make better choices in encryption standards will be released.
	71	+//__Improved feedback during migration to the current runtime architecture__//
	72	+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.
53	53
54		-//__Static alerts queue consumers__//
55		-Alerting will now only generate alerts for queues that are created and managed by the eMagiz JMS server.
	74	+//__Block user from making changes to their cloud while another upgrade is still in progress__//
	75	+We now block users from changing their cloud configuration when another upgrade is ongoing.
56	56
	77	+//__Cron trigger validation__//
	78	+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.
	79	+
57	57	== **Bug Fixes** ==
	81	+//__Making Edit (and View) the default action when configuring parameters__//
	82	+We have made the Edit (and View) button the default action when configuring parameters in a transformation.
58	58
59		-//__Flow Designer connection line__//
60		-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.
	84	+//__Property configuration pop-up resized__//
	85	+We have resized the property configuration overviews to make the property value better readable.
61	61
62		-//__Portal for migrated models__//
63		-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.
	87	+//__Alphabetically sorted components in the flow designer__//
	88	+As of this release, we now sort the components alphabetically in the flow designer.
64	64
65		-//__Error channel inbounds__//
66		-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.
	90	+//__Improved sorting on runtime overview__//
	91	+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.
67	67
	93	+//__Improved sorting on catalog overview__//
	94	+As of this release, we now sort the topics in the catalog by name.
	95	+
	96	+//__Styling fix on rich text editors__//
	97	+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.
	98	+
	99	+//__Styling fix on release edit__//
	100	+As of this release, the correct icon (green) will be shown when wanting to add a second API operation under the same "header."
	101	+
	102	+//__Removed false-positive alerts on transformations__//
	103	+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.
	104	+
	105	+//__Event Streaming Graphs - view thirty days back__//
	106	+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.
	107	+
	108	+//__Improved helptext__//
	109	+We have improved various help texts across the portal to indicate better what should be filled in for specific fields.
	110	+
68	68	== **Fancy Forum Answers** ==
69	69
70	70	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:
71	71
72		-* [[JSONPath in SpEL expressions>>https://my.emagiz.com/p/question/172825635703415034||target="blank"]]
	115	+* [[XSD is only partially imported into eMagiz (xmlStat.xsd)>>https://my.emagiz.com/p/question/172825635703773349||target="blank"]]
73	73
74		-== **Key takeaways** ==
	117	+== **Key Takeaways** ==
75	75
76	76	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:
77	77
...	...	@@ -82,7 +82,6 @@
82	82	* Check out the release notes [here]
83	83	* Start thinking about how the license tracker can aid your development
84	84	* Start thinking about major, minor, and patch
85		-* Upgrade to the latest build number
86	86	* Keep making great integrations
87	87
88	88	Let's stay in touch and till next time!
...	...	@@ -90,7 +90,6 @@
90	90	{{info}}
91	91	~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
92	92
93		-~*~* Indicates a next-generation-architecture only feature.
94	94	{{/info}}
95	95	)))
96	96