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,137 +1,138 @@
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 and some minor enhancements. This release is characterized by the significant steps we took to release several major features on our 3rd generation runtime, including 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	+As eMagiz, we continuously validate our best practices configuration on security to the industry-wide standards in the fields of security to uphold our reputation as a reliable and secure integration platform. As a result of our latest evaluation, we decided to follow the industry-wide standard to **not** support the following TLS versions anymore in our **[[current runtime>>doc:Main.eMagiz Academy.Fundamentals.fundamental-runtime-generation3||target="blank"]]** architecture for outgoing connections from eMagiz to external systems as of April 11th, 2024.
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 in Manage. Then, with the help of the queue browser, you can browse your queue as the name suggests.
	12	+* TLSv1.0
	13	+* TLSv1.1
12	12
13		-To do so, we offer two options within this functionality. First, 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 the current data in the queue. Then, when choosing the Wiretap functionality, you automatically wiretap your queue and are presented with copies (on a particular queue) of your actual message that passes through the queue from the moment you press the Wiretap button.
	15	+{{info}}Should you have concerns whether any of the external systems called from your eMagiz model only support the older TLS versions we suggest checking this via either OpenSSL or SOAP UI by calling the endpoint.{{/info}}
14	14
15		-[[image:Main.Images.Release Blog.WebHome@190-release-blog--queue-browser-overview.png]]
	17	+== **Announcement - Spring 6** ==
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.
	19	+We will release a major version of our [[current runtime>>doc:Main.eMagiz Academy.Fundamentals.fundamental-runtime-generation3||target="blank"]] base image for all our clients running on the **[[current runtime>>doc:Main.eMagiz Academy.Fundamentals.fundamental-runtime-generation3||target="blank"]]** architecture in our release that will be released on April 11th, 2024. 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.
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 inadvertently put many messages on a queue.
21		-* Clear message from the wiretap queue (Wiretap option)
22		- ** Once you are done with the analysis of a specific 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 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.
	21	+{{warning}}
	22	+* 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 changed. These new flow versions must be included in the subsequent release. Having your release already on the **latest** flow versions makes this less affecting.
	23	+* To help you identify which flow versions are essential here, you can consider all flows that contain any of the following components:
	24	+** Simple job launcher (data pipelines)
	25	+** Job explorer (data pipelines)
	26	+** HTTP components message sender (support object)
	27	+** Web service outbound gateway (with a 'message sender' attribute specified)
	28	+** SFTP session factory (support object)
	29	+** API gateways with OAuth2 as security mechanism.
	30	+* We recommend identifying flows with (advanced) custom Groovy scripts. As our Java and Spring versions change, 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.
	31	+** Additionally, the Groovy version has been moved from 3.0.19 to 4.0.18. These changes may affect your scripts as well. [[These release notes >>https://groovy-lang.org/releasenotes/groovy-4.0.html||target="blank"]] will specify the changes in more detail.
	32	+* 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}}
29	29
30		-[[image:Main.Images.Release Blog.WebHome@190-release-blog--queue-browser-explore-overview.png]]
	34	+== **Infra flow selection** ==
31	31
32		-[[image:Main.Images.Release Blog.WebHome@190-release-blog--queue-browser-wiretap-overview.png]]
	36	+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		-{{info}}The following restrictions apply to this functionality:
35		- * Message payload in excess of 100KB are not shown in the queue browser as they constitute a "large message"
36		- * The wiretap functionality works for a period of five minutes in which you can use the refresh button to see new messages coming in.
37		- ** After five minutes the wiretap functionality will be shutdown automatically under water.
38		- ** To see new messages after the five minutes you will have to access the wiretap functionality again from scratch.{{/info}}
	38	+[[image:Main.Images.Release Blog.WebHome@release-216-hack-heaven--infra-flow-comparison.png]]
39	39
40		-== **Message Redelivery ** ~*~* ==
	40	+In edit mode, you can select a new version via the right-click option, which you already use for other flows.
