Skip to Content

Changes for page 208 - Controlled State

Last modified by Carlijn Kokkeler on 2024/05/22 13:37
From version 96.1
edited by Erik Bakker
on 2023/06/22 13:26
Change comment: There is no comment for this version
To version 157.1
edited by Danniar Firdausy
on 2023/11/07 13:08
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -200 - Uncharted Territories
1 +208 - Controlled State
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.ebakker
1 +XWiki.dfirdausy
Content
... ... @@ -1,27 +1,23 @@
1 -In the last sprint cycle, we focused on improving various aspects of the portal functionality. Among others, we focused on the next-generation architecture and others.
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.200 - Uncharted Territories.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 -* Create - Flow Designer: it is possible to select multiple components by area selection on the area with a scrollbar.
8 -* Create - Flow designer: The new best practices have updated Kafka components' default values. Updated values are:
9 -** For Kafka templates:
10 -*** Batch size: 200000
11 -*** Linger: 300
12 -** For Kafka message listener containers
13 -*** Fetch min. amount: 100000
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 - Triggers: When creating a new trigger the order of the cancel and next buttons has been switched.
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.
14 14  
15 -{{warning}}The existing Kafka components in your flows will automatically be updated with the new best practice values. To make deploying these changes more effortless for you, we will create a new version of your flows after updating the values (versions will be created in the name of model contacts) and transfer them to the Deploy phase. You can then create and deploy a new release with updated flow versions.{{/warning}}
16 -
17 -* Deploy - Cloud Templates: New Cloud Templates are available for single-lane and double-lane environments. Please check out the cloud template [[release notes>>Main.Release Information.Cloud Templates.WebHome||target="blank"]] for more information.
18 -* Deploy - Architecture: We removed the deprecated reminder popup to update your cloud slot template. The automated upgrade feature replaces it alongside the "Upgrade" functionality in Deploy - Architecture.
19 -* Deploy - Deployment plan: We updated the right pane of the deployment plan to make it more compatible with the new runtime generation. Now, you can see all related logs regarding your deployment. By default, we only show some necessary logs, such as error logs, warning logs, and started runtime information logs. You can use the filter logs icons at the top of the list to show more information.
20 -* Deploy - Deployment plan: We updated the logic within our deployment plan functionality. The deployment step that disables all enabled triggers from the Manage phase disables triggers till you exit the deployment plan overview. That means that those triggers will be re-enabled after you move away from the deployment process or close the browser. Furthermore, there is no deployment step configuration to "enable" triggers anymore.
21 -
22 22  ====Bug fixes====
23 23  
24 -* Deploy - Architecture: We improved timeout settings to give Stop, Restart, and Reset runtime actions enough time to execute. (#957)
25 -* Design - Store: Importing into "Design" from the store is possible, even if the integration is not in Create yet.
26 -* Manage - Monitoring: Detailed HTTP statistics will now show the correct user in case of API key authorization in more cases. Note that this functionality requires a newly deployed release. (#956)
27 -* 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.
23 +