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	+195 - Easter Party

Author

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

Content

...	...	@@ -1,36 +1,44 @@
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	+As the quarter has ended, we went silent for a couple of weeks to plan for the upcoming quarter during our PI rituals. This time we added the famous "Hackathon" to the end of the PI week so we could start the Easter break with excellent spirit after solving several smaller feedback items and bugs reported by you. Several of those stories will be included in this and the upcoming release. On top of that, we introduce various improvements to our API Gateway pattern and our 3rd generation runtime architecture. Subsequently, we will release a new runtime image supporting the multiple improvements.
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.195 - Easter Party.WebHome||target= "blank"]].
4	4
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		-* Deploy - Architecture: Changing the memory of a runtime should now be done via the machine "details" screen. On top of this logic is added to check the overall health of the machine. This check is reevaluated on every change made on runtime level related to memory.
	5	+=====New features=====
8	8
9		-====Minor changes====
	7	+We take the first step to fix properties to a release. This gives users more control over properties. For example, they can ensure that the release contains suitable properties that are more manageable.
	8	+When this release reaches production, the first new release that users activate and have Gen3 containers/properties, the new feature becomes active. Users will see a wrench icon on the release. When they click on it, they will see an overview of the attached Gen3 properties. These properties cannot be altered for that specific release. This only counts for Gen3 properties, properties for Gen2 runtimes/machines will still be fetched from the Deploy-Properties list and can still be altered.
	9	+If users notice that a specific Gen3 property of a release not contains the correct value, users can edit the value by opening the property overview of the release. At the bottom of the overview, the option ‘Change properties’ allows users to edit the properties of a release.
10	10
11		-* Capture - Generic: When deleting a system, tenant, or integration, more information is provided on what you are deleting (#1174)
12		-* 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)
13		-* Create - Flow designer: Property pop-ups now contain the property name as a text where you can copy the property's name. (#1175)
14		-* 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)
15		-* 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)
16		-* 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)
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 continuing after pressing "Apply to environment" instead of when pressing "Apply Changes" in the next screen. (#606)
19		-* Deploy - Architecture: Applying to environment or saving your machine is not possible If there is more memory configured than available. (#1144)
20		-* Deploy - Architecture: Changing the memory of a runtime should now be done via the machine "details" screen. On top of this logic is added to check the overall health of the machine. This check is reevaluated on every change made on runtime level related to memory. (#545)
21		-* Manage - Monitoring: A progress bar is added when users have long searches on "Log entries". (#1133)
22		-* Manage - Alerting - Triggers - New: It can now filter across Queues, Topics, Recipients, and Runtimes when adding a new trigger. (#1089)
23		-* Manage - Alerting - Alerts: It is now possible to filter the alerts based on the status. (#1176)
24		-* Catalog: Topics are now sorted alphabetically (#1231)
	11	+A new ‘property’ release will be created when users use that option. A ‘property’ release can be identified by a suffix that contains a letter. Users can change the properties, and when they are done, they can directly activate and deploy the release. With our new improvements to the deployment plan, only the affected containers by the property change(s) will be redeployed. This will result in faster deployments.
25	25
	13	+{{info}}Important to note is that
	14	+* While changing a property in a ‘property’ release, users also have the option to alter the value in the Deploy-Properties list. By default, this is set to Yes, because when a new release is created, the values of Deploy-Properties will be used and not properties of an earlier release. When a user closes the screen for editing a property, the change will immediately be implemented.
	15	+* The auto-clean release functionality is unaffected by this change, ‘property’ releases will not be counted as a release.
	16	+* There is a maximum of 26 ‘property’ releases. (26 letters of the alphabet)
	17	+* Only the latest release can be edited. This can be identified by checking the suffix. The suffix with the latest letter of the alphabet is editable.{{/info}}
	18	+
	19	+=====Minor changes=====
	20	+
	21	+* General - Control Tower: Changed several generic triggers for more predictable behavior.
	22	+* Administration - License Tracker: The license tracker has been updated for new license models and features.
	23	+* Administration - License Tracker: When the feature ‘Data sink’ is enabled, the number of message packs of the contract will be displayed when you hover with the mouse over the feature.
	24	+* Capture - Settings: Editing message types are now consistent between new and existing ones. (#884)
	25	+* Design - API Gateway: Default HTTP responses are generated automatically (#417)
	26	+* Design - Solution design: An additional option is added to the context menu that navigates to the message definition added to event streaming topics without processors. (#850)
	27	+* Create - Add Integrations: We used the name of the API integration that you set in the Design phase to display on the Transfer screen. That helps you choose the correct integrations to add to the Create phase more quickly.
	28	+* Create - 3rd Generation Migration: You can toggle the custom error handling option for your event processors while migrating your event processing container to the 3rd Generation Runtime.
	29	+* Deploy - Deployment plan: When you run your deployment plan in your model using the new generation runtimes, you will be able to be the logs that relate to an executing deployment step.
	30	+* Deploy - Deployment plan: The "Prepare release" is not scheduled automatically anymore, so you can be in control of your deployment plan.
	31	+* Deploy - Architecture: Certificates only editable by system admin.
	32	+* Manage - Jobs: In case the model has containers that contain jobs in one of its flows, users can inspect job managers, job executions, and job step executions. Note that this only works for the 3rd generation runtime.
	33	+
26	26	====Bug fixes====
27	27
28		-* 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)
29		-* 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)
30		-* Create - Transformation: The 'View' and 'Edit' buttons under parameters are the default behavior when you are editing. (#1241)
31		-* 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)
32		-* Create - Flow designer: Components in the left panel of the flow designer are now alphabetically sorted by their name. (#1164)
33		-* Deploy - Property Overview: Resized window so that all property names are not cut off halfway. (#1081)
34		-* Deploy - Runtime Overview: Sorting on status is possible. (#1240)
35		-* 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)
36		-* Monitoring - Event streaming statistics: graphs can show up to 30 days.
	36	+* General - Runtime Image: A new runtime image for customer models running on the 3rd generation runtime. Please learn more about our [[Runtime Image release notes>>Main.Release Information.Runtime Images.V140.WebHome||target="blank"]].
	37	+* Design - API Gateway: Improved generation of Open API JSON and example messages for API gateway operations to handle cases where an element in your gateway definition is used multiple times. (#440)
	38	+* Design - API Gateway: We fixed an issue where changing the message format of a gateway message did not result in an update of the OpenAPI (i.e., Swagger) document.
	39	+* Design - System message: We fixed an issue that led to importing towards the wrong message definition when the option "Import from XSD" was chosen on a synchronous message. (#818)
	40	+* Create - Message: When viewing or editing an enumeration, it is no longer deleted when the cancel button is pressed.
	41	+
	42	+====Remarks====
	43	+
	44	+* Deploy - Releases: We removed the existing snapshots of release property values.