Skip to Content

Changes for page 216 - Hack Heaven

Last modified by Carlijn Kokkeler on 2024/05/22 13:35
From version 207.1
edited by Erik Bakker
on 2024/03/11 15:35
Change comment: There is no comment for this version
To version 192.1
edited by Carlijn Kokkeler
on 2024/01/29 15:39
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -216 - Hack Heaven
1 +213 - Joyful Journeys
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.ebakker
1 +XWiki.CarlijnKokkeler
Content
... ... @@ -1,34 +1,31 @@
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. On top of that, we launch 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 pop-up messages to improve the user experience. Moreover, we did several alignment & formatting improvements. Lastly, some more feedback items have been solved, and several more bug fixes have been done.
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.213 - Joyful Journeys||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) that are running Windows Server 2022 as an operating system was not possible. Now we have implemented a fix that will allow users to run these multi-environment setups on their Windows Server 2022 machines.
7 7  
7 +* Home - Q&A: The option to search by pressing the Enter key has been added.
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 created by default. (#941)
12 -* Create - Flow designer: Property pop-ups now contain the property name as a text where you can copy the name of the property. (#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: Warning pop-up that is shown when you try to migrate your JMS server to 3rd Generation runtime and there are other containers that need to be migrated first shows the list of other containers. (#1248)
15 -* Deploy - Releases: Implemented some usability improvements 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 infra version. Additionally, the context menu containing the versions also shows a caption now to show what exact component has been right clicked and whose flow versions are showing (entry/exit/onramp/offramp/etc.)
16 -* Deploy - Architecture: Applying to environment or saving your machine is not possible If there is more memory configured than available. (#1144)
17 -* 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)
18 -* Deploy - Architecture: Pending changes will now block continueing after pressing “Apply to environment”, instead of when pressing “Apply Changes” in the next screen. (#606)
19 -* Manage - Monitoring: progress bar is added when users haves long searches on “Log entries”. (#1133)
20 -* Manage - Alerting - Triggers - New: It is now possible to filter across Queues, Topics, Recipients and Runtimes when adding a new trigger. (#1089)
21 -* Manage - Alerting - Alerts: It is now possible to filter the alerts based on the status. (#1176)
22 -* Catalog: Topics are now sorted alphabetically (#1231)
11 +* All - Input fields: Multiple input fields have been updated to expand when the amount of characters exceeds the default size. (#822)
12 +* Design - Message: The tooltip for the optional/required toggle has been improved. (#1172)
13 +* Create - Transformation: UI improvements for static input components have been done. (#1172)
14 +* Create - Resources: A button "Update flows" has been added to update versions of all flows in which a resource is used. (#1129)
15 +* Deploy - Releases: When a new property release is created, this property release can now not only be viewed but also release properties can be deleted. (#1031)
16 +* Deploy - Containers: The error message that is displayed when deleting a runtime is now more descriptive. (#1053)
17 +* Deploy - Runtime overview: Insight into intended and actual deployments has been improved.
18 +* Deploy - Architecture: It is now possible to change the memory settings of a new container before pressing "Apply to environment". (#968)
19 +* Deploy - Architecture: Validation for runtimes that are moved from on premises to the cloud or vice versa has been improved. (#977)
20 +* Deploy - Architecture: The formatting of action messages regarding changes in retention bytes/hours has been improved.
21 +* Manage - Explore: The error messages that may be displayed when using wiretaps and the debugger have been improved.
23 23  
24 24  ====Bug fixes====
25 25  
26 -* Generic: Styling fix has been implemented for the text editor area in some places: QnA forum (posts and answers), Edit store item popup (documentation field) and the Flow > Other > Documentation input field in popup. (#1246)
27 -* Generic: The helptext for the protocols field on the Jetty server and the SSL Web service message sender is now clearer and shows which options are possible. (#1247)
28 -* Create - Transformation: The ‘View’ and ‘Edit’ button under parameters are default behaviour when you are editting. (#1241)
29 -* Create - Transformation: if one attribute rule from “string” to “nonEmptyString” has a filter with type “If exists” and with empty check, then no warning about type incompatible will be generated. For the current transformation with the false positive warnings, clicking “Refresh” button in the right panel will clean them. (#689)
30 -* Create - Flow designer: Components in the left panel of the flow designer are now alphabetically sorted by their name. (#1164)
31 -* Deploy - Property Overview: Resized window such that all property names are not cut off half way. (#1081)
32 -* Deploy - Runtime Overview: Sorting in status is possible. (#1240)
33 -* Deploy - Releases: We fixed a small 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)
34 -* Monitoring - Event streaming statistics: graphs can show up to 30 days.
25 +* Create - Flow Designer: We fixed an issue where it was not possible to remove the last onramp linked to a splitted entry (that was an all-entry before). (#1021)
26 +* Create - Flow Designer: A bug has been fixed where the changes to a component would be reverted if the editing pop-up would be kept open for some minutes without having saved the changes yet. (#1030)
27 +* Deploy - Architecture: During deployments prechecks will be done on runtimes that still have to be deployed from deploy architecture.
28 +* Manage - Monitoring: The correct number of cache hits and misses are now shown in the state generation statistics. (#1161)
29 +* Manage - Monitoring: We fixed an issue where heap memory usage data was accumulating when zooming out in the runtime statistics details dashboards.
30 +* Manage - Explorer: We aligned all timestamp formatting to yyyy-MM-dd HH:mm:ss.SSS. (#1151)
31 +* Manage - Notification settings: Internal recipients are now added correctly.