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
on 2023/11/07 12:08
Change comment:
There is no comment for this version
To version 43.1
edited by Erik Bakker
on 2023/01/18 11:41
on 2023/01/18 11:41
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-ControlledState1 +190 - Fast Forward - Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki. dfirdausy1 +XWiki.ebakker - Content
-
... ... @@ -1,30 +1,32 @@ 1 - In the last sprint cycle,wefocusedondeliveringmonitoringfunctionalityforthestategenerationcomponents.On top ofthat, we also madeseveral improvementsonthe componentsinterfacingtheuserstoimprove the user experienceaspectof ourplatform. Moreover, wemade somebug fixesandimprovementsonreleasesinDeployand monitoringinManage.1 +The release finished many new improvements to our 3rd generation runtime offering and fixed various annoying bugs and minor enhancements. Furthermore, we introduce several improvements in the interaction with the portal. 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.190 - Fast Forward.WebHome||target="blank"]]. 4 4 5 -=====Minor changes===== 5 +=====New features===== 6 +* A new runtime image for customer models running on the 3rd generation runtime. Please find out more on our [[Runtime Image release notes>>Main.Release Information.Runtime Images.V110.WebHome||target="blank"]]. 7 +* Manage - Explore: The Queue browser is a new feature that enables you to explore the queues on your JMS server and view (and delete) the message on them. It is only available if you migrated your JMS server to the 3rd generation runtime. 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. 9 +=====Major changes===== 18 18 19 - ====Bug fixes====11 +* Manage - Redelivery: You can explore the message redelivery functionality for the 3rd generation architecture and see more details about it. Besides that, you can also redeliver the message(s) on this page. 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. 13 +=====Minor changes===== 26 26 15 +* Design - System message: 'Request' and 'Response' entities are automatically generated and set as root entities for new SOAP web service integrations in 3rd generation runtimes. 16 +* Create - Flow designer: sensitive information stored in property values is masked. (#790) 17 +* Create - Flow Designer: when migrated from Gen2 to Gen3, the flow's JSON will be generated so the user can use it to compare the previous versions. 18 +* Create - Flow Designer: when importing a store item from another partner, an error popup will be shown instead of the default error message. 19 +* Deploy - Releases: The activate release functionality improved performance for 3rd generation models. 20 +* Deploy - Architecture: Before pressing "Apply to environment," we require a confirmation from you if you accept the topology changes suggested by eMagiz that might impact AWS. (#828) 21 +* Deploy - Architecture: We enabled setting memory limits for eMagiz runtimes running on Docker machines. (#571) 22 +* Deploy - Architecture: "HTTP settings" page changed to "Runtime settings," where you can enable/disable both HTTP and control bus per runtime. 23 +* Deploy - Releases - You will be reminded of empty runtimes when activating a release. Empty runtimes are runtimes without flows in the release, and these runtimes should be removed from your architecture. 27 27 28 -=====Infra and image changes===== 25 +====Bug fixes==== 26 +* Design-CDM: cannot break definition when setting cardinality to '*' if the parent entity has order matters set to 'No' (#508) 27 +* Create - Flow Designer: When copying and pasting, support objects such as "property placeholder," "support.bus-connection-caching," and "support. bus-connection-plain" are not duplicated (#793) 28 +* Create - Flow Designer: when importing a store item, it is possible to overwrite the value of properties in the setup step. 29 +* Deploy - Containers: We fixed an issue that the container overview does not show the entry flows which should run on that container. (#863) 30 +* Deploy - Architecture: Apply to environment button synchronizes event streaming topic states correctly. (#814) 31 +* Deploy - Architecture: The deploy runtimes option is only visible for admin. A new menu item, "Deploy agent," is added and visible for all users to show the command which can be used to deploy the agent to an on-premises machine. 29 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.