Changes for page 225 - Pop-up Party
Last modified by Bouke Reitsma on 2024/07/18 09:55
From version 248.1
edited by Carlijn Kokkeler
on 2024/05/21 12:12
on 2024/05/21 12:12
Change comment:
There is no comment for this version
To version 260.1
edited by Bouke Reitsma
on 2024/06/06 09:20
on 2024/06/06 09:20
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 -22 1-SwiftShift1 +222 - Flee Frustration - Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki. CarlijnKokkeler1 +XWiki.BoukeReitsma - Content
-
... ... @@ -1,18 +1,17 @@ 1 -In the last sprint cycle, we have worked on . 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! 2 2 3 -Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.22 1-SwiftShift||target="blank"]].3 +Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.222 - Flee Frustration||target="blank"]]. 4 4 5 -=====New features===== 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. 6 6 7 - * Q & A: Search results are now persisted when pressingthe back button after opening a question in the community Q & A. (#1324)8 -* Catalog: Wehavesignificantly improvedtheEventCatalogoverviewbyintroducinga muchsimplerlayoutforeasier navigation.9 -* Design-CDM/System message:A new attributewill be placedrightbelowtheattributethatusers right-clickedontoopencontextmenu toadda newattribute. (#151)10 -* De sign-Systemmessage:Movinganattributein thedatamodelisnowdirectlyshowninthetreestructureaswell. (#151)11 -* De sign-CDM/API Data model/ES data modelandsystem message:Thepop-upthat appears whenrearrangingattributesof an entitywill resulta pop-upwhichtextisconditionalwithrespecttothemessagetype. (#151)12 -* Deploy - Deployrelease:Whenexecutinga start/stopactionnagroup,thedescription ofthestepow contains thenameofthegroup.13 -* Deploy - Architecture:Whenstoppingagroupwith the followerstatus,thedescriptionofthepopupnow correctlydescribesthepurposeof button"Disableilovernd stopgroup".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) 14 14 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. 16 + 17 +