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	+196 - The Last Post

Content

...	...	@@ -1,36 +1,38 @@
1		-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. In addition, we launched 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.
	1	+Here's our first release of this quarter. We have delivered additional small (bug) fixes in this release and released the Live Flow testing feature. The last is a real improvement during the development process of a flow. Furthermore, you will find several improvements in the way of work for nextGen environments.
2	2
3		-Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.216 - Hack Heaven||target="blank"]].
	3	+Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.196 - The Last Post.WebHome||target= "blank"]].
4	4
5	5	=====New features=====
6		-* When deploying the on-premise agent for an on-premise machine, users now have the option to select "Multiple environments" when the selected OS type is Windows. This will solve an issue where deploying multiple machines from different environments (machines from Deploy architecture) to the same on-premise machine (the 'physical' machine) running Windows Server 2022 as an operating system was impossible. We have now implemented a fix allowing users to run these multi-environment setups on their Windows Server 2022 machines.
7		-* Deploy - Architecture: Changing the memory of a runtime should now be done via the machine "details" screen. On top of this logic is added to check the overall health of the machine. This check is reevaluated on every change made on runtime level related to memory.
8	8
	7	+* Create - Flow Testing: so far, the Flow Testing allows test eMagiz flows by defining the testing point on the starts and the end points and comparing the actual and expected messages. In this release, “Live Mode Testing” is introduced, making it possible to test communication with real endpoint. That means that an “http output gateway” can be marked in “Live Mode”, if so, the http output gateway will send its http request to the real endpoint and received the result so we can go further with testing.
	8	+
