Changes for page 216 - Hack Heaven

Summary

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

Details

Page properties

Title

...	...	@@ -1,1 +1,1 @@
1		-216 - Hack Heaven
	1	+204 - Found It

Content

...	...	@@ -1,107 +1,49 @@
1	1	{{container}}
2		-{{container layoutStyle="columns"}}
3		-(((
	2	+{{container layoutStyle="columns"}}(((
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, to select infra flows in a release, and makes it possible to deploy multiple agents to a single machine that adheres to specific conditions. Furthermore, several announcements will be made via this release blog (and other channels) to better prepare your model for upcoming major changes.
7	7
8		-== ** Announcement - TLS versions deprecated** ==
	5	+**Hi there, eMagiz developers!** We have processed additional feedback on the release properties in the last few weeks. On top of that, we have improved the error handling and manageability of our new generation monitoring stack.
9	9
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		-== ** Updated release functionality - Infra flow selection** ==
21		-
22		-This release will include a major update of our release functionality through which you can configure your release. As of now eMagiz will provide you with the option to visually see changes on infra flow level.
23		-
24		-[[image:Main.Images.Release Blog.WebHome@release-216-hack-heaven--infra-flow-comparison.png]]
25		-
26		-When you are in edit mode you can select a new version via the right-click option as you were used to for other flows.
27		-
28		-[[image:Main.Images.Release Blog.WebHome@release-216-hack-heaven--infra-flow-selection.png]]
29		-
30		-On top of that we have added an title to each context menu that specifies the flow type (i.e. 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		-== ** Updated deploy functionality on-premise - Multiple environments selection** ==
35		-
36		-{{warning}}The following is only applicable under the following conditions:
37		- * Windows 2022 server
38		- * Atleast 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 can be activated by the user. With the help of this checkbox you unlock the possibility of stabily 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 they are displayed closed to the edge of the canvas. By expanding the area you can select the selection of these components will become much easier.
47	47
48		-//__Improved handling of optionality in JSON on lists__//
49		-Previously, eMagiz would always create a JSON array if your data model expected a list. This would lead to unexpected and undesirable behavior of the message as empty arrays are not always accepted by external parties. With this release we have changed the way in which we generate the JSON output should there be an empty list in the output. Consequently the empty list will **not** be part of the output anymore as desired.
	9	+//__Improved check on nested property placeholders__//
	10	+To avoid problems when using nested property placeholders in your configuration, we have added additional checks to identify these nested properties as missing if they are indeed missing.
50	50
51		-//__Loading bar when searching for log entries__//
52		-To indicate to the user that eMagiz is still busy retrieving log entries we have now added a loading bar to the log entry overview upon pressing search.
	12	+//__Removed outdated properties when deploying on the new generation architecture stack__//
	13	+We have removed two specific outdated properties from the configuration when deploying on the new generation architecture stack. The properties in question were necessary before connecting to a Kafka cluster but have become obsolete once you migrate.
53	53
54		-//__Improved feedback when deleting elements from Capture__//
55		-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.
	15	+{{warning}}Should you still use the properties called "emagiz.runtime.name" and "emagiz.runtime.environment" **after** successfully migrating the flow in question to the next generation, please get in touch with us before deploying.{{/warning}}
56	56
57		-//__Enhanced filter options in Manage__//
58		-With this release we have added filter options on both the Alerting tab and the Trigger configuration pop-up. This results in being able to filter on Status (Alerting) and Queues, Topics, Recipients, and more (Trigger configuration pop-up) in these places.
	17	+//__Improved performance Manage Dashboards__//
	18	+We have improved the efficiency of retrieving the data shown in the Manage Dashboards for the next-generation architecture.
59	59
60		-//__Copy property names from Create__//
61		-This release unlocks the possibility to easily copy the name of a property placeholder so it can be used whilst deploying.
62		-
63		-//__Improved feedback during migration to the current-runtime architecture__//
64		-We have improved the feedback should you try to migrate the JMS before any other runtime under Create -> Settings.
65		-
66		-//__Block user from making changes to their cloud whilst another upgrade is still in progress__//
67		-We now block the user from making changes to their cloud configuration when another upgrade is still in progress.
68		-
69		-//__Cron trigger validation__//
70		-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.
71		-
72	72	== **Bug Fixes** ==
73		-//__Queue name validation__//
74		-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.
75	75
76		-[[image:Main.Images.Release Blog.WebHome@release-215-tiny-tales-queue-name-validation.png]]
	22	+//__Errors with long stack traces or long message histories will now also show in eMagiz__//
	23	+We have fixed a bug that could cause an error message to be lost between the flow and the Manage phase of eMagiz. This happened in situations where either the stack trace or the message history was very long. To ensure this new functionality is applied to your flows, create a new release and deploy it to your environment(s).
77	77
78		-//__Removal of onramp__//
79		-An issue has been fixed where removing an onramp that was previously linked to a combined entry was impossible in the Create phase.
	25	+//__Moving runtimes from on-premise to the cloud will not result in a broken container anymore__//
	26	+We have fixed a bug that caused specific runtimes to deploy on-premises but later migrated to the cloud, not to start up. By fixing this bug, you have more flexibility in moving containers around when running in a hybrid configuration.
80	80
81		-//__eMagiz login__//
82		-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.
83		-
84	84	== **Fancy Forum Answers** ==
85	85
86	86	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:
87	87
88		-* [[eMagiz Mendix Kafka Module Issue (Mendix 10)>>https://my.emagiz.com/p/question/172825635703748180||target="blank"]]
89		-* [[SFTP + Privatekey not working>>https://my.emagiz.com/p/question/172825635703760538||target="blank"]]
90		-* [[Attribute name is not allowed to start with 'xml'>>https://my.emagiz.com/p/question/172825635703760662||target="blank"]]
91		-* [[How do I change the default content-type from ISO-8859-1 to utf-8>>https://my.emagiz.com/p/question/172825635703760803||target="blank"]]
92		-* [[Preparing Image for <runtime> failed>>https://my.emagiz.com/p/question/172825635703761022||target="blank"]]
	32	+* [[XSLT Extension Gateway with JSON message>>https://my.emagiz.com/p/question/172825635703543227||target="blank"]]
	33	+* [[eMagiz property migration>>https://my.emagiz.com/p/question/172825635703543395||target="blank"]]
93	93
94		-== **Key Takeaways** ==
	35	+== **Key takeaways** ==
95	95
96	96	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:
97	97
98	98	* If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
99	99	* If you have feedback or ideas for us, talk to the Platypus
100		-* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
	41	+* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
101	101	* Clear your browser cache (Ctrl + Shift + Del)
102	102	* Check out the release notes [here]
103	103	* Start thinking about how the license tracker can aid your development
104	104	* Start thinking about major, minor, and patch
	46	+* Upgrade to the latest build number
105	105	* Keep making great integrations
106	106
107	107	Let's stay in touch and till next time!
...	...	@@ -109,11 +109,6 @@
109	109	{{info}}
110	110	~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
111	111
112		-{{/info}}
113		-)))
114		-
115		-(((
116		-{{toc/}}
117		-)))
	54	+~*~* Indicates a next-generation-architecture only feature.
	55	+{{/info}})))((({{toc/}}))){{/container}}
118	118	{{/container}}
119		-{{/container}}