Changes for page 216 - Hack Heaven

Summary

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

Details

Page properties

Title

...	...	@@ -1,1 +1,1 @@
1		-216 - Hack Heaven
	1	+211 - Log Luminary

Author

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

Content

...	...	@@ -2,113 +2,71 @@
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.
7	7
8		-== ** Announcement - TLS versions deprecated** ==
	6	+**Hi there, eMagiz developers!** In this release, we have done much work to improve our logging and overviews. This should improve the user experience for our platform. Next to this, we have done several minor changes and bug fixes, mainly relating to the Deploy and Manage phase.
9	9
10		-Placeholder for info from Bas
	8	+== **Logging** ==
	9	+//__Missing log entries__//
	10	+We improved crash handling so that log messages clearly show when and why a container failed to start.
11	11
12		-{{info}}Text{{/info}}
	12	+//__Runtime logging__//
	13	+We fixed a bug where no new log messages were showing up, even though they were produced by a container.
13	13
14		-== **Announcement - Spring 6** ==
	15	+//__Deployment execution error message__//
	16	+In some cases when a machine type step in the deployment plan execution errors, the portal may give an error when trying to display the error message. This has been fixed by now showing a generic error in the deployment plan and logging the full error in the Deploy history. The Deploy history will show a summary of the error and show the full error message in a new pop-up.
15	15
16		-Placeholder for info from Jelle
	18	+== **Overviews** ==
17	17
18		-{{warning}}Text{{/warning}}
	20	+//__Runtime overview__//
	21	+We added a new overview in the Deploy phase, called 'Runtime Overview', which shows the information of all runtimes on running machines.
19	19
20		-== **Infra flow selection** ==
	23	+[[image:Main.Images.Release Blog.WebHome@release-blog-211-runtime-overview.png]]
21	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.
	25	+//__Missing properties overview__//
	26	+The missing properties overview has been updated to show the runtimes and flow versions of missing property values.
23	23
24		-[[image:Main.Images.Release Blog.WebHome@release-216-hack-heaven--infra-flow-comparison.png]]
	28	+[[image:Main.Images.Release Blog.WebHome@release-blog-211-missing-properties-overview.png]]
25	25
26		-In edit mode, you can select a new version via the right-click option, which you already use for other flows.
	30	+//__Runtime restart or redeploy overview__//
	31	+Before executing the deployment plan to deploy machines, a pop-up will be shown with a list of the affected runtimes.
27	27
28		-[[image:Main.Images.Release Blog.WebHome@release-216-hack-heaven--infra-flow-selection.png]]
	33	+[[image:Main.Images.Release Blog.WebHome@release-blog-211-restarted-redeployed-runtimes.jpg]]
29	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		-
44	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 displayed close to the edge of the canvas. Expanding the area allows you to select these components, which will become much easier.
47	47
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.
	37	+//__Breaking changes pop-up__//
	38	+Pending changes that have a high risk level are now shown in red bold in the pop up that appears after clicking 'Apply to environment'.
50	50
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.
	40	+[[image:Main.Images.Release Blog.WebHome@release-blog-211-breaking-changes.png]]
52	52
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.
	42	+//__External recipients emailaddress__//
	43	+The overview of external recipients has been updated. External recipients are now created on a model level, instead of comma separated list. This means that you can add them to your environment directly, like internal users.
55	55
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.
	45	+//__Broker queue metrics dashboards__//
	46	+It is now possible to select the MQTT broker in the queue metrics dashboards.
58	58
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.
	48	+//__Runtime image version__//
	49	+The version of runtime images used to prepare your containers for deployments will be the same across all environments. This holds for releases that are deployed and promoted to a next environment.
61	61
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	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		-
74	74	== **Bug Fixes** ==
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.
77	77
78		-//__Property configuration pop-up resized__//
79		-We have resized the property configuration overviews to make the property value better readable.
	54	+//__Message throughput__//
	55	+The message throughput graph in the Manage phase will now show the correct data, independent from the selected time internal. Before, this graph would not show any data in some cases.
80	80
81		-//__Alphabetically sorted components in the flow designer__//
82		-As of this release, we now sort the components alphabetically in the flow designer.
	57	+//__Cloud template upgrade incorrect rollback__//
	58	+An issue has been fixed where a cloud template upgrade would be rolled back incorrectly due to failed runtime checks.
83	83
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.
	60	+//__Next generation block__//
	61	+Apply to environment will now be blocked when trying to deploy Gen3 runtimes on a Gen2 model.
86	86
87		-//__Improved sorting on catalog overview__//
88		-As of this release, we now sort the topics in the catalog by name.
89		-
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.
92		-
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		-
105	105	== **Fancy Forum Answers** ==
106	106
107	107	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:
108	108
109		-* [[XSD is only partially imported into eMagiz (xmlStat.xsd)>>https://my.emagiz.com/p/question/172825635703773349||target="blank"]]
	67	+* [[Save header as class 'long'>>https://my.emagiz.com/p/question/172825635703683851||target="blank"]]
110	110
111		-== **Key Takeaways** ==
	69	+== **Key takeaways** ==
112	112
113	113	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:
114	114