Skip to Content

Changes for page 216 - Hack Heaven

Last modified by Carlijn Kokkeler on 2024/05/22 13:35
From version 207.1
edited by Erik Bakker
on 2024/03/11 15:35
Change comment: There is no comment for this version
To version 34.1
edited by Erik Bakker
on 2022/12/06 16:05
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -216 - Hack Heaven
1 +189 - Private Eye
Content
... ... @@ -1,34 +1,24 @@
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.
1 +The release brings a private store to our community and makes the latest runtime image available for our customers running on the 3rd generation architecture. Furthermore, we introduce several improvements to our 3rd generation runtime and its interaction with the portal.
2 2  
3 -Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.216 - Hack Heaven||target="blank"]].
4 -
3 +Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.189 - Private Eye.WebHome||target="blank"]].
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) 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.
5 +* A new runtime image for customer models running on the 3rd generation runtime. Please find out more on our [[Release blog>>Main.Release Information.Runtime Images.V110.WebHome||target="blank"]].
7 7  
8 8  =====Minor changes=====
9 9  
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)
9 +* General: Code mapping is now available for models migrating to the 3rd generation runtime.
10 +* General: Added functionality that allows you to search by pressing "Enter" on various pages across the platform. (#785)
11 +* Store: Renamed several display names across the Store functionality to better clarify what the functionality does for you.
12 +* Deploy - Deployment plan: For 3rd generation runtimes we have changed the restart behavior in case of startup problems. This means that when a runtime is being deployed, which is constantly crashing and thereby causing problems, the restart of the runtime is limited to just five times. (#720)
13 +** After five times, the runtime will remain in the stopped state.
23 23  
24 24  ====Bug fixes====
16 +* Create - Flow designer: Resetting the JMS server sometimes resulted in invalid connection settings for connecting to the failover JMS server. (#717)
17 +* Create - Flow designer: Newly generated flows were configured with incorrect XSD or XLST resource locations under specific circumstances. (#718)
18 +* Deploy - Deployment plan: Before when you tried to deploy a Release via the Deploy functionality the widget could crash randomly. With this fix we ensured the widget will always load correctly. (#362)
19 +* Deploy - Architecture: Prechecks for cloud template upgrades failed unexpectedly under particular circumstances. (#703)
20 +* Manage - Runtime statistics: Data measurements of eMagiz-Mendix Connector runtimes are not missing anymore.
21 +* Manage - Error Dashboard: Solved a problem that caused a user to see a general error when opening the Manage Dashboard while running a 3rd generation runtime architecture.
25 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.
23 +====Remarks====
24 +* Mendix Runtime has been upgraded to Mendix 9.19.0.