Changes for page 216 - Hack Heaven

Summary

• Page properties (3 modified, 0 added, 0 removed)

Details

Page properties

Title

...	...	@@ -1,1 +1,1 @@
1		-216 - Hack Heaven
	1	+207 - Aligned State

Author

...	...	@@ -1,1 +1,1 @@
1		-XWiki.ebakker
	1	+XWiki.CarlijnKokkeler

Content

...	...	@@ -1,34 +1,46 @@
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 delivering state generation components. On top of that, we made several improvements regarding the alignment of components, and did some performance improvements and bug fixes. Moreover, we made a change in the metrics storage duration.
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.207 - Aligned State .WebHome||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.
	6	+* State generation: New state generation features have been added. Please check out [[V2.0.0>>Main.Release Information.Runtime Images.V200||target="blank"]] from the [[runtime images>>Main.Release Information.Runtime Images||target="blank"]] for more information.
7	7
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)
	10	+* Design - Channels: Moving already attached channels in the flow designer has been made sligthly easier. (#845)
	11	+* Create - Framework: The framework used in the flow designer has been updated, improving performance.
	12	+* Deploy - Architecture: The description users see when adapting the topic retention size has been changed to be less confusing.
	13	+* Deploy - Deployment plan: The algorithm for genarating a default deployment plan is improved to keep JMS downtime and alerting to a minimum. (#1009)
	14	+* Deploy - Deployment plan: A change in the memory settings of a container triggers a redeployment of the container. (#993)
	15	+* Deploy - Properties: We removed the deprecated tab Properties in the Deploy phase.
	16	+* Deploy - Release properties: The description of a property can be changed by editing the property. (#1064)
	17	+* Deploy - Release: The start/stop/restart machine deployment steps are now also executed correctly for AWS and on-premises machines.
	18	+* Deploy - Release: When a release is removed, the related unused images in the on-premises machines will be removed as well.
	19	+* Deploy - Release: Performance improvements have been implemented for loading releases in Deploy.
	20	+* Manage - Alerting: If alerting has been paused manually, it will not be activated automatically after a release deployment. (#1024)
	21	+* Manage - Alerting: Inactivated users should be removed from all alert settings (including “disabled“ settings) to avoid undesirable notifications.
	22	+* Manage - Monitoring: Graphs showing problematic runtimes, queues and requests have been updated to be sorted by “Process CPU usage”, “Messages in queue” and “Unsuccessful requests” by default respectively for 3rd generation runtimes. (#1069)
	23	+* Manage - Monitoring: The 3rd generation runtime dashboards have been changed to show data on UTC time zone by default. (#1070)
	24	+* Manage - Monitoring: Variables in the 3rd generation runtimes HTTP statistics detail pages are now sorted case insensitive. (#1063)
	25	+* Administration - My account: When an account password change request is made, even when this fails, a mail is sent to the account owner to inform on the action.
	26	+* Administration - My account: When changing a password, it is compared to a list of known database breaches for security. A warning is shown when the password is found in a database.
23	23
	28	+
	29	+
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.
	32	+* Design - Store: We fixed an issue that blocked you from importing Store content in the Design phase. The message definitions and message mappings are now imported correctly as the original content in the item of the Store.
	33	+* Design - Store: We fixed an issue that the orders of message definition elements were changed after being imported.
	34	+* Design - Store: We fixed an issue that importing a store item with synchronous message definitions went wrong. Now, the imported message definitions should be the same with the exported message definitions.
	35	+* Design - Store: We fixed an issue that static copies were missing when importing store items. (#888)
	36	+* Design - Store: Users who are not the model owner no longer see the eMagiz Store disclaimer popup, instead they see a popup containing a message. (#1027)
	37	+* Create - Errors - We fixed an issue that, when migrating to Gen3, the error channel to “errorChannel” is only created for the first inbound in an entry flow.
	38	+* Create - Styling: The styling of the left component panel has been restructured, solving a rare bug which would break the styling of certain functionalities.
	39	+* Deploy - Cloud Template: An issue with disk performance in the last cloud template update has been resolved in this release. Please check out the cloud template [[release notes>>Main.Release Information.Cloud Templates||target="blank"]] for more information.
	40	+* Manage - Monitoring: It is now possible to search on messages using partial search words in Manage Monitoring. For example, a search for Uptime can be done by searching for "up" "time" "ptim".
	41	+
	42	+
	43	+
	44	+=====Infra and image changes=====
	45	+
	46	+* Infra: New logging feature enabling us to make better choices in deprecating old encryption standards.