Skip to Content

Changes for page 216 - Hack Heaven

Last modified by Carlijn Kokkeler on 2024/05/22 13:35
From version 208.1
edited by Erik Bakker
on 2024/03/11 15:39
Change comment: There is no comment for this version
To version 172.1
edited by Carlijn Kokkeler
on 2023/12/21 16:06
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -216 - Hack Heaven
1 +211 - Log Luminary
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.ebakker
1 +XWiki.CarlijnKokkeler
Content
... ... @@ -1,33 +1,24 @@
1 -As part of our alignment week, we also had a hackathon event focusing on a wide array of reported feedback on the portal. The majority of the release blog will be focused on this. In addition, we launched new functionality that makes it easier to transform to JSON, select infra flows in a release, and deploy multiple agents to a single machine that adheres to specific conditions.
1 +In the last sprint cycle, we focused on improving several aspects related overviews and logging. It is now possible to see an overview of all runtimes on running machines, see runtimes and flow versions in the missing properties overview, and see which runtimes will be restarted or redeployed in a pop-up displayed when starting the deployment plan. Moreover, crash handling has been improved, as well as runtime logging and the display of the deployment execution error message. Lastly, several other minor changes and bug fixes have been done, mainly relating to the Deploy and Manage phase.
2 2  
3 -Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.216 - Hack Heaven||target="blank"]].
3 +Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.211 - Log Luminary||target="blank"]].
4 4  
5 5  =====New features=====
6 -* When deploying the on-premise agent for an on-premise machine, users now have the option to select "Multiple environments" when the selected OS type is Windows. This will solve an issue where deploying multiple machines from different environments (machines from Deploy architecture) to the same on-premise machine (the 'physical' machine) running Windows Server 2022 as an operating system was impossible. We have now implemented a fix allowing users to run these multi-environment setups on their Windows Server 2022 machines.
7 7  
7 +* Deploy - Releases: We added the possibility to see the container versions in the release details. This can be viewed by clicking the three dots of the release in the Deploy phase.
8 +
8 8  =====Minor changes=====
9 9  
10 -* Capture - Generic: When deleting a system, tenant, or integration, more information is provided on what you are deleting (#1174)
11 -* Create - Transformation: An optional list in JSON will only create a list if there are items for that list. Otherwise, no list will be made by default. (#941)
12 -* Create - Flow designer: Property pop-ups now contain the property name as a text where you can copy the property's name. (#1175)
13 -* Create - Flow designer: When specifying a cron trigger in an inbound component, the validity of the cron is checked to ensure that no issues with the expression occur after deploying the flow version. (#1165)
14 -* Create - Settings: The warning pop-up is shown when you try to migrate your JMS server to 3rd Generation runtime, and other containers that need to be migrated first show the list of other containers. (#1248)
15 -* Deploy - Releases: Some usability improvements were implemented in Deploy > Releases. Users can now select the flow version of the infra flows (for each pattern respectively) by right-clicking the light-green eMagiz platform component (much like in Create). When the infra flow version has been edited in a release, the platform will color light blue to signify this change in the infra version. The context menu containing the versions also shows a caption to show what exact component has been right-clicked and whose flow versions are showing (i.e., entry, exit, onramp, offramp)
16 -* Deploy - Architecture: When architectural changes are pending in Deploy → Architecture, the screen will not allow edits and show a message that changes are pending. (#1079)
17 -* Deploy - Architecture: Pending changes will now block continuing after pressing "Apply to environment" instead of when pressing "Apply Changes" in the next screen. (#606)
18 -* Manage - Monitoring: A progress bar is added when users have long searches on "Log entries". (#1133)
19 -* Manage - Alerting - Triggers - New: It can now filter across Queues, Topics, Recipients, and Runtimes when adding a new trigger. (#1089)
20 -* Manage - Alerting - Alerts: It is now possible to filter the alerts based on the status. (#1176)
21 -* Catalog: Topics are now sorted alphabetically (#1231)
11 +* Deploy - Releases: When deploying a new release, containers that have no changes between the deployed release and the new release will not be deployed and restarted.
12 +* Deploy - Containers: Changing the list of flows that should run on a container will now trigger the rebuilding of images.
22 22  
23 23  ====Bug fixes====
24 24  
25 -* Generic: Styling fix has been implemented for the text editor area in some places: Q&A forum (posts and answers), Edit store item pop-up (documentation field), and the Flow > Other > Documentation input field in the pop-up. (#1246)
26 -* Generic: The help text for the protocols field on the Jetty server and the SSL Web service message sender is clearer and shows possible options. (#1247)
27 -* Create - Transformation: The 'View' and 'Edit' buttons under parameters are the default behavior when you are editing. (#1241)
28 -* Create - Transformation: if one attribute rule from "string" to "nonEmptyString" has a filter with type "If exists" and with an empty check, then no warning about type incompatible will be generated. Clicking the "Refresh" button in the right panel for the current transformation with the false positive warnings will clean them. (#689)
29 -* Create - Flow designer: Components in the left panel of the flow designer are now alphabetically sorted by their name. (#1164)
30 -* Deploy - Property Overview: Resized window so that all property names are not cut off halfway. (#1081)
31 -* Deploy - Runtime Overview: Sorting in status is possible. (#1240)
32 -* Deploy - Releases: We fixed a minor styling issue when you edit the release by adding/removing the operations to the system in the API pattern. The cursor "Red stop sign "and "Green plus "are showing correctly now. (#788)
33 -* Monitoring - Event streaming statistics: graphs can show up to 30 days.
16 +* Create - Flow Designer: An issue has been fixed where it was not possible to load more store items in the left panel in the Create phase Flow Designer.
17 +* Create - Flow Designer: We improved the help text of the advanced option of ‘max fetch size’ for the mail inbound adapter to better describe how that option affects its behavior. (#1100)
18 +* Deploy - Containers: The collection and publishing of runtime metrics is no longer synchronized across containers, which improves their processing.
19 +* Deploy - Deployment plan: We solved a bug where a deployment step in the deployment plan could randomly get stuck.
20 +* Deploy - Runtimes: We improved the out of memory behavior of runtimes. Runtimes will now always restart when an out of memory error occurs.
21 +* Manage - Alerting: The alert ‘topic approaching maximum size’ alert has been temporarily disabled due to a high number of false positives.
22 +* Manage - Alerting: We solved an issue where the ‘missing metrics’ alert did not always contain the full container name.
23 +
24 +