Changes for page 208 - Controlled State
Last modified by Carlijn Kokkeler on 2024/05/22 13:37
From version 154.3
edited by Danniar Firdausy
on 2023/11/07 11:46
on 2023/11/07 11:46
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 - 208 -Controlled State1 +185 - Get Ready - Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki. dfirdausy1 +XWiki.eMagiz - Content
-
... ... @@ -1,24 +1,22 @@ 1 - In thesprintcycle, we focusedon deliveringmonitoringfunctionalityforthestate generationcomponents. On top of that, we also made severalimprovementson thecomponentsinterfacingtheusersto improvetheuserexperiencepectof our platform. Moreover, we madesomebugfixes andimprovements on releases in Deploy and monitoring in Manage.1 +Release that updates the manage statistics sections for our new monitoring stack. On top of that, we have released a new cloud template and released several other functionalities. 2 2 3 -Please find out more on our [[Release blog>>Main.Release Information.Release Blogs. 208 -Controlled State.WebHome||target="blank"]].3 +Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.185 - Get ready.WebHome||target="blank"]]. 4 4 5 +=====New features===== 6 +* Deploy - User Management: Before and after applying to environment, keep track of user management changes. Export history as an excel file. 7 + 5 5 =====Minor changes===== 6 6 7 -* Design - MessageMapping:Thebutton 'ImportfromStore'will directlyopenthe store.8 -* Create- FlowDesigner:Performance improvementsfor the FlowDesignerhavebeenimplemented.9 - *Deploy-Releases: When a release is removed,the relatedunused images in the on-premises machines will be removed as well.10 - *Manage-Monitoring: There is a new page calledthe"Stategenerationstatistics"that islocatedright under the Topic statistics navigation menu,which isonlyshown and accessible formodels that has the add-on license for state generation.11 -* Ma nage- Triggers:Whencreatinga new triggertheorderofthecanceland nextbuttons has beenswitched.12 -* All-Buttons:Theave and cancel buttonsareplacedslightlyfurtherapartto avoidmisclicking.(#1022)10 +* Design System. Changed the look and feel across the portal altogether. Changes can be seen in: 11 + ** Datagids, where there is now on hover action for example. 12 + ** Pop ups 13 + ** Context menus, also have on hover action 14 +* Message Redelivery - admin logs improved to better analyze issues when they occur 15 +* Create - Flow Designer: small bugs ( copy/paste by keyboard, copy annotation, display interceptors and queue channels) are fixed 13 13 14 14 ====Bug fixes==== 15 - 16 -* Create & Deploy - Styling: The styling of the event streaming canvas in the Create and Deploy phases has been slightly altered to make topic and event-processor names more readable. (#1055) 17 -* Deploy - Architecture: Containers are set inactive when they are removed in Design and unused. 18 -* Deploy - Releases: We fixed an issue that a lot of error popups were shown when you promoted a release version to a next environment. (#1087) 19 -* Manage - Triggers: Besides checking the error header, the error trigger is configured to check if an error message contains a term. 20 - 21 - 22 -=====Infra and image changes===== 23 - 24 -* State generation: New state generation features have been added. Please check out [[V2.0.0>>https://docs.emagiz.com/bin/view/Main/Release%20Information/Runtime%20Images/V2.0.0/]] from the [[runtime images>>Main.Release Information.Runtime Images||target="blank"]] for more information. 18 +* Deploy - Deployment plan. Performance of page to deploy a release increases significantly 19 +* Store - Import resources was incorrectly done in specific cases, which is now fixed 20 +* Store - Target namespace will be imported when imported XML Message Definition 21 +* Store - When exporting components, if property values contains bus name, they will be updated automatically with new bus name when importing into a new bus. 22 +* Store: Importing items from the store sometimes resulted in invalid JMS connection factories.