9	9	=====Minor changes=====
10	10
11		-* Capture - Generic: When deleting a system, tenant, or integration, more information is provided on what you are deleting (#1174)
12		-* Create - Transformation: An optional list in JSON will only create a list if there are items for that list. Otherwise, no list will be made by default. (#941)
13		-* Create - Flow designer: Property pop-ups now contain the property name as a text where you can copy the property's name. (#1175)
14		-* Create - Flow designer: When specifying a cron trigger in an inbound component, the validity of the cron is checked to ensure that no issues with the expression occur after deploying the flow version. (#1165)
15		-* Create - Settings: The warning pop-up is shown when you try to migrate your JMS server to 3rd Generation runtime, and other containers that need to be migrated first show the list of other containers. (#1248)
16		-* Deploy - Releases: Some usability improvements were implemented in Deploy > Releases. Users can now select the flow version of the infra flows (for each pattern respectively) by right-clicking the light-green eMagiz platform component (much like in Create). When the infra flow version has been edited in a release, the platform will color light blue to signify this change in the infra version. The context menu containing the versions also shows a caption to show what exact component has been right-clicked and whose flow versions are showing (i.e., entry, exit, onramp, offramp)
17		-* Deploy - Architecture: When architectural changes are pending in Deploy → Architecture, the screen will not allow edits and show a message that changes are pending. (#1079)
18		-* Deploy - Architecture: Pending changes will now block continuing after pressing "Apply to environment" instead of when pressing "Apply Changes" in the next screen. (#606)
19		-* Deploy - Architecture: Applying to environment or saving your machine is not possible If there is more memory configured than available. (#1144)
20		-* Deploy - Architecture: Changing the memory of a runtime should now be done via the machine "details" screen. On top of this logic is added to check the overall health of the machine. This check is reevaluated on every change made on runtime level related to memory. (#545)
21		-* Manage - Monitoring: A progress bar is added when users have long searches on "Log entries". (#1133)
22		-* Manage - Alerting - Triggers - New: It can now filter across Queues, Topics, Recipients, and Runtimes when adding a new trigger. (#1089)
23		-* Manage - Alerting - Alerts: It is now possible to filter the alerts based on the status. (#1176)
24		-* Catalog: Topics are now sorted alphabetically (#1231)
	11	+* Deploy - Architecture: The topics are now ordered alphabetically and the runtimes will now get the same order as design architecture (after ‘apply to environment’)
	12	+* Create - Flow designer: CDM edit right is applied to the message definition in Create phase. You can not change CDM message definition, Gateway message definition, even Event streaming message definition without the proper right.
	13	+* Deploy - Architecture: We improved the auto-healing feature of AWS machines. The new generation JMS server runtimes always start before other runtimes are ran.
	14	+* Administration-User management: Company contact can edit permissions of models that fall under child companies
	15	+* Administration: Contracts page removed
	16	+* Create-Flow designer: Model resources tab removed on resources page when adding an resource to a validating filter.
	17	+* Deploy - Releases: We reduced the time it takes to prepare a release, before it can be deployed. The process of building runtime images has been optimized.
	18	+* Deploy - Releases: We have improved editing properties in releases for runtimes that are 3rd generation compatible.
	19	+* Design - Store: You are able to see some warning messages when you import a transformation from store. Because your imported transformation is required some information from the related store fragment. You should include that store fragment to avoid a breaking transformation in Create phase after importing. Afterward, we will update your existing flow component transformer to make it work correctly.
	20	+* Design - Store: We updated importing to help you avoiding an error during importing store item that will break your message definition in some special cases.
	21	+* Create - Store: We excluded automatically resources that are not good enough from the exporting wizard. Then you will easy to recognize a problem and avoid creating unusable store item.
	22	+* Flow Designer: Resources in "Unused resources" section can be marked as used for the case that the resources are referred by components through property placeholders or in custom spel expressions.
	23	+* Create - API Gateway: We fixed an issue where an optional query parameter would cause failed requests, if that parameter was not supplied. Please reset your entry flow to apply the fix.
	24	+* Create - API Gateway: We fixed an issue where API-Key secured requests would fail with error code 500 instead of code 401, if no API-Key was supplied. Please reset your entry flow to apply the fix.
	25	+* Design - Store: We fixed an issue that you import the message definition(s) and a specialized DataType of imported message definition(s) are not matched with the exported message definition(s). Now, they are matched and your transformation won't get issues.
	26	+* Create-Resources: When viewing a resource, its full name will be shown, removing the need to download the resource in order to obtain its name
	27	+* Create - Flow designer: Improve responsiveness of resources tab at right panel
	28	+* Manage - Explore: New button to delete queue is added and only visible for Expert Service (Admin)
25	25
26	26	====Bug fixes====
27	27
28		-* Generic: Styling fix has been implemented for the text editor area in some places: Q&A forum (posts and answers), Edit store item pop-up (documentation field), and the Flow > Other > Documentation input field in the pop-up. (#1246)
29		-* Generic: The help text for the protocols field on the Jetty server and the SSL Web service message sender is clearer and shows possible options. (#1247)
30		-* Create - Transformation: The 'View' and 'Edit' buttons under parameters are the default behavior when you are editing. (#1241)
31		-* Create - Transformation: if one attribute rule from "string" to "nonEmptyString" has a filter with type "If exists" and with an empty check, then no warning about type incompatible will be generated. Clicking the "Refresh" button in the right panel for the current transformation with the false positive warnings will clean them. (#689)
32		-* Create - Flow designer: Components in the left panel of the flow designer are now alphabetically sorted by their name. (#1164)
33		-* Deploy - Property Overview: Resized window so that all property names are not cut off halfway. (#1081)
34		-* Deploy - Runtime Overview: Sorting on status is possible. (#1240)
35		-* Deploy - Releases: We fixed a minor styling issue when you edit the release by adding/removing the operations to the system in the API pattern. The cursor "Red stop sign" and "Green plus" are showing correctly now. (#788)
36		-* Monitoring - Event streaming statistics: graphs can show up to 30 days.
	32	+* Create - Flow designer: Improved help texts of various flow components related to key-/truststores and their usage. They now better explain what you need them for and mention important security considerations.
	33	+* Create - Flow designer: Various small (cosmetic) fixes and changes in the edit pages of some flow components to make them more consistent with similar pages.
	34	+* Manage/Event streaming statistics. For some models, (some) topic data did not show in the graphs.
	35	+* Deploy - Releases: We fixed an issue, where after removing containers from a machine, during execution of the deployment plan, the removed containers are not recognized as change, causing the ‘Deploy machine’ step to be skipped.
	36	+
	37	+====Remarks====
	38	+