Changes for page 264 - Strict Separation
Last modified by Erik Bakker on 2026/03/22 21:45
From version 192.1
edited by CarlijnKokkeler
on 2024/01/29 15:39
on 2024/01/29 15:39
Change comment:
There is no comment for this version
To version 324.1
edited by Erik Bakker
on 2026/03/22 21:44
on 2026/03/22 21:44
Change comment:
There is no comment for this version
Summary
-
Page properties (3 modified, 0 added, 0 removed)
Details
- Page properties
-
- Title
-
... ... @@ -1,1 +1,1 @@ 1 -2 13-JoyfulJourneys1 +264 - Strict Separation - Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki. CarlijnKokkeler1 +XWiki.ebakker - Content
-
... ... @@ -1,31 +1,32 @@ 1 - In thelastsprintcycle,wefocusedonimprovingpop-upmessagestoimprove theuserexperience.Moreover,wedidseveralalignment&formattingimprovements. Lastly,some morefeedbackitemshavebeensolved,and several morebug fixes havebeendone.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.2 13-JoyfulJourneys||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 -==== =Newfeatures=====5 +==== Minor changes ==== 6 6 7 -* Home - Q&A: The option to search by pressing the Enter key has been added. 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. 8 8 9 -==== =Minorchanges=====18 +==== Bug fixes ==== 10 10 11 -* All - Input fields: Multiple input fields have been updated to expand when the amount of characters exceeds the default size. (#822) 12 -* Design - Message: The tooltip for the optional/required toggle has been improved. (#1172) 13 -* Create - Transformation: UI improvements for static input components have been done. (#1172) 14 -* Create - Resources: A button "Update flows" has been added to update versions of all flows in which a resource is used. (#1129) 15 -* Deploy - Releases: When a new property release is created, this property release can now not only be viewed but also release properties can be deleted. (#1031) 16 -* Deploy - Containers: The error message that is displayed when deleting a runtime is now more descriptive. (#1053) 17 -* Deploy - Runtime overview: Insight into intended and actual deployments has been improved. 18 -* Deploy - Architecture: It is now possible to change the memory settings of a new container before pressing "Apply to environment". (#968) 19 -* Deploy - Architecture: Validation for runtimes that are moved from on premises to the cloud or vice versa has been improved. (#977) 20 -* Deploy - Architecture: The formatting of action messages regarding changes in retention bytes/hours has been improved. 21 -* Manage - Explore: The error messages that may be displayed when using wiretaps and the debugger have been improved. 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) 22 22 23 -==== Bugfixes====29 +==== Remarks ==== 24 24 25 -* Create - Flow Designer: We fixed an issue where it was not possible to remove the last onramp linked to a splitted entry (that was an all-entry before). (#1021) 26 -* Create - Flow Designer: A bug has been fixed where the changes to a component would be reverted if the editing pop-up would be kept open for some minutes without having saved the changes yet. (#1030) 27 -* Deploy - Architecture: During deployments prechecks will be done on runtimes that still have to be deployed from deploy architecture. 28 -* Manage - Monitoring: The correct number of cache hits and misses are now shown in the state generation statistics. (#1161) 29 -* Manage - Monitoring: We fixed an issue where heap memory usage data was accumulating when zooming out in the runtime statistics details dashboards. 30 -* Manage - Explorer: We aligned all timestamp formatting to yyyy-MM-dd HH:mm:ss.SSS. (#1151) 31 -* Manage - Notification settings: Internal recipients are now added correctly. 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)