Skip to Content

Changes for page 225 - Pop-up Party

Last modified by Bouke Reitsma on 2024/07/18 09:55
From version 260.1
edited by Bouke Reitsma
on 2024/06/06 09:20
Change comment: There is no comment for this version
To version 250.1
edited by Carlijn Kokkeler
on 2024/05/21 12:12
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -222 - Flee Frustration
1 +221 - Swift Shift
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.BoukeReitsma
1 +XWiki.CarlijnKokkeler
Content
... ... @@ -1,17 +1,18 @@
1 -In the last sprint cycle, we have worked to allow cron trigggers for hours, days and months prepended by a 0. Moreover, changes in Design that will create or delete runtimes, or impact your model architecture, will trigger a warning before being put into effect in Design Architecture. We have also done several bug fixes, for example, users are not logged out from the portal anymore while deploying. Furthermore, users are now blocked from deploying at the same time on the same environment. Find out about the rest below!
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.222 - Flee Frustration||target="blank"]].
3 +Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.221 - Swift Shift||target="blank"]].
4 4  
5 5  ====New features====
6 -* Design - Architecture: If a user makes changes in Design that will create or delete runtimes, or impact your model architecture, that user will be warned about this before it is put into effect in Design Architecture.
7 7  
8 -====Bug fixes====
9 -* Design - Architecture: The number on the JMS container correctly displays the amount of queues present in Design. (#1284)
10 -* Create - Flow Designer: Property values displayed in the Flow Designer and property values of your active release are now synchronized correctly. (#1053)
11 -* Deploy - Architecture: We have improved machine health calculations to prevent the creation of a machine with invalid memory configurations. (#1282)
12 -* Deploy - Deployment plan: Users are blocked from being logged out during deployment execution, so that triggers are re-enabled after the deployment plan has been executed. (#1293)
13 -* Deploy - Properties: Cron triggers now allow for hours, days and months prepended by a 0, for example 05.
14 -* Deploy - Releases: Users are blocked from deploying at the same time on the same environment on the [[current runtime>>doc:Main.eMagiz Academy.Fundamentals.fundamental-runtime-generation3||target="blank"]] architecture. (#1293)
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".
15 15  
16 -
17 -
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.