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	+205 - World Explorers

Content

...	...	@@ -1,125 +1,53 @@
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	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.
	5	+**Hi there, eMagiz developers!** We have processed additional feedback on the Manage phase to ensure you can more easily create overviews of your statistics, displaying all information correctly and improving the migration process to the next-generation architecture in the Create phase slightly. On top of that, we have improved the scalability of our new generation monitoring stack and the alerting structure. We will also release a new cloud template for our next-generation infrastructure to comply with technical requirements from our cloud provider.
7	7
8		-== ** Announcement - TLS versions deprecated** ==
	7	+== ** Mandatory Cloud Template Upgrade - Next-generation models ** ==
9	9
10		-Placeholder for info from Bas
	9	+As can be seen on our [[status page>>https://status.emagiz.com/incidents/dbh6g9w3ks7q||target="blank"]], we will release a new cloud template for our next-generation models (both single and double lane) that will change a configuration in these templates to comply with technical and operational requirements from our cloud provider. The announcement of the status page itself holds more detail for those to whom it pertains.
11	11
12		-{{info}}Text{{/info}}
13		-
14		-== **Announcement - Spring 6** ==
15		-
16		-We expect to release a major version of our current runtime base image for all our clients running on the **current runtime** architecture in the next release. 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.
17		-
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 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
20		-* To help you identify which flow versions are essential 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 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.
28		-** 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.
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}}
30		-
31		-== **Infra flow selection** ==
32		-
33		-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.
34		-
35		-[[image:Main.Images.Release Blog.WebHome@release-216-hack-heaven--infra-flow-comparison.png]]
36		-
37		-In edit mode, you can select a new version via the right-click option, which you already use for other flows.
38		-
39		-[[image:Main.Images.Release Blog.WebHome@release-216-hack-heaven--infra-flow-selection.png]]
40		-
41		-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.
42		-
43		-[[image:Main.Images.Release Blog.WebHome@release-216-hack-heaven--context-menu-title.png]]
44		-
45		-== **Multiple environments selection** ==
46		-
47		-{{warning}}The following is only applicable under the following conditions:
48		- * Windows 2022 server
49		- * At least one port opened (as a consequence of a hosted web service){{/warning}}
50		-
51		-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.
52		-
53		-[[image:Main.Images.Release Blog.WebHome@release-216-hack-heaven--multiple-environments.png]]
54		-
55	55	== **Feedback Items** ==
56		-//__Easier component selection in flow designer__//
57		-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.
58	58
59		-//__Improved handling of optionality in JSON on lists__//
60		-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.
	13	+//__Improved Validation when migrating to the next-generation architecture__//
	14	+To improve the migration process to the next-generation architecture, we now show a list of all reported problems, allowing the user to resolve them before migrating to the next-generation architecture.
61	61
62		-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.
	16	+{{info}}Note that when no problem is found, the migration process of that runtime will start automatically.{{/info}}
63	63
64		-//__Loading bar when searching for log entries__//
65		-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.
	18	+//__Improved HTTP Statistics__//
	19	+To improve the filtering and refresh functionality we offer on this overview, we have made several changes in this release that will improve the behavior of this overview.
66	66
67		-//__Improved feedback when deleting elements from Capture__//
68		-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.
	21	+//__Show values on the runtime level in Deploy Architecture__//
	22	+We have improved the values shown on the runtime (i.e., container) level in Deploy Architecture so you can better assess whether the memory configuration is still suitable for your deployed solution.
69	69
70		-//__Enhanced filter options in Manage__//
71		-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.
	24	+{{info}}To get to the values we use different calculation methods per type of runtime, as certain runtime types have various reasons for existence.
	25	+* JMS - The number of queues in the active release.
	26	+* Messaging Container - The number of messaging integrations in the active release.
	27	+* Messaging Connector - The number of messaging integrations related to this system in the active release.
	28	+* API Gateway Container - The number of operations in the active release.
	29	+* Event Streaming Container - The number of event processors in the active release.
