Changes for page 216 - Hack Heaven
Last modified by Carlijn Kokkeler on 2024/05/22 13:35
From version 152.1
edited by Carlijn Kokkeler
on 2023/10/26 12:50
on 2023/10/26 12:50
Change comment:
There is no comment for this version
To version 208.1
edited by Erik Bakker
on 2024/03/11 15:39
on 2024/03/11 15:39
Change comment:
There is no comment for this version
Summary
-
Page properties (3 modified, 0 added, 0 removed)
Details
- Page properties
-
- Title
-
... ... @@ -1,1 +1,1 @@ 1 -2 07-AlignedState1 +216 - Hack Heaven - Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki. CarlijnKokkeler1 +XWiki.ebakker - Content
-
... ... @@ -1,37 +1,33 @@ 1 - Inthe lastsprintcycle, wefocused ondeliveringstategenerationcomponents.Ontopof that, wemadeseveral improvementsregardingthealignmentofmponentsandwedidsomeperformanceimprovementsandbugfixes.Moreover,we made achange in themetricsstorage duration.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. 2 2 3 -Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.2 07-Aligned State.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 -=====Runtime release notes===== 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. 6 6 7 -There is a new eMagiz Mendix connector available because a memory leak was found, only affecting Mendix connectors that have been migrated to the next generation architecture. It is advised to upgrade to the new eMagiz Mendix connector before fully migrating to the next generation architecture. 8 - 9 9 =====Minor changes===== 10 10 11 -* Design - Message Mapping: The button 'Import from Store' will directly open the store. 12 -* Create - Flow Designer: Performance improvements for the Flow Designer have been implemented. 13 -* Create - Flow Designer: When importing items from the store, flow fragments that are hidden in Design will be listed under the versions in Create. (#1044) 14 -* Create - Flow Designer: Resources without names won't trigger error messages when users select components. (#950) 15 -* Create - Flow Designer: A migration step has been added, such that the error channel is set to “errorChannel” of all inbounds in a flow if the custom error handling is set to false. 16 -* Create - Flow Designer: The performance of highlighting resources of selected components is improved in Read-only mode. 17 -* Deploy - Releases: When a release is removed, the related unused images in the on-premises machines will be removed as well. 18 -* Deploy - Release Properties: Special characters such as a backslash do not break properties after deployment. (#1028) 19 -* Manage - Monitoring: We will change the retention of monitoring data of different environments. For minute level data, it will be kept for test, acceptance and production environments for 7, 14 and 30 days respectively. Then the minute level data will be reduced to hour level data then will be stored for test, acceptance and production for 3, 6 and 12 months respectively. (#1045) 20 -* Manage - Monitoring: Extended user session times for 3rd generation runtime dashboards. 21 -* Manage - Triggers: When creating a new trigger the order of the cancel and next buttons has been switched. 22 -* Manage - Data Sink: The data sink page has been moved to the “Explore” tab. (#946) 23 -* Manage - Alerting: For gen3 models, you will no longer receive alert messages for every error message, every log message of 'level' ERROR, and for memory usage above 80%. For gen3 models with event streaming, the threshold to receive the 'Topic approaching maximum size' alert has been increased from 95% of the configured size used to 110%. The gen3 configurable trigger for error messages has been extended with the option to check whether the 'last-exception' message contained a certain text. This can be combined with the header-value match. 24 -* All - Buttons: The save and cancel buttons are placed slightly further apart to avoid misclicking. (#1022) 25 -* All - Systems: The positioning of Systems across Design, Create and Deploy phases are now synchronized to the position of their respective System in the Capture phase. (#687) 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 made by default. (#941) 12 +* Create - Flow designer: Property pop-ups now contain the property name as a text where you can copy the property's name. (#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: 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) 15 +* 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) 16 +* 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) 17 +* Deploy - Architecture: Pending changes will now block continuing after pressing "Apply to environment" instead of when pressing "Apply Changes" in the next screen. (#606) 18 +* Manage - Monitoring: A progress bar is added when users have long searches on "Log entries". (#1133) 19 +* Manage - Alerting - Triggers - New: It can now filter across Queues, Topics, Recipients, and Runtimes when adding a new trigger. (#1089) 20 +* Manage - Alerting - Alerts: It is now possible to filter the alerts based on the status. (#1176) 21 +* Catalog: Topics are now sorted alphabetically (#1231) 26 26 27 27 ====Bug fixes==== 28 28 29 -* Create& Deploy -Styling:Thestylingof the eventstreamingcanvasintheCreateandDeployphaseshas been slightlyalteredto makepicand event-processornamesmorereadable. (#1055)30 -* Deploy - Architecture:Containersaresetinactivewhen theyare removed inDesignandunused.31 -* Deploy-Releases:Wefixedan issuethat alotoferrorpopupswere shownwhen youpromotedaleaseversionto a next environment. (#1087)32 -* Manage - Triggers:Besideschecking theerrorheader, theerrortriggerisconfigured tocheckifan errorssagecontains a term.33 - 34 - 35 - =====Infraandimagechanges=====36 - 37 -* State generation: New state generationfeatureshavebeenadded. Please check out[[V2.0.0>>https://docs.emagiz.com/bin/view/Main/Release%20Information/Runtime%20Images/V2.0.0/]]from the[[runtime images>>Main.ReleaseInformation.RuntimeImages||target="blank"]] formoreinformation.25 +* 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) 26 +* 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) 27 +* Create - Transformation: The 'View' and 'Edit' buttons under parameters are the default behavior when you are editing. (#1241) 28 +* 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) 29 +* Create - Flow designer: Components in the left panel of the flow designer are now alphabetically sorted by their name. (#1164) 30 +* Deploy - Property Overview: Resized window so that all property names are not cut off halfway. (#1081) 31 +* Deploy - Runtime Overview: Sorting in status is possible. (#1240) 32 +* 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) 33 +* Monitoring - Event streaming statistics: graphs can show up to 30 days.