Skip to Content

Changes for page 264 - Strict Separation

Last modified by Erik Bakker on 2026/03/22 21:45
From version 68.1
edited by Erik Bakker
on 2023/04/13 14:31
Change comment: There is no comment for this version
To version 324.1
edited by Erik Bakker
on 2026/03/22 21:44
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -195 - Easter Party
1 +264 - Strict Separation
Content
... ... @@ -1,43 +1,32 @@
1 -As the quarter has ended, we went silent for a couple of weeks to plan for the upcoming quarter during our PI rituals. This time we added the famous "Hackathon" to the end of the PI week so we could start the Easter break with excellent spirit after solving several smaller feedback items and bugs reported by you. Several of those stories will be included in this and the upcoming release. On top of that, we introduce various improvements to our API Gateway pattern and our 3rd generation runtime architecture. Subsequently, we will release a new runtime image supporting the multiple improvements.
1 +This release includes our new user management for models running on our latest versions of the API Gateway **and** Event Streaming offerings. Furthermore, it includes a new **[[environment template>>Main.Release Information.Cloud Templates.WebHome||target="blank"]]** that improves machine behavior in a single-lane cloud configuration when runtimes are added or removed. On top of that, we introduce several improvements that enhance and clarify the user experience throughout the platform.
2 2  
3 -Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.195 - Easter Party.WebHome||target= "blank"]].
3 +Please find out more on our [[Release blog>>doc:Main.Release Information.Release Blogs.264 - Strict Seperation.WebHome||target="blank"]].
4 4  
5 -=====New features=====
5 +==== Minor changes ====
6 6  
7 -* Deploy - Releases: We take the first step to fix properties to a release. This gives users more control over properties. For example, they can ensure that the release contains suitable properties that are more manageable.
8 -** When this release reaches production, the first new release that users activate and have Gen3 containers/properties, the new feature becomes active. Users will see a wrench icon on the release. When they click on it, they will see an overview of the attached Gen3 properties.
9 -** These properties cannot be altered for that specific release. This only counts for Gen3 properties, properties for Gen2 runtimes/machines will still be fetched from the Deploy-Properties list and can still be altered. If users notice that a specific Gen3 property of a release not contains the correct value, users can edit the value by opening the property overview of the release. At the bottom of the overview, the option ‘Change properties’ allows users to edit the properties of a release.
10 -** A new ‘property’ release will be created when users use that option. A ‘property’ release can be identified by a suffix that contains a letter. Users can change the properties, and when they are done, they can directly activate and deploy the release. With our new improvements to the deployment plan, only the affected containers by the property change(s) will be redeployed. This will result in faster deployments.
7 +* Deploy - User management: Several new functionalities are released, improving the user experience when dealing with user management. To experience these improvements, you need to be running on the latest version of our API Gateway and/or Event Streaming offering.
8 +** When you click “Apply to environment” in Deploy > User management, a pop-up now displays all pending changes. You can select only the changes you want to apply (cherry-pick), and any related dependencies will be automatically selected. This helps prevent mistakes and ensures consistency when applying updates. With this enhancement, you can more easily and safely customize configurations per environment.
9 +** For fully migrated models (using DSH for Eventstreaming), the ‘transfer to design’ and ‘apply to environment’ buttons are combined. All changes will be shown when you press ‘apply to environment’ and will be applied when you press ‘apply’.
10 +** For fully migrated models (using API MAM for API gateway), the ‘transfer to design’ and ‘apply to environment’ buttons are combined. All changes will be shown when you press ‘apply to environment’ and will be applied when you press ‘apply’.
11 +* Deploy - Property: When saving a property, we now perform an optimization check. These improvements help reduce redundancy and keep property configurations cleaner and easier to maintain.
12 +** If other properties share the same name and value, we will recommend grouping them to improve manageability.
13 +** If any runtimes in the list of linked runtimes do not use the property, we suggest removing those runtimes from the list.
14 +** If none of the linked runtimes use the property, we recommend removing it.
15 +* Deploy - Releases: It is no longer possible to try to deploy a release that contains runtimes that are not linked to any flows in the architecture. (#1066)
16 +* Deploy - Architecture: Adding/moving/deleting containers from machines will now not replace the underlying instances. This was only the case for singlelanes. Doublelanes do not have this behaviour and are not affected.
11 11  
12 -{{info}}Important to note is that
13 -* While changing a property in a ‘property’ release, users also have the option to alter the value in the Deploy-Properties list. By default, this is set to Yes, because when a new release is created, the values of Deploy-Properties will be used and not properties of an earlier release. When a user closes the screen for editing a property, the change will immediately be implemented.
14 -* The auto-clean release functionality is unaffected by this change, ‘property’ releases will not be counted as a release.
15 -* There is a maximum of twenty-six ‘property’ releases. (twenty-six letters of the alphabet)
16 -* Only the latest release can be edited. This can be identified by checking the suffix. The suffix with the latest letter of the alphabet is editable.{{/info}}
18 +==== Bug fixes ====
17 17  
18 -=====Minor changes=====
20 +* Design - Import XSD: Added the ability to import XSD files with an element of type 'all'. (#1146)
21 +* Design - Swagger Configuration: Errors related to the generation of the Swagger UI in eMagiz have been resolved. Users will no longer encounter errors when generating JSON (new cases). (#1424) (#1337)
22 +** Additionally, users can now define multiple tags per operation. Multiple tags should be separated using “-”. (#838)
23 +** An issue affecting the generation of examples for custom-defined schemas in the request and response body has also been fixed.
24 +** Schema validation has been extended to help prevent configuration mistakes. Existing errors related to referencing or schema definitions in the request/response body may still be present. However, when opening the edit page and clicking Save, the extended validation will be triggered. If the configuration results in an error, the validation will indicate this so it can be corrected before saving. (#924)
25 +* Create - Flow Testing: Users will get a pop-up error message related to their broken test case and will be asked to fix it. For automated test cases, a warning about broken test cases is shown to users who want to create a new version in the flow designer.
26 +* Deploy - Release Execution: The description of a manual step in the deployment plan is only shown once while deploying. (#933)
27 +* Manage - Alerting - Triggers: Fixed synchronization issue for log triggers, preventing unexpected behavior when all log triggers must be re-sent (#961)
19 19  
20 -* General - Control Tower: Changed several generic triggers for more predictable behavior.
21 -* Administration - License Tracker: The license tracker has been updated for new license models and features.
22 -* Administration - License Tracker: When the feature ‘Data sink’ is enabled, the number of message packs of the contract will be displayed when you hover with the mouse over the feature.
23 -* Capture - Settings: Editing message types are now consistent between new and existing ones. (#884)
24 -* Design - API Gateway: Default HTTP responses are generated automatically (#417)
25 -* Design - Solution design: An additional option is added to the context menu that navigates to the message definition added to event streaming topics without processors. (#850)
26 -* Create - Add Integrations: We used the name of the API integration that you set in the Design phase to display on the Transfer screen. That helps you choose the correct integrations to add to the Create phase more quickly.
27 -* Create - 3rd Generation Migration: You can toggle the custom error handling option for your event processors while migrating your event processing container to the 3rd Generation Runtime.
28 -* Deploy - Deployment plan: When you run your deployment plan in your model using the new generation runtimes, you will be able to be the logs that relate to an executing deployment step.
29 -* Deploy - Deployment plan: The "Prepare release" is not scheduled automatically anymore, so you can be in control of your deployment plan.
30 -* Deploy - Architecture: Certificates only editable by system admin.
31 -* Manage - Jobs: In case the model has containers that contain jobs in one of its flows, users can inspect job managers, job executions, and job step executions. Note that this only works for the 3rd generation runtime.
29 +==== Remarks ====
32 32  
33 -====Bug fixes====
34 -
35 -* General - Runtime Image: A new runtime image for customer models running on the 3rd generation runtime. Please learn more about our [[Runtime Image release notes>>Main.Release Information.Runtime Images.V140.WebHome||target="blank"]].
36 -* Design - API Gateway: Improved generation of Open API JSON and example messages for API gateway operations to handle cases where an element in your gateway definition is used multiple times. (#440)
37 -* Design - API Gateway: We fixed an issue where changing the message format of a gateway message did not result in an update of the OpenAPI (i.e., Swagger) document.
38 -* Design - System message: We fixed an issue that led to importing towards the wrong message definition when the option "Import from XSD" was chosen on a synchronous message. (#818)
39 -* Create - Message: When viewing or editing an enumeration, it is no longer deleted when the cancel button is pressed.
40 -
41 -====Remarks====
42 -
43 -* Deploy - Releases: We removed the existing snapshots of release property values.
31 +* General - Portal: We have removed part of our platform's functionality as it was not used anymore.
32 +* General - Help Text: We have updated our help text widget to align it with the new UI options in Mendix. (#1757)