Changes for page 216 - Hack Heaven

Summary

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

Details

Page properties

Title

...	...	@@ -1,1 +1,1 @@
1		-192 - Small Step
	1	+216 - Hack Heaven

Content

...	...	@@ -1,70 +1,99 @@
1	1	{{container}}
2		-{{container layoutStyle="columns"}}(((
	2	+{{container layoutStyle="columns"}}
	3	+(((
3	3	[[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.
4	4
5		-**Hi there, eMagiz developers!** In the last couple of weeks, we worked hard on building several essential things that will be released later this Q. On top of that, we finished additional features for our 3rd generation runtime that give you chirurgical precision when doing maintenance on a model. Among the other features, we have a new event streaming graph and general updates to our platform.
	8	+== ** Announcement - TLS 1.0 and 1.1 deprecated** ==
6	6
7		-== **Start/Stop Flows** ~*~* ==
	10	+Placeholder for info from Bas
8	8
9		-{{warning}}Note that depending on the alert, this functionality will only work when your JMS server is running on the 3rd generation runtime{{/warning}}
	12	+{{info}}Text{{/info}}
10	10
11		-To enhance your options when running into problems or when maintaining your solution in a Production environment, we have added a new feature to our Deploy phase called "Start/Stop Flows." You can access this functionality via the "Deploy Architecture" overview in Deploy. On the runtime level, you can open the context menu and select the "Start/Stop Flows" option.
	14	+== **Announcement - Spring 6** ==
12	12
13		-[[image:Main.Images.Release Blog.WebHome@192-release-blog--start-stop-flows-context-menu.png]]
	16	+Placeholder for info from Jelle
14	14
15		-After selecting the option, eMagiz will open a pop-up where you can stop and start the starting point of each flow deployed on that runtime. This effect is that the flow will process no new messages, but the flow will still process all remaining messages after stopping the flow. To prevent a flow, you select a flow and press the Stop button. To start it again, press Start.
	18	+{{warning}}Text{{/warning}}
16	16
17		-[[image:Main.Images.Release Blog.WebHome@192-release-blog--start-stop-flows-pop-up-menu.png]]
	20	+== ** Updated release functionality - Infra flow selection** ==
18	18
19		-{{info}}Only in "Start Editing" mode can you start and stop specific flows{{/info}}
	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.
20	20
21		-== **Manage overview Event Streaming** ~*~* ==
	24	+[[image:Main.Images.Release Blog.WebHome@release-216-hack-heaven--infra-flow-comparison.png]]
22	22
23		-To enhance the observability of your event streaming solution while running in the 3rd generation runtime architecture, we have added a new feature to our Manage phase called "Event streaming statistics." You can access this functionality via the "Monitoring" menu in Manage. Then, you can see metadata information on all your topics by clicking on the "Event streaming statistics" overview. Among others, you can see whether data is consumed, on which topic much data is produced, and whether consumers are lagging in consuming data.
	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.
24	24
25		-[[image:Main.Images.Release Blog.WebHome@192-release-blog--event-streaming-overview-manage.png]]
	28	+[[image:Main.Images.Release Blog.WebHome@release-216-hack-heaven--infra-flow-selection.png]]
26	26
27		-== **Feedback items ** ==
	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.
28	28
29		-We have also solved other feedback items besides the flow designer's critical updates.
	32	+[[image:Main.Images.Release Blog.WebHome@release-216-hack-heaven--context-menu-title.png]]
30	30
31		-//__Topic configuration calculation__//
32		-With this release, we have simplified the configuration of settings on the topic level to enforce certain best practices within the portal and simultaneously make it easier to configure topics.
	34	+== ** Updated deploy functionality on-premise - Multiple environments selection** ==
33	33
34		-//__Make preparation step in deployment plan visible__//
35		-For deployment on the 3rd generation runtime to work, the portal needs some preparation work. We have now made this step explicit and part of the deployment plan.
	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}}
36	36
37		-{{warning}}Make sure to update your deployment plan accordingly to ensure that the preparation step is not forgotten{{/warning}}
	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.
38	38
39		-//__3rd generation runtime debugger feedback__//
40		-We have improved the user experience of the 3rd generation runtime debugger with this release by solving various feedback items we noticed in the first adoptions of the functionality.
	42	+[[image:Main.Images.Release Blog.WebHome@release-216-hack-heaven--multiple-environments.png]]
41	41
42		-//__No "Shift key" needed anymore to select multiple items in the flow designer__//
43		-As of now, you do not have to hold your "Shift key" when you want to select multiple items in the flow designer. This will make it easier to select parts of flows.
	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.
44	44
45		-//__User Management synchronization now happens in one step__//
46		-With this release, we have updated the synchronization process between Design and Deploy concerning User Management. When you press the "Transfer from design" button, both Users and Roles will be synchronized.
	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.
47	47
	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.
	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.
	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.
	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	+
	64	+== **Bug Fixes** ==
	65	+//__Queue name validation__//
	66	+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.
	67	+
	68	+[[image:Main.Images.Release Blog.WebHome@release-215-tiny-tales-queue-name-validation.png]]
	69	+
	70	+//__Removal of onramp__//
	71	+An issue has been fixed where removing an onramp that was previously linked to a combined entry was impossible in the Create phase.
	72	+
	73	+//__eMagiz login__//
	74	+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.
	75	+
48	48	== **Fancy Forum Answers** ==
49	49
50	50	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:
51	51
52		-* [[Change property with new release in generation 3 runtimes>>https://my.emagiz.com/p/question/172825635703274441||target="blank"]]
53		-* [[Mapped request header "Accept">>https://my.emagiz.com/p/question/172825635703300348||target="blank"]]
54		-* [[OAUTH2.0 Advanced Options 'Resource'>>https://my.emagiz.com/p/question/172825635703300155||target="blank"]]
	80	+* [[eMagiz Mendix Kafka Module Issue (Mendix 10)>>https://my.emagiz.com/p/question/172825635703748180||target="blank"]]
	81	+* [[SFTP + Privatekey not working>>https://my.emagiz.com/p/question/172825635703760538||target="blank"]]
	82	+* [[Attribute name is not allowed to start with 'xml'>>https://my.emagiz.com/p/question/172825635703760662||target="blank"]]
	83	+* [[How do I change the default content-type from ISO-8859-1 to utf-8>>https://my.emagiz.com/p/question/172825635703760803||target="blank"]]
	84	+* [[Preparing Image for <runtime> failed>>https://my.emagiz.com/p/question/172825635703761022||target="blank"]]
55	55
56		-== **Key takeaways** ==
	86	+== **Key Takeaways** ==
57	57
58		-Thanks to all that helped build and those who tested and gave feedback to improve the product. To end this post, here are some key takeaways for you:
	88	+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:
59	59
60	60	* If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
61	61	* If you have feedback or ideas for us, talk to the Platypus
62		-* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
	92	+* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
63	63	* Clear your browser cache (Ctrl + Shift + Del)
64	64	* Check out the release notes [here]
65	65	* Start thinking about how the license tracker can aid your development
66	66	* Start thinking about major, minor, and patch
67		-* Upgrade to the latest build number
68	68	* Keep making great integrations
69	69
70	70	Let's stay in touch and till next time!
...	...	@@ -72,6 +72,11 @@
72	72	{{info}}
73	73	~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
74	74
75		-~*~* Indicates a GEN3-only feature.
76		-{{/info}})))((({{toc/}}))){{/container}}
	104	+{{/info}}
	105	+)))
	106	+
	107	+(((
	108	+{{toc/}}
	109	+)))
77	77	{{/container}}
	111	+{{/container}}