Skip to Content

Changes for page 216 - Hack Heaven

Last modified by Carlijn Kokkeler on 2024/05/22 13:35
From version 41.1
edited by Erik Bakker
on 2023/01/18 11:22
Change comment: There is no comment for this version
To version 209.1
edited by Erik Bakker
on 2024/03/12 14:27
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -190 - Fast Forward
1 +216 - Hack Heaven
Content
... ... @@ -1,34 +1,33 @@
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.
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.190 - Fast Forward.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 -* A new runtime image for customer models running on the 3rd generation runtime. Please find out more on our [[Runtime Image release notes>>Main.Release Information.Runtime Images.V110.WebHome||target="blank"]].
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 7  
8 -=====Major changes=====
9 -
10 -* Store - Private store. This release introduces the private store with the following features:
11 -** Store items will be private by default and are only accessible for users that belong to the same company as the user that exported the store content. Note that the store item needs to be approved before it is visible to users.
12 -** A new user role, "Store Exporter," will be introduced and can be assigned to the users who can create and update store items.
13 -** Approval of a store item will be executed by eMagiz personnel, who can also set a store item to be public.
14 -** Public store items will be importable by all users.
15 -
16 16  =====Minor changes=====
17 17  
18 -* Create - Event Streaming: Event streaming is now available for models migrating to the 3rd generation runtime.
19 -* Create - Transformation: source filter on attribute with empty field is more readable in read-only mode. (#732)
20 -* Create - Migration: Improved compatibility checks related to the 3rd generation runtime migration.
21 -* Deploy - Check properties: Informative error messages when saving or creating a property. (#576)
22 -* Deploy - Deployment plan: We improved the deployment plan to avoid it causing problems when executing a deployment plan containing loads of steps.
23 -* Deploy - Architecture: Added reset feature for 3rd generation runtimes.
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)
24 24  
25 25  ====Bug fixes====
26 -* Create - Settings: We fixed an issue where changing the connection type did not update all relevant flows.
27 -* Create - Flow designer: Newly generated flows were configured with incorrect resource locations under specific circumstances.
28 -* Deploy - User management: Fixed an issue where 'Apply to environment' would take very long to finish.
29 -* Deploy - Deployment plan: While generating a default plan, flow type steps will not be created for OSGi runtimes that run on a Docker machine. (#798)
30 -* Deploy - Architecture: Cloud slots now wake up without potential need to apply to environment.
31 -* Deploy - Architecture: 3rd generation runtimes are included in runtime checks while upgrading your cloud environment.
32 32  
33 -====Remarks====
34 -* Mendix Runtime has been upgraded to Mendix 9.19.0.
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 on 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.