Changes for page 216 - Hack Heaven
Last modified by Carlijn Kokkeler on 2024/05/22 13:35
From version 17.1
edited by Erik Bakker
on 2022/11/08 08:30
on 2022/11/08 08:30
Change comment:
There is no comment for this version
To version 207.1
edited by Erik Bakker
on 2024/03/11 15:35
on 2024/03/11 15:35
Change comment:
There is no comment for this version
Summary
-
Page properties (2 modified, 0 added, 0 removed)
Details
- Page properties
-
- Title
-
... ... @@ -1,1 +1,1 @@ 1 -1 87-IntegrationSponsor1 +216 - Hack Heaven - Content
-
... ... @@ -1,25 +1,34 @@ 1 - Thereleasebrings thenextstepoftheDesignstoreto thepublicandreleasesanewversionof the eMagizMendixConnectorthat unlocks those usingit tomigrate to thenextgeneration runtime.Ontopfthat,wehaveseveralfeedbackitemsandbugfixes.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. 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. 2 2 3 -Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.1 87-Integration Sponsor Switch.WebHome||target="blank"]].3 +Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.216 - Hack Heaven||target="blank"]]. 4 4 5 5 =====New features===== 6 -* Design - Store: It is now possible to import Transformations and Data Models from the Store into a model. 7 -** The Design Store can now be opened from the Mapping and Data Model screens as well. 8 -** The Design Store now offers search options to find store items that include Transformations and/or Data Models. 9 -** When importing a Store item with a Transformation and/or Data Model a new merge tool is available to link the Store Items data model to the users data model or to add new attributes/entities to the user data model. 10 -** When importing a Store item with a data model that has been previously linked the links are automatically restored allowing for easy updating of store based Integrations and for easier installation of multiple Store items with the same data model. 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) that are running Windows Server 2022 as an operating system was not possible. Now we have implemented a fix that will allow users to run these multi-environment setups on their Windows Server 2022 machines. 11 11 12 12 =====Minor changes===== 13 13 14 -* Create - Flow designer: Improved the help texts of the Kafka components to better explain certain performance and load-balancing considerations, and added detailed information how messages (including headers) are converted to/from Kafka records. 15 -* Create - eMagiz Mendix Connector exit: Download buttons are added for non legacy eMagiz Mendix connectors 16 -* Create - Overview: You will now be able to see the errors that you have within a flow but on the integration widget. To do this, go into your flow and the number of errors you have in it, if any, will update so that next time you don’t have to navigate inside the flow to check how many alerts you have. 10 +* Capture - Generic: When deleting a system, tenant or integration, more information is provided on what you are deleting (#1174) 11 +* Create - Transformation: An optional list in JSON will only create a list if there are items for that list. Otherwise, no list will be created by default. (#941) 12 +* Create - Flow designer: Property pop-ups now contain the property name as a text where you can copy the name of the property. (#1175) 13 +* 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) 14 +* Create - Settings: Warning pop-up that is shown when you try to migrate your JMS server to 3rd Generation runtime and there are other containers that need to be migrated first shows the list of other containers. (#1248) 15 +* Deploy - Releases: Implemented some usability improvements 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 infra version. Additionally, the context menu containing the versions also shows a caption now to show what exact component has been right clicked and whose flow versions are showing (entry/exit/onramp/offramp/etc.) 16 +* Deploy - Architecture: Applying to environment or saving your machine is not possible If there is more memory configured than available. (#1144) 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 continueing after pressing “Apply to environment”, instead of when pressing “Apply Changes” in the next screen. (#606) 19 +* Manage - Monitoring: progress bar is added when users haves long searches on “Log entries”. (#1133) 20 +* Manage - Alerting - Triggers - New: It is now possible to filter across Queues, Topics, Recipients and Runtimes when adding a new trigger. (#1089) 21 +* Manage - Alerting - Alerts: It is now possible to filter the alerts based on the status. (#1176) 22 +* Catalog: Topics are now sorted alphabetically (#1231) 17 17 18 - 19 19 ====Bug fixes==== 20 -* Design - Store: Importing store item from response messages doesn't cause issues anymore 21 -* Design - Store: Importing response message and transformation to Api integration is possible 22 -* Design - API Gateway: The order of attributes in gateway messages were not always the same as the order in the generated Open API document. 23 -* Create - Flow Designer: Fix bugs when copy and paste components in G3 configuration 24 -* Create - Flow designer - Store: We fixed the maintaining selection of flow flagment from Store. 25 -* Manage - Exceptions of error messages: The count of error messages per exception class are now displayed (#744) 25 + 26 +* Generic: Styling fix has been implemented for the text editor area in some places: QnA forum (posts and answers), Edit store item popup (documentation field) and the Flow > Other > Documentation input field in popup. (#1246) 27 +* Generic: The helptext for the protocols field on the Jetty server and the SSL Web service message sender is now clearer and shows which options are possible. (#1247) 28 +* Create - Transformation: The ‘View’ and ‘Edit’ button under parameters are default behaviour when you are editting. (#1241) 29 +* Create - Transformation: if one attribute rule from “string” to “nonEmptyString” has a filter with type “If exists” and with empty check, then no warning about type incompatible will be generated. For the current transformation with the false positive warnings, clicking “Refresh” button in the right panel will clean them. (#689) 30 +* Create - Flow designer: Components in the left panel of the flow designer are now alphabetically sorted by their name. (#1164) 31 +* Deploy - Property Overview: Resized window such that all property names are not cut off half way. (#1081) 32 +* Deploy - Runtime Overview: Sorting in status is possible. (#1240) 33 +* Deploy - Releases: We fixed a small 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) 34 +* Monitoring - Event streaming statistics: graphs can show up to 30 days.