Skip to Content

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
Change comment: There is no comment for this version
To version 47.1
edited by Erik Bakker
on 2023/01/31 14:56
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -208 - Controlled State
1 +191 - Fifty Fifty
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.dfirdausy
1 +XWiki.ebakker
Content
... ... @@ -1,29 +1,53 @@
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 a lot of minor 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 - Controlled State .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 +=====New features=====
6 +* Deploy - Architecture: We added the possibility to register network shares in your container volume settings. This enables the use of network shares without having to mount them manually on the host machine and then again on the container level. This option is only available for 3rd generation runtimes that run on-premises.
7 +* Deploy - Containers: In Deploy containers, a 'Debug' option is added for flows on the 3rd generation eMagiz runtime.
8 +** This option will temporarily be available for users on the next generation runtime. It allows one to easily wiretap messages from channels in a flow to a queue, which can then be browsed using the queue browser. One flow can be wiretapped at the time per container.
9 +** To use this option, the model must be fully migrated to Gen3, including the JMS. Additionally, only flows in a container with the Gen3 Debugging components inside the associated container infra flow can be debugged. Please consult the documentation for more information on how to set up debugging on Gen3.
10 +* Manage - Alerting: Five new triggers are available for Model in G3.
11 +** Error Message is to evaluate the headers of the original message which resulted in an error.
12 +** Log Keyword is to evaluate logging messages. You can provide one or several words which you expect in your logging events.
13 +** Queue Consumers is to check whether more than one consumer is expected on the queue level.
14 +** Queue Messages is to configure for queues where more than 100 messages on a queue can occur
15 +** Queue Throughput is to monitor issues with your system by setting thresholds for the number of messages expected to pass through the flow.
16 +
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.
19 +* Data-Limit: Set data limit per environment.
20 +* Login page: The login page /login.html now redirects to the actual login page /p/login. (#671)
21 +* Create - Flow designer: Removed the unnecessary refresh button from the component creation pop-ups. (#858)
22 +* Create - Flow designer: Properties in the property overview pages are sorted as Test/Acceptance/Production. (#804)
23 +* Create - Flow designer: We improved validation and help text on Wss4J interceptors components. (#733)
24 +* Create-Flow testing: Improved the help text when adding a header type for a test message. It clearly states which Java classes can be used, along with some examples. (#742)
25 +* Deploy - Releases: Setting a release as active by pressing the deploy button creates an entry in the deploy history. (#823)
26 +* Deploy - Releases: We improved the notification pop-ups of failed machine deployments.
27 +* Deploy - Releases: We added column sorting to the pop-up showing the missing properties. (#860)
28 +* Deploy - Architecture: New cloud slots have their auto-upgrade value set to true by default. (#841)
29 +* Deploy - Architecture: A docker container's status is more visible when you open the detail page of the docker container.
30 +* Deploy - Architecture: The instance's state is now visible on the detail page about an instance. (#699)
31 +* Deploy - Architecture: We changed the wake-up time of cloud slots on Fridays to 6:00 UTC so that they no longer fall within our regular deployment windows. (#559)
32 +* Deploy - Architecture: We added runtime memory checks to 'Apply to environment' to prevent invalid deployments. (#719)
33 +* Deploy - Properties: We improved runtime selection when copying properties. (#796)
34 +* Manage - Explore: Improved the displayed error message when a message could not be loaded in the message redelivery screen. (#696)
35 +* Manage - Explore: "Save as test message" button opens a pop-up that allows you to edit your test message's name, description, content, and headers before saving it.
36 +* Manage - HTTP statistics: Fixed a typo in the HTTP statistics dashboard. (#856)
37 +* Manage - Alerting: By default, no filter is applied to the status when navigating to the "Notifications" overview or resetting the filters on the "Notifications" overview. (#486)
17 17  
39 +
18 18  ====Bug fixes====
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.
42 +* Design - Solution design: We hide systems without functional integration now. (#714)
43 +* Create - API Gateway: Security header case insensitive
44 +* Create - Flow designer: Enabling redelivery for your integration is applied after resetting your offramp and exit flow. Before this change, you needed to remove and add the integration to Create phase to use this setting.
45 +* Deploy - Containers: Applied styling to the error pop-up with the list of reasons why a runtime can't be deleted to make it easier to read. (#546)
46 +* Deploy - Architecture: Deploying your model to the cloud for the first time required you to press 'Apply to Environment' twice. This is no longer the case. (#508)
47 +* Deploy-Volumes: Network volumes are visible when the container is not deployed.
48 +* Manage - Monitoring: Fix typo in Event Processors Metrics. (#835)
25 25  
50 +====Remarks====
26 26  
27 -=====Infra and image changes=====
52 +* Mendix Runtime has been upgraded to Mendix 9.21.0.
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.