Changes for page 216 - Hack Heaven

Summary

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

Details

Page properties

Title

...	...	@@ -1,1 +1,1 @@
1		-196 - The Last Post
	1	+216 - Hack Heaven

Content

...	...	@@ -1,81 +1,130 @@
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!** In the last few weeks, we have work hard on improving our next generation architecture and introduced the "live" mode within our flow testing functionality. Furthermore there are loads of smaller feedback items and bugs that have been resolved with this release. So without further ado let us dive into all we have to offer.
	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		-== **"Live" mode on flow testing** ==
	8	+== ** Announcement - TLS versions deprecated** ==
8	8
9		-With this release we bring an improved version of the flow testing functionality. As of now you will have the option to switch between "live" and "mock" mode will running a flow test. The "mock" mode is the mode you are used to from us. In this mode all external communication is mocked by the system and only the functional process can be tested.
	10	+Placeholder for info from Bas
10	10
11		-By switching to "live" mode you can not only test the functional process but also the communication to the external system. You can do so by entering the "edit" mode of the flow test and toggle between "mock" and "live" mode. When doing so eMagiz will show you the following pop-up stressing the consequences of your actions.
	12	+{{info}}Text{{/info}}
12	12
13		-[[image:Main.Images.Release Blog.WebHome@196-release-blog--live-flow-testing-pop-up.png]]
	14	+== **Announcement - Spring 6** ==
14	14
15		-Once confirmed you will see that the user interface now indicates that the endpoint is in "live" mode.
	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		-[[image:Main.Images.Release Blog.WebHome@196-release-blog--live-flow-testing-result.png]]
	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: Simple job launcher (data pipelines), Job explorer (data pipelines), HTTP components message sender (support object), Web service outbound gateway (with a 'message sender' attribute specified), SFTP session factory (support object), API gateways with OAuth2 as security mechanism.
	21	+* 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.
	22	+* 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
	23	+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		-{{info}}* The following restrictions apply for this functionality
20		- ** "Live" mode can only be activated on HTTP outbound gateway components
21		- ** "Live" mode can **not** be active when you want to use the flow test as an "automated" test{{/info}}
22	22
23		-== **3rd generation improvements** ==
	26	+== **Infra flow selection** ==
24	24
25		-//__Event Streaming statistics completion__//
26		-In this release, we have updated the retrieval of data to ensure that for all models, all environments and all topics this data can be shown to the user so they can properly monitor the environment.
	28	+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.
27	27
28		-//__Deployments on next generation architecture__//
29		-This release fixes several smaller bugs and adds several improvements to the deployment process of the next generation architecture.
	30	+[[image:Main.Images.Release Blog.WebHome@release-216-hack-heaven--infra-flow-comparison.png]]
30	30
31		-//__Clean queues option__//
32		-This release introduces an option for **admins** to clean queues that remained after a migration towards the next generation runtime architecture. This will make the overview of which queues are "problematic" a much more realistic overview.
	32	+In edit mode, you can select a new version via the right-click option, which you already use for other flows.
33	33
34		-== **Feedback items ** ==
	34	+[[image:Main.Images.Release Blog.WebHome@release-216-hack-heaven--infra-flow-selection.png]]
35	35
36		-//__On-premise containers are started upon slot wakeup__//
37		-With this release, we have added additional functionality to models running in the next generation runtime architecture. With this improvement all on-premise containers are stopped when the cloud slot goes to sleep and are woken up once the slot is woken up in the morning.
	36	+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.
38	38
39		-//__Resource path is shown to the user__//
40		-You can now, without downloading, see the resource path of a resource by viewing the metadata of the resource. You can do so by pressing the "eye" icon to view this information.
	38	+[[image:Main.Images.Release Blog.WebHome@release-216-hack-heaven--context-menu-title.png]]
41	41
42		-//__Flow designer improvements__//
43		-With this release various improvements have been made to the flow designer. Among others we have improved the overview of what an "unused resource" is. You now have the option to define certain resources that are used but cannot be auto-detected by eMagiz to be an "used" resource to avoid confusion.
	40	+== **Multiple environments selection** ==
44	44
45		-//__Improved capabilities of a company contact__//
46		-With this release we have improved the capabilities of a company contact. As of now you can also add users to models belonging to subcompanies below your the company to which you are the company contact.
	42	+{{warning}}The following is only applicable under the following conditions:
	43	+ * Windows 2022 server
	44	+ * At least one port opened (as a consequence of a hosted web service){{/warning}}
47	47
48		-== **Bug fixes ** ==
	46	+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.
