Skip to Content

Changes for page 204 - Found It

Last modified by Carlijn Kokkeler on 2024/05/22 13:39
From version 46.1
edited by Erik Bakker
on 2023/01/31 14:51
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
Content
... ... @@ -1,40 +1,40 @@
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.
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.191 - Fifty Fifty.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 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 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 to easily wiretap messages from channels in a flow to a queue, which can the 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 which also needs to be reset. Additionally only flows in a container that has the Gen3 Debugging components inside of the associated container infra flow can be debugged. For more information on how to setup debugging on Gen3, please consult the documentation.
10 -* Manage - Alerting: There are 4 new types of triggers available for Model in G3.
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 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 a one or several words which you expect in your logging events.
13 -** Queue Consumers is to configure for queues where more than 1 consumer is expected.
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 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 that are expected to pass through the flow.
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 16  
17 17  =====Minor changes=====
18 18  
19 19  * Data-Limit: Set data limit per environment.
20 -* Login page: Login page /login.html now redirects to the real login page /p/login. (#671)
20 +* Login page: The login page /login.html now redirects to the actual login page /p/login. (#671)
21 21  * Create - Flow designer: Removed the unnecessary refresh button from the component creation pop-ups. (#858)
22 22  * Create - Flow designer: Properties in the property overview pages are sorted as Test/Acceptance/Production. (#804)
23 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 now clearly states which types of Java classes can be used along with some examples. (#742)
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 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 popups of failed machine deployments.
27 -* Deploy - Releases: We added column sorting to the popup showing the missing properties. (#860)
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 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 detail page of the docker container.
30 -* Deploy - Architecture: On the detail page about an instance, the state of the instance is now visible. (#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)
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 33  * Deploy - Properties: We improved runtime selection when copying properties. (#796)
34 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 HTTP statistics dashboard. (#856)
37 -* Manage - Alerting: By default, no filter is applied to Status when navigating to Notifications, or resetting the filters on Notifications. (#486)
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)
38 38  
39 39  
40 40  ====Bug fixes====
... ... @@ -41,11 +41,11 @@
41 41  
42 42  * Design - Solution design: We hide systems without functional integration now. (#714)
43 43  * Create - API Gateway: Security header case insensitive
44 -* Create - Flow designer: Enabling redelivery for you 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 apply 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 visible when container not deployed.
48 -* Manage - Monitoring: Fix typo in Event Proccessors Metrics. (#835)
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)
49 49  
50 50  ====Remarks====
51 51