Skip to Content

Changes for page 232 - Bug Busters

Last modified by Carlijn Kokkeler on 2024/11/04 11:23
From version 40.1
edited by Erik Bakker
on 2022/12/22 13:15
Change comment: There is no comment for this version
To version 291.1
edited by Carlijn Kokkeler
on 2024/08/12 12:00
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -189 - Private Eye
1 +227 - Fix Frenzy
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.ebakker
1 +XWiki.CarlijnKokkeler
Content
... ... @@ -1,34 +1,17 @@
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 +During our recent sprint cycle, we have ......
2 2  
3 -Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.189 - Private Eye.WebHome||target="blank"]].
3 +Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.227 - Fix Frenzy||target="blank"]].
4 4  
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"]].
5 +====Minor changes====
6 +* Deploy - Architecture: The user is now able to search in the Start/Stop flows overview.
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 -=====Minor changes=====
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.
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 -
33 -====Remarks====
34 -* Mendix Runtime has been upgraded to Mendix 9.19.0.
9 +* Create - Flow Designer: We fixed an issue where certain areas were selected in the flow designer when only hovering over them, without clicking.
10 +* Create - Flow Testing: The tracing information for errorChannel messages has been improved.
11 +* Create - Message Definitions: The "last changed by" and "last changed date" values of additional namespace resources are now updated correctly when you make changes to your namespaces in your message definitions.
12 +* Deploy - Releases: We fixed a bug where runtimes that did not change appeared in the deployment plan in the list of flows that will be restarted.
13 +* Deploy - Releases: When moving to the Deploy phase for the first time, a background action could fail, preventing deploying a release.
14 +* Deploy - Runtime Overview: We fixed a bug such that the runtime overview now shows the correct container version.
15 +* Manage - Alerting: We have implemented a fix that allows you to activate and test queue triggers per environment when you are migrating your model to the current runtime architecture. You will be able to test the queue triggers of any environment that is fully migrated, even if another environment is still in the process of migrating.
16 +* Manage - Alerting: You can now add internal and external recipients to your default trigger configuration at the same time, and they will be applied to your triggers correctly.
17 +* Manage - Alerting: We have fixed a case where a tenant-queue-trigger could be activated on a hybrid environment, before the JMS of that environment had been deployed to the current runtime.