72	72
73		-//__Copy property names from Create__//
74		-This release unlocks the possibility of easily copying the name of a property placeholder so it can be used while deploying.
	31	+There might be multi-tenant and multi-runtime situations that do not always get to the exact number; however, this is a great improvement compared to showing no values.{{/info}}
75	75
76		-//__Improved feedback during migration to the current runtime architecture__//
77		-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.
78		-
79		-//__Block user from making changes to their cloud while another upgrade is still in progress__//
80		-We now block users from changing their cloud configuration when another upgrade is ongoing.
81		-
82		-//__Cron trigger validation__//
83		-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		-
85	85	== **Bug Fixes** ==
86		-//__Making Edit (and View) the default action when configuring parameters__//
87		-We have made the Edit (and View) button the default action when configuring parameters in a transformation.
88	88
89		-//__Property configuration pop-up resized__//
90		-We have resized the property configuration overviews to make the property value better readable.
	35	+//__Gain the ability again to configure certificates in Deploy Architecture again__//
	36	+In restricting the configuration options on the certificate level in one of our latter releases, it became impossible for normal users to add and edit certificates within Deploy Architecture. To resolve this problem we have now released a fix to resolve this issue, giving people the ability again to add and edit certificates under Deploy Architecture.
91	91
92		-//__Alphabetically sorted components in the flow designer__//
93		-As of this release, we now sort the components alphabetically in the flow designer.
	38	+//__Ensure that differing container configurations deploy the correct configuration__//
	39	+When you run in a multi-runtime configuration and change the actual flows that need to run on container A vs. container B, it happened before that all flows were still being deployed on all runtimes. With this release, we will feed this information correctly to our infrastructure to ensure the correct and configured flows are deployed on the proper containers.
94	94
95		-//__Improved sorting on runtime overview__//
96		-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.
	41	+//__Remove queurying options in Manage__//
	42	+To avoid errors and loading problems when analyzing your statistics in Manage, we have removed the option to select a default time range spanning more than seven days. This is to guarantee the stability of the solution and to avoid users getting unnecessary errors.
97	97
98		-//__Improved sorting on catalog overview__//
99		-As of this release, we now sort the topics in the catalog by name.
100		-
101		-//__Styling fix on rich text editors__//
102		-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.
103		-
104		-//__Styling fix on release edit__//
105		-As of this release, the correct icon (green) will be shown when wanting to add a second API operation under the same "header."
106		-
107		-//__Removed false-positive alerts on transformations__//
108		-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.
109		-
110		-//__Event Streaming Graphs - view thirty days back__//
111		-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.
112		-
113		-//__Improved helptext__//
114		-We have improved various help texts across the portal to indicate better what should be filled in for specific fields.
115		-
116	116	== **Fancy Forum Answers** ==
117	117
118	118	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:
119	119
120		-* [[XSD is only partially imported into eMagiz (xmlStat.xsd)>>https://my.emagiz.com/p/question/172825635703773349||target="blank"]]
	48	+* [[Getting files from subfolders (FTP)>>https://my.emagiz.com/p/question/172825635703568575||target="blank"]]
121	121
122		-== **Key Takeaways** ==
	50	+== **Key takeaways** ==
123	123
124	124	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:
125	125
...	...	@@ -130,6 +130,7 @@
130	130	* Check out the release notes [here]
131	131	* Start thinking about how the license tracker can aid your development
132	132	* Start thinking about major, minor, and patch
	61	+* Upgrade to the latest build number
133	133	* Keep making great integrations
134	134
135	135	Let's stay in touch and till next time!
...	...	@@ -137,11 +137,6 @@
137	137	{{info}}
138	138	~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
139	139
140		-{{/info}}
141		-)))
142		-
143		-(((
144		-{{toc/}}
145		-)))
	69	+~*~* Indicates a next-generation-architecture only feature.
	70	+{{/info}})))((({{toc/}}))){{/container}}
146	146	{{/container}}
147		-{{/container}}