Skip to Content

Changes for page 204 - Found It

Last modified by Carlijn Kokkeler on 2024/05/22 13:39
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 47.1
edited by Erik Bakker
on 2023/01/31 14:56
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -190 - Fast Forward
1 +191 - Fifty Fifty
Content
... ... @@ -1,34 +1,53 @@
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 +The release introduces a lot of minor fixes as a result of our "hackathon" efforts. Subsequently, we will release several 3rd generation runtime offerings.
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.191 - Fifty Fifty.WebHome||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 +* Deploy - Architecture: We added the possibility to register network shares in your container volume settings. This enables the use of network shares without having to mount them manually on the host machine and then again on the container level. This option is only available for 3rd generation runtimes that run on-premises.
7 +* Deploy - Containers: In Deploy containers, a 'Debug' option is added for flows on the 3rd generation eMagiz runtime.
8 +** This option will temporarily be available for users on the next generation runtime. It allows one to easily wiretap messages from channels in a flow to a queue, which can then be browsed using the queue browser. One flow can be wiretapped at the time per container.
9 +** To use this option, the model must be fully migrated to Gen3, including the JMS. Additionally, only flows in a container with the Gen3 Debugging components inside the associated container infra flow can be debugged. Please consult the documentation for more information on how to set up debugging on Gen3.
10 +* Manage - Alerting: Five new triggers are available for Model in G3.
11 +** Error Message is to evaluate the headers of the original message which resulted in an error.
12 +** Log Keyword is to evaluate logging messages. You can provide one or several words which you expect in your logging events.
13 +** Queue Consumers is to check whether more than one consumer is expected on the queue level.
14 +** Queue Messages is to configure for queues where more than 100 messages on a queue can occur
15 +** Queue Throughput is to monitor issues with your system by setting thresholds for the number of messages expected to pass through the flow.
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.
19 +* Data-Limit: Set data limit per environment.
20 +* Login page: The login page /login.html now redirects to the actual login page /p/login. (#671)
21 +* Create - Flow designer: Removed the unnecessary refresh button from the component creation pop-ups. (#858)
22 +* Create - Flow designer: Properties in the property overview pages are sorted as Test/Acceptance/Production. (#804)
23 +* Create - Flow designer: We improved validation and help text on Wss4J interceptors components. (#733)
24 +* Create-Flow testing: Improved the help text when adding a header type for a test message. It clearly states which Java classes can be used, along with some examples. (#742)
25 +* Deploy - Releases: Setting a release as active by pressing the deploy button creates an entry in the deploy history. (#823)
26 +* Deploy - Releases: We improved the notification pop-ups of failed machine deployments.
27 +* Deploy - Releases: We added column sorting to the pop-up showing the missing properties. (#860)
28 +* Deploy - Architecture: New cloud slots have their auto-upgrade value set to true by default. (#841)
29 +* Deploy - Architecture: A docker container's status is more visible when you open the detail page of the docker container.
30 +* Deploy - Architecture: The instance's state is now visible on the detail page about an instance. (#699)
31 +* Deploy - Architecture: We changed the wake-up time of cloud slots on Fridays to 6:00 UTC so that they no longer fall within our regular deployment windows. (#559)
32 +* Deploy - Architecture: We added runtime memory checks to 'Apply to environment' to prevent invalid deployments. (#719)
33 +* Deploy - Properties: We improved runtime selection when copying properties. (#796)
34 +* Manage - Explore: Improved the displayed error message when a message could not be loaded in the message redelivery screen. (#696)
35 +* Manage - Explore: "Save as test message" button opens a pop-up that allows you to edit your test message's name, description, content, and headers before saving it.
36 +* Manage - HTTP statistics: Fixed a typo in the HTTP statistics dashboard. (#856)
37 +* Manage - Alerting: By default, no filter is applied to the status when navigating to the "Notifications" overview or resetting the filters on the "Notifications" overview. (#486)
24 24  
39 +
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  
42 +* Design - Solution design: We hide systems without functional integration now. (#714)
43 +* Create - API Gateway: Security header case insensitive
44 +* Create - Flow designer: Enabling redelivery for your integration is applied after resetting your offramp and exit flow. Before this change, you needed to remove and add the integration to Create phase to use this setting.
45 +* Deploy - Containers: Applied styling to the error pop-up with the list of reasons why a runtime can't be deleted to make it easier to read. (#546)
46 +* Deploy - Architecture: Deploying your model to the cloud for the first time required you to press 'Apply to Environment' twice. This is no longer the case. (#508)
47 +* Deploy-Volumes: Network volumes are visible when the container is not deployed.
48 +* Manage - Monitoring: Fix typo in Event Processors Metrics. (#835)
49 +
33 33  ====Remarks====
34 -* Mendix Runtime has been upgraded to Mendix 9.19.0.
51 +
52 +* Mendix Runtime has been upgraded to Mendix 9.21.0.
53 +