Wiki source code of 221 - Swift Shift
Version 250.1 by Carlijn Kokkeler on 2024/05/21 12:12
Hide last authors
author | version | line-number | content |
---|---|---|---|
![]() |
247.1 | 1 | In the last sprint cycle, we have worked on . |
![]() |
1.1 | 2 | |
![]() |
247.1 | 3 | Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.221 - Swift Shift||target="blank"]]. |
![]() |
35.1 | 4 | |
![]() |
250.1 | 5 | ====New features==== |
![]() |
241.1 | 6 | |
![]() |
247.1 | 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". | ||
![]() |
230.1 | 14 | |
![]() |
249.1 | 15 | ====Bug fixes==== |
![]() |
247.1 | 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. |