Skip to Content

Changes for page 208 - Controlled State

Last modified by Carlijn Kokkeler on 2024/05/22 13:37
From version 154.14
edited by Danniar Firdausy
on 2023/11/07 12:08
Change comment: There is no comment for this version
To version 57.1
edited by Erik Bakker
on 2023/03/14 08:31
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -208 - Controlled State
1 +194 - Giant Leap
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.dfirdausy
1 +XWiki.ebakker
Content
... ... @@ -1,30 +1,24 @@
1 -In the last sprint cycle, we focused on delivering monitoring functionality for the state generation components. On top of that, we also made several improvements on 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.
1 +The release introduces various improvements on our 3rd generation runtime architecture and various other fixes in other parts of the portal. Subsequently, we will release a new runtime image supporting the various improvements.
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.194 - Giant Leap.WebHome||target= "blank"]].
4 4  
5 +=====New features=====
6 +
7 +* A new runtime image for customer models running on the 3rd generation runtime. Please learn more about our [[Runtime Image release notes>>Main.Release Information.Runtime Images.V130.WebHome||target="blank"]].
8 +* Design - Settings: We added XML support to API Management. To enable this feature, change the 'Default message format' in the Design settings section. You can change individual operations by changing the message format of your gateway message. Migrating existing operations requires a reset of the exit flow and a change in the catalog in Design. For more information, see the release blog post. (#815)
9 +* Deploy - Releases: New release properties pop-up that shows all properties in your release, grouped by containers that they are assigned to. This pop-up can be accessed by pressing the wrench-shaped icon, which becomes available once a release is set as active.
10 +
5 5  =====Minor changes=====
6 6  
7 -* Design - Message Mapping: The button 'Import from Store' will directly open the store.
8 -* Create - Flow Designer: Input fields for XPath expressions have been made wider and capable of expanding to facilitate longer inputs.
9 -* Create - Flow Designer: Small styling changes and bugfixes have been implemented for edge-cases during editing channels in the Flow Designer.
10 -* Deploy - Releases: During removing a release, users will be informed about the environments and the runtimes in which the release under deletion is running.
11 -* Deploy - Releases: When a release is removed, the related unused images in the on-premises machines will be removed as well.
12 -* Deploy - Deployment: The preparing step of the release at the begining of the deployment is now faster due to the improved process in building the images.
13 -* Manage - Monitoring: There is a new page called the "State generation statistics" that is located right under the Topic statistics navigation menu, which is only shown and accessible for models that has the add-on license for state generation.
14 -* 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 phrase.
15 -* Manage - Triggers: When creating a new trigger the order of the cancel and next buttons has been switched.
16 -* 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.
17 -* 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.
13 +* Design - API Gateway: OData API type exclusively selectable for system admin. (#816)
14 +* Design - API Catalog: When you change a path in the Design phase, your HTTP inbound gateways that use the changed path will also be updated in Create phase if you have edit rights. (#524)
15 +* 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.
16 +* Manage - Error messages: Message history is sorted by timestamp descending.
18 18  
19 19  ====Bug fixes====
20 20  
21 -* 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)
22 -* Deploy - Architecture: Containers are set inactive when they are removed in Design and unused.
23 -* Deploy - Deployment: We fixed an issue that the deployment plan got stuck or stopped randomly sometimes.
24 -* Deploy - Deployment: We resolved an issue where sometimes older containers get deployed, while eMagiz shows the new containers are deployed.
25 -* Manage - Monitoring: Improved message processing in infra components that should reduce the occurance of log messages failed to be sent in Gen3 models.
26 -
27 -
28 -=====Infra and image changes=====
29 -
30 -* 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.
20 +* Create - Message Definition: Attribute can be declared as JSON array in API Gateway and Event Streaming. (#908)
21 +* Create - Migration: We fixed a third-generation migration issue where the legacy error handling flow components were not removed from the asynchronous routing flow.
22 +* Create - Flow designer: when migrating a container’s flows from gen2 to gen 3, “global wire tap” components and their relevant components will be removed.
23 +* Deploy - Release: We fixed an issue that caused images not to be built in specific situations when running in the new runtime generation runtime.
24 +* Deploy - User management: Fixed an issue where 'Apply to environment' would take very long to finish. (#797)