Changes for page 216 - Hack Heaven

Summary

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

Details

Page properties

Title

...	...	@@ -1,1 +1,1 @@
1		-214 - System Symphony
	1	+216 - Hack Heaven

Author

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

Content

...	...	@@ -2,53 +2,111 @@
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!** 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.
5	5
6		-**Hi there, eMagiz developers!** This release contains multiple bug fixes, as well as some other improvements. The monitoring graphs have been improved, such that they can now show data up to the last thirty days. Moreover, we can now deploy on Windows without relying on a Linux subsystem (WSL) to make on-premise deployment on a Windows host more accessible. Furthermore, several improvements regarding failover functionality have been done. Lastly, bug fixes regarding resource paths and image versions have been done.
	8	+== ** Announcement - TLS versions deprecated** ==
7	7
	10	+Placeholder for info from Bas
	11	+
	12	+{{info}}Text{{/info}}
	13	+
	14	+== **Announcement - Spring 6** ==
	15	+
	16	+Placeholder for info from Jelle
	17	+
	18	+{{warning}}Text{{/warning}}
	19	+
	20	+== **Infra flow selection** ==
	21	+
	22	+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.
	23	+
	24	+[[image:Main.Images.Release Blog.WebHome@release-216-hack-heaven--infra-flow-comparison.png]]
	25	+
	26	+In edit mode, you can select a new version via the right-click option, which you already use for other flows.
	27	+
	28	+[[image:Main.Images.Release Blog.WebHome@release-216-hack-heaven--infra-flow-selection.png]]
	29	+
	30	+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.
	31	+
	32	+[[image:Main.Images.Release Blog.WebHome@release-216-hack-heaven--context-menu-title.png]]
	33	+
	34	+== **Multiple environments selection** ==
	35	+
	36	+{{warning}}The following is only applicable under the following conditions:
	37	+ * Windows 2022 server
	38	+ * At least one port opened (as a consequence of a hosted web service){{/warning}}
	39	+
	40	+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.
	41	+
	42	+[[image:Main.Images.Release Blog.WebHome@release-216-hack-heaven--multiple-environments.png]]
	43	+
8	8	== **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 displayed close to the edge of the canvas. Expanding the area allows you to select these components, which will become much easier.
9	9
10		-//__On premise Windows machines__//
11		-We can now deploy on Windows without relying on a Linux subsystem (WSL) to make on-premise deployment on a Windows host more accessible.
	48	+//__Improved handling of optionality in JSON on lists__//
	49	+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.
12	12
13		-[[image:Main.Images.Microlearning.WebHome@emagiz-runtime-management--intermediate-runtime-management-deploy-agent.png]]
14		- [[image:Main.Images.Release Blog.WebHome@release-blog-214-system-symphony-windows.png]]
	51	+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.
15	15
16		-//__Adding multiple attributes__//
17		-It is now possible to add multiple existing attributes to an entity at once. This saves time when having to add multiple attributes to an entity.
	53	+//__Loading bar when searching for log entries__//
	54	+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.
18	18
19		-[[image:Main.Images.Release Blog.WebHome@release-blog-214-system-symphony-group-tree-attributes.png]]
	56	+//__Improved feedback when deleting elements from Capture__//
	57	+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.
20	20
21		-//__Monitoring graphs__//
22		-The monitoring graphs can now show data up to the last thirty days.
	59	+//__Enhanced filter options in Manage__//
	60	+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.
23	23
	62	+//__Copy property names from Create__//
	63	+This release unlocks the possibility of easily copying the name of a property placeholder so it can be used while deploying.
	64	+
	65	+//__Improved feedback during migration to the current runtime architecture__//
	66	+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.
	67	+
	68	+//__Block user from making changes to their cloud while another upgrade is still in progress__//
	69	+We now block users from changing their cloud configuration when another upgrade is ongoing.
	70	+
	71	+//__Cron trigger validation__//
	72	+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.
	73	+
24	24	== **Bug Fixes** ==
25		-//__Image versions__//
26		-To keep the overview of releases compact we now have improved the (automatic) deletion behavior in the following way:
27		-* The deletion of releases with deployed container versions will not be blocked anymore.
28		-* Automated release clean up behaviour will also not exclude these releases from deletion.
29		-* Images that belong to deleted releases will be kept if there are other releases that would reuse them, otherwise they will be deleted together with the releases.
	75	+//__Making Edit (and View) the default action when configuring parameters__//
	76	+We have made the Edit (and View) button the default action when configuring parameters in a transformation.
30	30
31		-//__Failover group helptext__//
32		-The helptext of the Group attribute has been improved.
	78	+//__Property configuration pop-up resized__//
	79	+We have resized the property configuration overviews to make the property value better readable.
33	33
34		-[[image:Main.Images.Release Blog.WebHome@release-blog-214-system-symphony-group-helptext.png]]
	81	+//__Alphabetically sorted components in the flow designer__//
	82	+As of this release, we now sort the components alphabetically in the flow designer.
35	35
36		-//__Failover group refresh__//
37		-A new state 'Leader (single node)' has been added in case there is only one node for failover setup. Moreover, a refresh button is added in the Group tab of "Start/Stop Flows" screen. To utilize this, a new runtime image, [[V.2.1.1>>Main.Release Information.Runtime Images.V211||target="blank"]], is needed.
	84	+//__Improved sorting on runtime overview__//
	85	+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.
38	38
39		-[[image:Main.Images.Release Blog.WebHome@release-blog-214-system-symphony-group-refresh.png]]
	87	+//__Improved sorting on catalog overview__//
	88	+As of this release, we now sort the topics in the catalog by name.
40	40
41		-//__Resource paths__//
42		-After migrating a gateway away fom the legacy runtime architecture, the path references in the event processors would be broken. This has been fixed.
	90	+//__Styling fix on rich text editors__//
	91	+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.
43	43
	93	+//__Styling fix on release edit__//
	94	+As of this release, the correct icon (green) will be shown when wanting to add a second API operation under the same "header."
	95	+
	96	+//__Removed false-positive alerts on transformations__//
	97	+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.
	98	+
	99	+//__Event Streaming Graphs - view thirty days back__//
	100	+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.
	101	+
	102	+//__Improved helptext__//
	103	+We have improved various help texts across the portal to indicate better what should be filled in for specific fields.
	104	+
44	44	== **Fancy Forum Answers** ==
45	45
46	46	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:
47	47
48		-* [[Token header dispeared after XSLT extension gateway>>https://my.emagiz.com/p/question/172825635703734925||target="blank"]]
49		-* [[Weird characters such as '¥' and '¶' in eMagiz but not in Postman>>https://my.emagiz.com/p/question/172825635703747839||target="blank"]]
50		-* [[Failed to list files error log>>https://my.emagiz.com/p/question/172825635703747912||target="blank"]]
51		-* [[API new client secret>>https://my.emagiz.com/p/question/172825635703748007||target="blank"]]
	109	+* [[XSD is only partially imported into eMagiz (xmlStat.xsd)>>https://my.emagiz.com/p/question/172825635703773349||target="blank"]]
52	52
53	53	== **Key Takeaways** ==
54	54