Changes for page 225 - Pop-up Party
Last modified by Bouke Reitsma on 2024/07/18 09:55
From version 28.1
edited by Erik Bakker
on 2022/11/24 11:26
on 2022/11/24 11:26
Change comment:
There is no comment for this version
To version 247.1
edited by Carlijn Kokkeler
on 2024/05/21 12:11
on 2024/05/21 12:11
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 -1 88-CloseEncounters1 +221 - Swift Shift - Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki. ebakker1 +XWiki.CarlijnKokkeler - Content
-
... ... @@ -1,21 +1,18 @@ 1 - Thereleasebringsseveral improvements to our 3rd generationruntimeand its interaction with the portal. On top of that, we haveseveral feedbackitems andbug fixes.1 +In the last sprint cycle, we have worked on . 2 2 3 -Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.1 88-CloseEncounters.WebHome||target="blank"]].3 +Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.221 - Swift Shift||target="blank"]]. 4 4 5 -===== Minorchanges=====5 +===== New features ===== 6 6 7 -* General: Code mapping is now available for models migrating to the 3rd generation runtime. 8 -* General: Added functionality that allows you to search by pressing "Enter" on various pages across the platform. (#785) 9 -* Store: Renamed several display names across the Store functionality to better clarify what the functionality does for you. 10 -* Deploy - Deployment plan: When a runtime is being deployed, which is constantly crashing and thereby causing problems, the restart of the runtime is limited to just five times. (#720) 11 -** After five times, the runtime will remain in the stopped state. 7 +* Q & A: Search results are now persisted when pressing the back button after opening a question in the community Q & A. (#1324) 8 +* Catalog: We have significantly improved the Event Catalog overview by introducing a much simpler layout for easier navigation. 9 +* Design - CDM/System message: A new attribute will be placed right below the attribute that users right-clicked on to open context menu to add a new attribute. (#151) 10 +* Design - System message: Moving an attribute in the datamodel is now directly shown in the tree structure as well. (#151) 11 +* Design - CDM/API Data model/ES data model and system message: The pop-up that appears when rearranging attributes of an entity will result in a pop-up which text is conditional with respect to the messagetype. (#151) 12 +* Deploy - Deploy release: When executing a start/stop action on a group, the description of the step now contains the name of the group. 13 +* Deploy - Architecture: When stopping a group with the follower status, the description of the popup now correctly describes the purpose of button "Disable failover and stop group". 12 12 13 -====Bug fixes==== 14 -* Create - Flow designer: Resetting the JMS server sometimes resulted in invalid connection settings for connecting to the failover JMS server. (#717) 15 -* Create - Flow designer: Newly generated flows were configured with incorrect XSD or XLST resource locations under specific circumstances. (#718) 16 -* Deploy - Architecture: Prechecks for cloud template upgrades failed unexpectedly under particular circumstances. (#703) 17 -* Manage - Runtime statistics: Data measurements of eMagiz-Mendix Connector runtimes are not missing anymore. 18 -* Manage - Error Dashboard: Solved a problem that caused a user to see a general error when opening the Manage Dashboard while running a 3rd generation runtime architecture. 19 - 20 -====Remarks==== 21 -* Mendix Runtime has been upgraded to Mendix 9.19.0. 15 +===== Bug fixes ===== 16 +* Design - System messages: When importing an xsd to a new response or request message, you will not receive a warning message anymore to avoid confusion. (#140) 17 +* Deploy - Containers: The delete behaviour of containers in the container overview has been improved. (#1053) 18 +* Deploy - API Gateway: We fixed an issue where the generation of scope properties was incorrect for legacy API gateway runtimes using OAuth 2.0 security scheme.