49	49
50		-//__Optional API parameters are handled correctly__//
51		-Currently, eMagiz would create the wrong expression for handling optional API parameters. With this release we have improved the expression in such a way that all optional parameters are handled correctly out of the box.
	48	+[[image:Main.Images.Release Blog.WebHome@release-216-hack-heaven--multiple-environments.png]]
52	52
53		-//__Without CDM rights nothing related to any data model can be edited anymore__//
54		-With this release, we have made sure that nothing related to any data model can be edited without having the proper rights.
	50	+== **Feedback Items** ==
	51	+//__Easier component selection in flow designer__//
	52	+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.
55	55
56		-//__Improved sorting of Design and Deploy archticture__//
57		-With this release, we now ensure that both Design and Deploy architecture are sorted in the same manner to avoid confusion when quickly switching between both views.
	54	+//__Improved handling of optionality in JSON on lists__//
	55	+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.
58	58
	57	+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.
	58	+
	59	+//__Loading bar when searching for log entries__//
	60	+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.
	61	+
	62	+//__Improved feedback when deleting elements from Capture__//
	63	+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.
	64	+
	65	+//__Enhanced filter options in Manage__//
	66	+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.
	67	+
	68	+//__Copy property names from Create__//
	69	+This release unlocks the possibility of easily copying the name of a property placeholder so it can be used while deploying.
	70	+
	71	+//__Improved feedback during migration to the current runtime architecture__//
	72	+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.
	73	+
	74	+//__Block user from making changes to their cloud while another upgrade is still in progress__//
	75	+We now block users from changing their cloud configuration when another upgrade is ongoing.
	76	+
	77	+//__Cron trigger validation__//
	78	+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.
	79	+
	80	+== **Bug Fixes** ==
	81	+//__Making Edit (and View) the default action when configuring parameters__//
	82	+We have made the Edit (and View) button the default action when configuring parameters in a transformation.
	83	+
	84	+//__Property configuration pop-up resized__//
	85	+We have resized the property configuration overviews to make the property value better readable.
	86	+
	87	+//__Alphabetically sorted components in the flow designer__//
	88	+As of this release, we now sort the components alphabetically in the flow designer.
	89	+
	90	+//__Improved sorting on runtime overview__//
	91	+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.
	92	+
	93	+//__Improved sorting on catalog overview__//
	94	+As of this release, we now sort the topics in the catalog by name.
	95	+
	96	+//__Styling fix on rich text editors__//
	97	+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	+
	99	+//__Styling fix on release edit__//
	100	+As of this release, the correct icon (green) will be shown when wanting to add a second API operation under the same "header."
	101	+
	102	+//__Removed false-positive alerts on transformations__//
	103	+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	+
	105	+//__Event Streaming Graphs - view thirty days back__//
	106	+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	+
	108	+//__Improved helptext__//
	109	+We have improved various help texts across the portal to indicate better what should be filled in for specific fields.
	110	+
59	59	== **Fancy Forum Answers** ==
60	60
61	61	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:
62	62
63		-* [[jsonPath in SpEL expressions>>https://my.emagiz.com/p/question/172825635703415034||target="blank"]]
64		-* [[Connecting to Azure SQL>>https://my.emagiz.com/p/question/172825635703415110||target="blank"]]
65		-* [[Changes to JSON api keep breaking my model validation, although they are irrelevant to me>>https://my.emagiz.com/p/question/172825635703415225||target="blank"]]
	115	+* [[XSD is only partially imported into eMagiz (xmlStat.xsd)>>https://my.emagiz.com/p/question/172825635703773349||target="blank"]]
66	66
67		-== **Key takeaways** ==
	117	+== **Key Takeaways** ==
68	68
69		-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:
	119	+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:
70	70
71	71	* If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
72	72	* If you have feedback or ideas for us, talk to the Platypus
73		-* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
	123	+* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
74	74	* Clear your browser cache (Ctrl + Shift + Del)
75	75	* Check out the release notes [here]
76	76	* Start thinking about how the license tracker can aid your development
77	77	* Start thinking about major, minor, and patch
78		-* Upgrade to the latest build number
79	79	* Keep making great integrations
80	80
81	81	Let's stay in touch and till next time!
...	...	@@ -83,6 +83,11 @@
83	83	{{info}}
84	84	~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
85	85
86		-~*~* Indicates a GEN3-only feature.
87		-{{/info}})))((({{toc/}}))){{/container}}
	135	+{{/info}}
	136	+)))
	137	+
	138	+(((
	139	+{{toc/}}
	140	+)))
88	88	{{/container}}
	142	+{{/container}}