Changes for page 216 - Hack Heaven

Summary

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

Details

Page properties

Title

...	...	@@ -1,1 +1,1 @@
1		-190 - Fast Forward
	1	+216 - Hack Heaven

Content

...	...	@@ -1,131 +1,136 @@
1	1	{{container}}
2		-{{container layoutStyle="columns"}}(((
	2	+{{container layoutStyle="columns"}}
	3	+(((
3	3	[[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]]
4	4
5		-**Hi there, eMagiz developers!** It has been a while since our last deployment on the 9th of December. As a result we have finished up a lot of new improvements to our 3rd generation runtime offering and fixed a variety of annoying bugs as well as some small improvements. This release is characterized by the major steps we took to release several major features on our 3rd generation runtime among which are the queue browser and message redelivery functionality.
	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.
6	6
7		-== **Queue Browser** ==
	8	+== ** Announcement - TLS versions deprecated** ==
8	8
9		-{{warning}}Note that this functionality only works when your JMS server is running on the 3rd generation runtime{{/warning}}
	10	+Placeholder for info from Bas
10	10
11		-To enhance the observability of your integration landscape while running in the 3rd generation runtime architecture we have added a new feature to our Manage phase called the "Queue browser". You can access this functionality via the "Explore" menu option in Manage. With the help of the queue browser you can, as the name suggests, browse your queue.
	12	+{{info}}Text{{/info}}
12	12
13		-To do so, we offer two options within this functionality. We have the Explore function and we have the Wiretap function. When selecting a queue and opting for the Explore option you get a live view of what data is currently present on the queue. When selecting the Wiretap functionality you automatically wiretap your queue and are presented with copies (on a special queue) of your actual message that pass through the queue from the moment you pressed the Wiretap button.
	14	+== **Announcement - Spring 6** ==
14	14
15		-[[image:Main.Images.Release Blog.WebHome@190-release-blog--queue-browser-overview.png]]
	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.
16	16
17		-After selecting the queue and choosing the option eMagiz will show you the list of messages (oldest first) that are currently on the queue (Explore option) or that passed the queue since the moment you activate the option (Wiretap option). For each message you have various options at your disposal.
	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:
	21	+** Simple job launcher (data pipelines)
	22	+** Job explorer (data pipelines)
	23	+** HTTP components message sender (support object)
	24	+** Web service outbound gateway (with a 'message sender' attribute specified)
	25	+** SFTP session factory (support object)
	26	+** API gateways with OAuth2 as security mechanism.
	27	+* 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.
	28	+** 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
	29	+* 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}}
18	18
19		-* Delete the message from the queue (Explore option)
20		- ** This means throwing away live data which can be helpful in a test or acceptance environment where you inadvertedly put a lot of messages on a queue.
21		-* Clear message from the wiretap queue (Wiretap option)
22		- ** Once you are done with the analysis of a certain message in the wiretap functionality you can clear it from the overview so it does not clutter the view anymore
23		-* Refresh messages list (both options)
24		- ** By pressing this button you can refresh the list of messages that are displayed to you. Note that the list is sorted in such a way that the oldest messages are shown first
25		-* Save as test message
26		- ** By pressing this button you can save the message and use it in our flow testing functionality in Create. Note that we link the message to the corresponding flow if we can. Should we not be able to do so we link the message to your model so you can still use it in the flow testing functionality.
27		-* Download
28		- ** By pressing this button you can download the message and use it outside of the tooling should that be needed.
29	29
30		-[[image:Main.Images.Release Blog.WebHome@190-release-blog--queue-browser-explore-overview.png]]
	32	+== **Infra flow selection** ==
31	31
32		-[[image:Main.Images.Release Blog.WebHome@190-release-blog--queue-browser-wiretap-overview.png]]
	34	+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.
33	33
34		-== **Message Redelivery ** ==
	36	+[[image:Main.Images.Release Blog.WebHome@release-216-hack-heaven--infra-flow-comparison.png]]
35	35
36		-{{warning}}Note that this functionality only works when your JMS server is running on the 3rd generation runtime and the functionality is enabled for you environment.{{/warning}}
	38	+In edit mode, you can select a new version via the right-click option, which you already use for other flows.
37	37
38		-[[image:Main.Images.Release Blog.WebHome@190-release-blog--message-redelivery-overview.png]]
	40	+[[image:Main.Images.Release Blog.WebHome@release-216-hack-heaven--infra-flow-selection.png]]
39	39
40		-Just as with our current offering we now offer our message redelivery functionality for our 3rd generation architecture. To enhance the user experience we have placed this functionality as well under the "Explore" option in Manage. When selecting the message redelivery option you will see all messages that are currently in need to be redelivered (as an error occurred).
	42	+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.
41	41
42		-Just as in the current functionality you can select a specific message and retry (or delete) it. The same can be done for all messages at once. Following that you can still see the linked error message as you could before.
	44	+[[image:Main.Images.Release Blog.WebHome@release-216-hack-heaven--context-menu-title.png]]
43	43
44		-On top of that we have added some additional functionality.
	46	+== **Multiple environments selection** ==
45	45
46		-* Search option
47		- ** Original queue name
48		- ** Original message ID (which can be found as a header called jms_messageid in the error message view)
49		-* Save as test message
50		- ** By pressing this button you can save the message and use it in our flow testing functionality in Create.
51		-* Download
52		- ** By pressing this button you can download the message and use it outside of the tooling should that be needed.
	48	+{{warning}}The following is only applicable under the following conditions:
	49	+ * Windows 2022 server
	50	+ * At least one port opened (as a consequence of a hosted web service){{/warning}}
53	53
54		-[[image:Main.Images.Release Blog.WebHome@190-release-blog--message-redelivery-detail-overview.png]]
	52	+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.
55	55
56		-== **3rd generation runtime bolstering** ==
	54	+[[image:Main.Images.Release Blog.WebHome@release-216-hack-heaven--multiple-environments.png]]
57	57
58		-This release will introduce various improvements for our 3rd generation runtime. Below you will find the most noteworthy enhancements we made to the 3rd generation runtime and its interaction with the portal.
	56	+== **Feedback Items** ==
	57	+//__Easier component selection in flow designer__//
	58	+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.
59	59
60		-//__Define memory settings for on-premise runtimes from Deploy Architecture__//
61		-With this release, you are now able to define the memory settings (and therefore the memory limits) of your on-premise runtimes in the same manner as cloud runtimes. In all cases you can now define and change the memory settings via Deploy Architecture. In contrast to how these values are actualized for cloud runtimes you need to create a new release and deploy it to actualize the changes on-premise.
	60	+//__Improved handling of optionality in JSON on lists__//
	61	+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.
62	62
63		-//__Empty runtime feedback when deploying a release (or setting the release as active)__//
64		-To prevent that you are not being able to deploy a release to your environment due to a mismatch between what is in your release and in Deploy Architecture we have now added a feedback pop-up when deploying a release that notifies you for which runtimes there is a mismatch between your release and Deploy Architecture.
	63	+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.
65	65
66		-//__Auto-fill namespaces for SOAP hosted webservices__//
67		-Based on your configuration in Design eMagiz will now auto-fill the namespace when you host a SOAP web service. This avoids any potential problems in validating messages.
	65	+//__Loading bar when searching for log entries__//
	66	+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.
68	68
69		-{{warning}}If you already migrated your JMS flow, you should execute a "Reset" action on the JMS level to get these changes in your model{{/warning}}
	68	+//__Improved feedback when deleting elements from Capture__//
	69	+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.
70	70
71		-//__Removed the ability to add "Debug components" to a flow running in the 3rd generation runtime architecture__//
72		-As of this release, you can no longer add debug components on a flow already migrated to the 3rd generation runtime. This functionality will not work in the 3rd generation runtime and would break your flow.
	71	+//__Enhanced filter options in Manage__//
	72	+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.
73	73
74		-//__Deployment plan is updated correctly when completly migrated to the 3rd generation runtime architecture__//
75		-We have fixed a bug that generated an incorrect default deployment plan once you were fully migrated to the 3rd generation runtime.
	74	+//__Copy property names from Create__//
	75	+This release unlocks the possibility of easily copying the name of a property placeholder so it can be used while deploying.
76	76
77		-//__Correct property generation for Event Streaming flows using the 3rd generation runtime architecture__//
78		-With this release, the properties generated for Event Streaming flows running in the 3rd generation runtime are configured correctly to mimic the ones in the image.
	77	+//__Improved feedback during migration to the current runtime architecture__//
	78	+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.
79	79
80		-//__Added "Reset" functionality__//
81		-With this release, a new functionality has been added for 3rd generation runtimes that allows you to combine several steps into one action, called "Reset runtime." The effect of this action is the same as it currently is in the legacy runtime.
	80	+//__Block user from making changes to their cloud while another upgrade is still in progress__//
	81	+We now block users from changing their cloud configuration when another upgrade is ongoing.
82	82
83		-== **Feedback items ** ==
	83	+//__Cron trigger validation__//
	84	+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.
84	84
85		-We have also solved other feedback items besides the flow designer's critical updates.
	86	+== **Bug Fixes** ==
	87	+//__Making Edit (and View) the default action when configuring parameters__//
	88	+We have made the Edit (and View) button the default action when configuring parameters in a transformation.
86	86
87		-//__Improved naming convention on Store related pages__//
88		-We have improved various display names using the merge functionality within our store offering.
	90	+//__Property configuration pop-up resized__//
	91	+We have resized the property configuration overviews to make the property value better readable.
89	89
90		-//__Update security protocols for our internal architecture__//
91		-Parts of our internal infrastructure (i.e., docs.emagiz.com) have been updated to adhere to the latest security standards.
	93	+//__Alphabetically sorted components in the flow designer__//
	94	+As of this release, we now sort the components alphabetically in the flow designer.
92	92
93		-//__Improved read-only description for "if exists" constructions in Transformations__//
94		-To make it clear what the "if exists" check does while not being in "Start Editing" mode, we have improved the description so users without edit rights or without wanting to enter the "Start Editing" mode can read and interpret what the check does.
	96	+//__Improved sorting on runtime overview__//
	97	+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.
95	95
	99	+//__Improved sorting on catalog overview__//
	100	+As of this release, we now sort the topics in the catalog by name.
96	96
97		-== **Bug fixes ** ==
	102	+//__Styling fix on rich text editors__//
	103	+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	98
99		-//__Decent validation feedback when not filling in the property value__//
100		-We have fixed the validation feedback you get when not filling in the property value using the "Check properties" functionality.
	105	+//__Styling fix on release edit__//
	106	+As of this release, the correct icon (green) will be shown when wanting to add a second API operation under the same "header."
101	101
102		-//__Incorrect resource locations__//
103		-We have fixed several instances where the resource location was not generated correctly in the 3rd generation runtime.
	108	+//__Removed false-positive alerts on transformations__//
	109	+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	104
105		-//__Apply to environment in User Management performance improvement__//
106		-We have improved the performance of updating User Management on your environment. This way, the update functionality is more stable and faster.
	111	+//__Event Streaming Graphs - view thirty days back__//
	112	+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	107
	114	+//__Improved helptext__//
	115	+We have improved various help texts across the portal to indicate better what should be filled in for specific fields.
	116	+
108	108	== **Fancy Forum Answers** ==
109	109
110	110	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:
111	111
112		-* [[Is eMagiz able to read XSD attributes>>https://my.emagiz.com/p/question/172825635703236146||target="blank"]]
113		-* [[Does eMagiz use ActiveMQ?>>https://my.emagiz.com/p/question/172825635703235780||target="blank"]]
114		-* [[Tool for test messages to eMagiz Queues>>https://my.emagiz.com/p/question/172825635703236227||target="blank"]]
115		-* [[How to Remove Cloud Container>>https://my.emagiz.com/p/question/172825635703236460||target="blank"]]
	121	+* [[XSD is only partially imported into eMagiz (xmlStat.xsd)>>https://my.emagiz.com/p/question/172825635703773349||target="blank"]]
116	116
117		-== **Key takeaways** ==
	123	+== **Key Takeaways** ==
118	118
119		-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:
	125	+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:
120	120
121	121	* If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
122	122	* If you have feedback or ideas for us, talk to the Platypus
123		-* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
	129	+* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
124	124	* Clear your browser cache (Ctrl + Shift + Del)
125	125	* Check out the release notes [here]
126	126	* Start thinking about how the license tracker can aid your development
127	127	* Start thinking about major, minor, and patch
128		-* Upgrade to the latest build number
129	129	* Keep making great integrations
130	130
131	131	Let's stay in touch and till next time!
...	...	@@ -133,6 +133,11 @@
133	133	{{info}}
134	134	~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
135	135
136		-~*~* Indicates a GEN3-only feature.
137		-{{/info}})))((({{toc/}}))){{/container}}
	141	+{{/info}}
	142	+)))
	143	+
	144	+(((
	145	+{{toc/}}
	146	+)))
138	138	{{/container}}
	148	+{{/container}}