41	41
42		-{{warning}}Note that this functionality only works when your JMS server is running on the 3rd generation runtime, and the functionality is enabled for your environment.{{/warning}}
	42	+[[image:Main.Images.Release Blog.WebHome@release-216-hack-heaven--infra-flow-selection.png]]
43	43
44		-[[image:Main.Images.Release Blog.WebHome@190-release-blog--message-redelivery-overview.png]]
	44	+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.
45	45
46		-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 under the "Explore" option in Manage. When selecting the message redelivery option, you will see all messages that currently need to be redelivered (as an error occurred).
	46	+[[image:Main.Images.Release Blog.WebHome@release-216-hack-heaven--context-menu-title.png]]
47	47
48		-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.
	48	+== **Multiple environments selection** ==
49	49
50		-On top of that, we have added some additional functionality.
	50	+{{warning}}The following is only applicable under the following conditions:
	51	+ * Windows 2022 server
	52	+ * At least one port opened (as a consequence of a hosted web service){{/warning}}
51	51
52		-* Search option
53		- ** Original queue name
54		- ** Original message ID (which can be found as a header called jms_messageid in the error message view)
55		-* Save as test message
56		- ** By pressing this button, you can save the message and use it in our flow testing functionality in Create.
57		-* Download
58		- ** By pressing this button, you can download the message and use it outside of the tooling should that be needed.
	54	+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.
59	59
60		-[[image:Main.Images.Release Blog.WebHome@190-release-blog--message-redelivery-detail-overview.png]]
	56	+[[image:Main.Images.Release Blog.WebHome@release-216-hack-heaven--multiple-environments.png]]
61	61
62		-== **3rd generation runtime bolstering** ==
	58	+== **Feedback Items** ==
	59	+//__Easier component selection in flow designer__//
	60	+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.
63	63
64		-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.
	62	+//__Improved handling of optionality in JSON on lists__//
	63	+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.
65	65
66		-//__Define memory settings for on-premise runtimes from Deploy Architecture__//
67		-With this release, you can now 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.
	65	+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.
68	68
69		-//__Empty runtime feedback when deploying a release (or setting the release as active)__//
70		-To prevent you are not being able to deploy a release to your environment due to a mismatch between what is in your release and 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.
	67	+//__Loading bar when searching for log entries__//
	68	+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.
71	71
72		-//__Auto-fill namespaces for SOAP hosted webservices__//
73		-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.
	70	+//__Improved feedback when deleting elements from Capture__//
	71	+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.
74	74
75		-//__Updated H2 database setting__//
76		-As of this release, we have improved the configuration of our H2 databases used within eMagiz. This new setting will ensure the runtime controls when the H2 database is shut down.
	73	+//__Enhanced filter options in Manage__//
	74	+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.
77	77
78		-{{warning}}If you already migrated your runtime, you should execute a "Reset" action on the infra flow to get these changes in your model{{/warning}}
	76	+//__Copy property names from Create__//
	77	+This release unlocks the possibility of easily copying the name of a property placeholder so it can be used while deploying.
79	79
80		-//__Runtime settings option added to context menu on runtime level Deploy Architecture__//
81		-As a replacement for the current HTTP settings context menu, we added a new menu item called runtime settings. On top of being able to configure your HTTP settings (which you need to define for a hosted web service), you now also can define whether the control bus needs to work for this runtime.
	79	+//__Improved feedback during migration to the current runtime architecture__//
	80	+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.
82	82
83		-//__Deploy Agent option added to context menu on machine level Deploy Architecture__//
84		-With this release, we have added a context menu item allowing users to deploy the agent needed to run your 3rd generation architecture on-premise. For more information on installing this, please check out this [[microlearning>>doc:Main.eMagiz Academy.Microlearnings.Expert Level.Solution Architecture.expert-solution-architecture-onpremises-installguide.WebHome||target="blank"]]
	82	+//__Block user from making changes to their cloud while another upgrade is still in progress__//
	83	+We now block users from changing their cloud configuration when another upgrade is ongoing.
85	85
86		-//__Performance improvement creating a release__//
87		-With this release, we have improved the performance of creating a release.
	85	+//__Cron trigger validation__//
	86	+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.
