Changes for page 208 - Controlled State
Last modified by Carlijn Kokkeler on 2024/05/22 13:37
From version 154.13
edited by Danniar Firdausy
on 2023/11/07 12:07
on 2023/11/07 12:07
Change comment:
There is no comment for this version
To version 45.1
edited by Erik Bakker
on 2023/01/31 14:39
on 2023/01/31 14:39
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 +191 - Fifty Fifty - Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki. dfirdausy1 +XWiki.ebakker - Content
-
... ... @@ -1,29 +1,36 @@ 1 - In thelast sprint cycle, we focusedon delivering monitoring functionality for thetategenerationcomponents.On top ofthat,we alsomadeseveral improvementsonthecomponentsinterfacingtheusers toimprovetheuserexperienceaspectof our platform.Moreover, we made somebug fixesandimprovementson releases inDeployand monitoringin Manage.1 +The release introduces a lot of small fixes as a result of our "hackathon" efforts. Subsequently we will release several 3rd generation runtime offerings. 2 2 3 -Please find out more on our [[Release blog>>Main.Release Information.Release Blogs. 208-ControlledState.WebHome||target="blank"]].3 +Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.191 - Fifty Fifty.WebHome||target="blank"]]. 4 4 5 -=====Minor changes===== 5 +=====New features===== 6 +* Manage - Alerting: There are 4 new types of triggers available for Model in G3. 7 +** Error Message is to evaluate the headers of the original message which resulted in an error. 8 +** Log Keyword is to evaluate logging messages. You can provide a one or several words which you expect in your logging events. 9 +** Queue Consumers is to configure for queues where more than 1 consumer is expected. 10 +** Queue Messages is to configure for queues where more than 100 messages on a queue can occur 11 +** Queue Throughput is to monitor issues with your system by setting thresholds for the number of messages that are expected to pass through the flow. 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. 13 +=====Major changes===== 17 17 18 - ====Bug fixes====15 +* 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. 19 19 20 -* 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) 21 -* Deploy - Architecture: Containers are set inactive when they are removed in Design and unused. 22 -* Deploy - Deployment: We fixed an issue that the deployment plan got stuck or stopped randomly sometimes. 23 -* Deploy - Deployment: We resolved an issue where sometimes older containers get deployed, while eMagiz shows the new containers are deployed. 24 -* Manage - Monitoring: Improved message processing in infra components that should reduce the occurance of log messages failed to be sent in Gen3 models. 17 +=====Minor changes===== 25 25 19 +* 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. 20 +* Create - Flow designer: sensitive information stored in property values is masked. (#790) 21 +* 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. 22 +* Create - Flow Designer: when importing a store item from another partner, an error popup will be shown instead of the default error message. 23 +* Deploy - Releases: The activate release functionality improved performance for 3rd generation models. 24 +* 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) 25 +* Deploy - Architecture: We enabled setting memory limits for eMagiz runtimes running on Docker machines. (#571) 26 +* Deploy - Architecture: "HTTP settings" page changed to "Runtime settings," where you can enable/disable both HTTP and control bus per runtime. 27 +* 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. 26 26 27 -=====Infra and image changes===== 29 +====Bug fixes==== 30 +* Design-CDM: cannot break definition when setting cardinality to '*' if the parent entity has order matters set to 'No' (#508) 31 +* 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) 32 +* Create - Flow Designer: when importing a store item, it is possible to overwrite the value of properties in the setup step. 33 +* Deploy - Containers: We fixed an issue that the container overview does not show the entry flows which should run on that container. (#863) 34 +* Deploy - Architecture: Apply to environment button synchronizes event streaming topic states correctly. (#814) 35 +* 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. 28 28 29 -* 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.