Skip to Content

Changes for page 208 - Controlled State

Last modified by Carlijn Kokkeler on 2024/05/22 13:37
From version 97.1
edited by Erik Bakker
on 2023/07/17 15:25
Change comment: There is no comment for this version
To version 158.1
edited by Danniar Firdausy
on 2023/11/08 13:41
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -201 - Be Informed
1 +208 - Controlled State
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.ebakker
1 +XWiki.dfirdausy
Content
... ... @@ -1,30 +1,23 @@
1 -In the last sprint cycle, we focused on planning ahead, finishing up and working on the Hackathon to fix several smaller items.
1 +In the last sprint cycle, we focused on providing users with a monitoring functionality for the state generation components. On top of that, we also made several improvements to the components interfacing the users to improve the user experience aspect of our platform. Moreover, we made some bug fixes and improvements on releases in Deploy and monitoring in Manage.
2 2  
3 -Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.201 - Be Informed.WebHome||target= "blank"]].
3 +Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.208 - Controlled State .WebHome||target="blank"]].
4 4  
5 5  =====Minor changes=====
6 6  
7 -* Portal - Menu: the back button is changed to have text so it shows clearer the navigation target. (#949)
8 -* Design-Architecture: Topic Storage detail page contains help text. (#994)
9 -* Design - API Endpoint Specification: Improved UI and added independent scroll functionality. (#832)
10 -* Design - API Gateway: Small styling improvements to the edit integration page. (#954)
11 -* Create - Flow Designer: When deleting one or multiple components, you will not be able to change the selection before confirming or cancelling the delete action. (#969)
12 -* Create - Migrate to 3rd Generation: In the event one or more flows break during migration, a popup will inform the fows containing errors after migration is finished. (#983)
13 -* Deploy-User management: The user that makes a change is recorded in history instead of the user that applies to environment. (#979)
14 -* Deploy-Architecture: Upon pressing the button “Apply to environment”, a confirmation page is shown. Here all changes made in the portal that will have an effect in your running environment are listed. These changes can be applied to environment or reverted. (#828)
15 -** Changes made in Deploy Architecture with an effect to your running environment will only be listed when they are made after this release.
16 -** Changes with a direct effect will not be listed (for example restarting a machine).
7 +* Create - Flow Designer: Input fields for XPath expressions have been made wider and capable of expanding to facilitate longer inputs. (#822)
8 +* Create - Flow Designer: Small styling changes and bug fixes have been implemented for edge cases during editing channels in the Flow Designer.
9 +* Deploy - Releases: During removing a release, users will be informed about the environments and the runtimes in which the release under deletion is running. (#1060)
10 +* Deploy - Releases: When a release is removed, the related unused images in the on-premises machines will be removed as well.
11 +* Deploy - Deployment: The “preparing” step of the release at the beginning of the deployment is now faster due to the improved process of building the images.
12 +* Manage - Monitoring: There is a new page called "State generation statistics" that is located right under the Topic statistics navigation menu, which is only shown and accessible for models that have the add-on license for state generation.
13 +* Manage - Error messages & Log entries: Searching on entries now supports phrase matching, meaning that users can search entries based on phrases containing two or more words and entries with distances of 2 or incomplete search phrases.
14 +* Manage - Alerting: In Alerts, the previous "Source" column is renamed to "Source trigger" and its value is derived from the type of trigger which generates alert.
15 +* All - Toggles: We updated all instances of the toggle switch in the platform due to the latest eMagiz Design System module implementation in our platform.
16 +* All - Error Channel: Added a migration step in Gen3 migration, we set the error channel to “errorChannel” of all inbounds in a flow if the custom error handling is set to false.
17 17  
18 18  ====Bug fixes====
19 19  
20 -* Design - Solutions: We fixed an issue that a message mapping error is displayed despite having a passthrough API gateway. (#935)
21 -* Design - Settings: The full length of the contract number can now be registered. (#958)
22 -* Create - Migrate to 3rd Generation: Components used in Gen 2 flows that can be used in Gen3 will not block migration. (#982)
23 -* Deploy - Deployment plan: We fixed an issue that the list of installing flows did not show in the left pane when you deploy a release version to install/start/stop some flows into you runtimes. (#990)
24 -* Deploy - User Management: As a user with view-only rights in Deploy/User management, you can now double click on a user to open its details. (#972)
25 -* Manage - Manage Dashboards: The screen loading speed is significantly improved for all models. This is most noticeable for larger models. (#964)
20 +* Deploy - Deployment: We fixed an issue that the deployment plan got stuck or stopped randomly sometimes.
21 +* Deploy - Deployment: We resolved an issue where sometimes older containers get deployed, while eMagiz shows the new containers are deployed.
22 +* Manage - Monitoring: Improved message processing in infra components that should reduce the occurrence of log messages failing to be sent in Gen3 models.
26 26  
27 -=====Infra and image changes=====
28 -
29 -* Changed the endpoint that is used for sending errormessages to the eMagiz Control Tower.
30 -* Updated the Spring version of the gateway supporting deploy and manage phase operations.