88	88
89		-== **Feedback items ** ==
	88	+== **Bug Fixes** ==
	89	+//__Making Edit (and View) the default action when configuring parameters__//
	90	+We have made the Edit (and View) button the default action when configuring parameters in a transformation.
90	90
91		-We have also solved other feedback items besides the flow designer's critical updates.
	92	+//__Property configuration pop-up resized__//
	93	+We have resized the property configuration overviews to make the property value better readable.
92	92
93		-//__Sensitive information stored in properties is masked __//
94		-We have made how we display sensitive information across the portal similar for various parts of the portal.
	95	+//__Alphabetically sorted components in the flow designer__//
	96	+As of this release, we now sort the components alphabetically in the flow designer.
95	95
96		-//__Importing "Private" store content to which you do not have access__//
97		-We have improved the user feedback a user will get when trying to import a "Private" store item unavailable to the user.
	98	+//__Improved sorting on runtime overview__//
	99	+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.
98	98
	101	+//__Improved sorting on catalog overview__//
	102	+As of this release, we now sort the topics in the catalog by name.
99	99
100		-== **Bug fixes ** ==
	104	+//__Styling fix on rich text editors__//
	105	+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.
101	101
102		-//__Fix the possibility that allowed you to break the system message when dealing with the "Order matters" functionality__//
103		-We have fixed the possibility you had that would break your system message upon validating it in Create when using the "Order matters" functionality.
	107	+//__Styling fix on release edit__//
	108	+As of this release, the correct icon (green) will be shown when wanting to add a second API operation under the same "header."
104	104
105		-//__Synchronization of Event Streaming topic states__//
106		-We fixed synchronization issues that could occur when several changes were executed on a model that uses a fast amount of topics.
	110	+//__Removed false-positive alerts on transformations__//
	111	+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.
107	107
108		-//__Copy and paste default support objects__//
109		-With this release, you can now copy and paste components without worrying that additional support objects already existing in your target flow are copied over and over into the same flow.
	113	+//__Event Streaming Graphs - view thirty days back__//
	114	+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.
110	110
111		-//__Fix editability of properties when importing store items__//
112		-With this release, you can once again change property names upon importing a store item.
	116	+//__Improved helptext__//
	117	+We have improved various help texts across the portal to indicate better what should be filled in for specific fields.
113	113
114	114	== **Fancy Forum Answers** ==
115	115
116	116	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:
117	117
118		-* [[Can I change my 2FA secret, eg. move to another authenticator?>>https://my.emagiz.com/p/question/172825635703274697||target="blank"]]
119		-* [[Webrequest header 'SOAPAction'>>https://my.emagiz.com/p/question/172825635703274615||target="blank"]]
120		-* [[XPathException on XPATH router>>https://my.emagiz.com/p/question/172825635703274295||target="blank"]]
121		-* [[Change property with new release in generation 3 runtimes>>https://my.emagiz.com/p/question/172825635703274441||target="blank"]]
	123	+* [[XSD is only partially imported into eMagiz (xmlStat.xsd)>>https://my.emagiz.com/p/question/172825635703773349||target="blank"]]
122	122
123		-== **Key takeaways** ==
	125	+== **Key Takeaways** ==
124	124
125		-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:
	127	+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:
126	126
127	127	* If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
128	128	* If you have feedback or ideas for us, talk to the Platypus
129		-* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
	131	+* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
130	130	* Clear your browser cache (Ctrl + Shift + Del)
131	131	* Check out the release notes [here]
132	132	* Start thinking about how the license tracker can aid your development
133	133	* Start thinking about major, minor, and patch
134		-* Upgrade to the latest build number
135	135	* Keep making great integrations
136	136
137	137	Let's stay in touch and till next time!
...	...	@@ -139,6 +139,11 @@
139	139	{{info}}
140	140	~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
141	141
142		-~*~* Indicates a GEN3-only feature.
143		-{{/info}})))((({{toc/}}))){{/container}}
	143	+{{/info}}
	144	+)))
	145	+
	146	+(((
	147	+{{toc/}}
	148	+)))
144	144	{{/container}}
	150	+{{/container}}