Skip to Content

Changes for page 232 - Bug Busters

Last modified by Carlijn Kokkeler on 2024/11/04 11:23
From version 314.1
edited by Erik Bakker
on 2024/09/09 10:17
Change comment: There is no comment for this version
To version 41.1
edited by Erik Bakker
on 2023/01/18 11:22
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -229 - Xpath Alignment
1 +190 - Fast Forward
Content
... ... @@ -1,10 +1,34 @@
1 -During our recent sprint cycle, we made several improvements to keep our model running smoothly. We also made some small changes to various XPath-related parts of the portal and updated our deployment plan. Please find all our changes and bug fixes below.
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.229 - Xpath Alignment||target="blank"]].
3 +Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.190 - Fast Forward.WebHome||target="blank"]].
4 4  
5 -====Minor changes====
6 -* Deploy - Deployment plan: We updated the deployment step that temporarily disables the triggers in your model. As a result, you can now define after which waiting period (determined in minutes) you want eMagiz to take action. When it reaches this point, eMagiz will act according to the selected option. You can opt to "automatically re-enable triggers," "receive a notification mail," or "both." On top of that, we reintroduced the automatic "enable trigger" step, which can be added as the last step of your deployment plan to automatically re-enable triggers. Be aware that you *still* need to enable triggers manually if you have manually disabled them before deploying. This can be done via the Manage phase.
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"]].
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 +
8 8  ====Bug fixes====
9 -* Create - Flow Designer: Improved the help text of the edit/new header menu in the XPath header enricher component (#727)
10 -* Create - Transformation: Fixed bug that causes the value input field to disappear if you switch from custom xpath to if it exists. (#1010)
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.