Changes for page 216 - Hack Heaven

Summary

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

Details

Page properties

Title

...	...	@@ -1,1 +1,1 @@
1		-215 - Tiny Tales
	1	+216 - Hack Heaven

Author

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

Content

...	...	@@ -2,39 +2,117 @@
2	2	{{container layoutStyle="columns"}}
3	3	(((
4	4	[[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]]
5		-
6		-**Hi there, eMagiz developers!** This release blog is small because we have been busy working on items that will be released later. For this release, the event streaming graph has been improved. Moreover, some bug fixes have been done. The validation for queue names with respect to spaces has been improved. Furthermore, it is now possible to remove an onramp that was previously linked to an all-entry. Lastly, it is now possible to log in to eMagiz by pressing enter when the username field is selected.
7	7
	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	+
	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	+
	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: 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}}
	24	+
	25	+
	26	+== **Infra flow selection** ==
	27	+
	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.
	29	+
	30	+[[image:Main.Images.Release Blog.WebHome@release-216-hack-heaven--infra-flow-comparison.png]]
	31	+
	32	+In edit mode, you can select a new version via the right-click option, which you already use for other flows.
	33	+
	34	+[[image:Main.Images.Release Blog.WebHome@release-216-hack-heaven--infra-flow-selection.png]]
	35	+
	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.
	37	+
	38	+[[image:Main.Images.Release Blog.WebHome@release-216-hack-heaven--context-menu-title.png]]
	39	+
	40	+== **Multiple environments selection** ==
	41	+
	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	+
8	8	== **Feedback Items** ==
9		-//__Improved event streaming graph__//
10		-The event streaming graph has been improved so that the offset difference of a topic is the sum of the offset differences of each partition in that topic.
	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.
11	11
12		-[[image:Main.Images.Release Blog.WebHome@release-215-tiny-tales-topics-2.png]]
	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.
13	13
14		-//__Flow versions auto deletion__//
15		-Previously, the latest ten versions of a flow were not always selectable for a release. This has been improved so that from now on, the latest ten committed versions of each flow are always available.
	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.
16	16
	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.
	61	+
	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.
	64	+
	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.
	67	+
	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.
	70	+
	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.
	73	+
	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.
	76	+
	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	+
17	17	== **Bug Fixes** ==
18		-//__Queue name validation__//
19		-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.
	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.
20	20
21		-[[image:Main.Images.Release Blog.WebHome@release-215-tiny-tales-queue-name-validation.png]]
	84	+//__Property configuration pop-up resized__//
	85	+We have resized the property configuration overviews to make the property value better readable.
22	22
23		-//__Removal of onramp__//
24		-An issue has been fixed where removing an onramp that was previously linked to a combined entry was impossible in the Create phase.
	87	+//__Alphabetically sorted components in the flow designer__//
	88	+As of this release, we now sort the components alphabetically in the flow designer.
25	25
26		-//__eMagiz login__//
27		-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.
	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.
28	28
	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	+
29	29	== **Fancy Forum Answers** ==
30	30
31	31	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:
32	32
33		-* [[eMagiz Mendix Kafka Module Issue (Mendix 10)>>https://my.emagiz.com/p/question/172825635703748180||target="blank"]]
34		-* [[SFTP + Privatekey not working>>https://my.emagiz.com/p/question/172825635703760538||target="blank"]]
35		-* [[Attribute name is not allowed to start with 'xml'>>https://my.emagiz.com/p/question/172825635703760662||target="blank"]]
36		-* [[How do I change the default content-type from ISO-8859-1 to utf-8>>https://my.emagiz.com/p/question/172825635703760803||target="blank"]]
37		-* [[Preparing Image for <runtime> failed>>https://my.emagiz.com/p/question/172825635703761022||target="blank"]]
	115	+* [[XSD is only partially imported into eMagiz (xmlStat.xsd)>>https://my.emagiz.com/p/question/172825635703773349||target="blank"]]
38	38
39	39	== **Key Takeaways** ==
40	40