Changes for page 262 - Good News
Last modified by Erik Bakker on 2026/02/23 08:06
From version 14.1
edited by Erik Bakker
on 2022/10/24 13:35
on 2022/10/24 13:35
Change comment:
There is no comment for this version
To version 281.1
edited by Erik Bakker
on 2025/09/21 21:29
on 2025/09/21 21:29
Change comment:
There is no comment for this version
Summary
-
Page properties (2 modified, 0 added, 0 removed)
Details
- Page properties
-
- Title
-
... ... @@ -1,1 +1,1 @@ 1 - 186-DaemonSwitch1 +253 - Rince Repeat - Content
-
... ... @@ -1,35 +1,21 @@ 1 -Th ereleasebrings thenew monitoringstacktofruitionandvariousupdatestohandlingmultiplenamespaces.Ontopofthat,wehave releaseda sleuthofsmallerfeedbackitemsandbugfixes.1 +This release features various updates to our platform, with a user-centric focus, as we work on wrapping up improved functionality for our new event streaming broker. All those improvements will be shared in the future once everything is ready. 2 2 3 -Please find out more on our [[Release blog>>Main.Release Information.Release Blogs. 186-DaemonSwitch.WebHome||target="blank"]].3 +Please find out more on our [[Release blog>>doc:Main.Release Information.Release Blogs.253 - Rince Repeat.WebHome||target="blank"]]. 4 4 5 -=====New features===== 6 -* Generic - New monitoring stack: As of this release, you can run on the new monitoring stack. For more information on becoming an early adopter, don't hesitate to get in touch with us at [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]. 5 +==== Major Changes ==== 7 7 8 - =====Minor changes=====7 +* Deploy -> Containers: The user can now easily see the containers a flow should run on in Deploy → Containers via the button in the flow grid. Furthermore, we have overhauled the user experience on this overview to align with recent improvements to other parts of Deploy. (#976) 9 9 10 -* Create - Flow designer: You can now see who/when a resource was changed on a resource view page. 11 -* Design - Solution: You will see a warning in the Solution view on operation if it is not connected to a backend API operation or in "Transformation" mode. 12 -* Create - Flow designer: You can see all related configurations that use a specific resource when viewing the details of the resource. 13 -* Design - API Gateway: Changes in your Gateway messages are reflected directly in your OpenAPI JSON document. 14 -* Model Dashboard - Going to manage from the model dashboard now loads the error message dashboard without having to click on the error messages dashboard explicitly 15 -* Create - Flow testing: The name of the starting point in the flow testing result tab is matched with the component type. 16 -* Deploy - Releases: The automated flow test pop-up can now be closed by pressing "Enter." 17 -* Deploy - Properties: Password-type properties are masked in the unused properties pop-up. 18 -* Deploy - User management: "Generate Keystore" button is renamed "Download Keystore," and the file name contains environment information. 19 -* Create - Flow Testing: Added a button to display the content of a selected trace message in a pop-out. 20 -* Deploy - Properties: You can use enter key to search on the property overview page. 21 -* Create - Flow designer: Increased size of the SpEL expression input field of standard transformer component. 22 -* Create - Flow Designer: Show generated resources toggle is not disabled by default; your preference for showing or hiding generated resources will be saved. 23 -* Administration - Licenses: Added event streaming storage usage of your models. 24 -* Store: Compatibility check is added, which prevents importing G3 store items into G2 flow/integration 25 -* General: Improved help texts explaining options and screens related to the new runtime architecture or the migration towards it. 9 +==== Minor changes ==== 26 26 27 -====Bug fixes==== 28 -* Deploy - Properties: Improved the layout of the cron trigger generator page 29 -* Deploy - Properties: Generating a password or CRON trigger will not reset the runtime field 30 -* Create - Flow designer: While editing an exit flow, the system message is not editable. 31 -* Design - Integration designer: For event streaming integrations, switching between Design Mapping and Create Transformation sometimes did not work. 32 -* Create - Transformation: For event streaming integrations, the 'Start editing' button sometimes did not work. 33 -* Create - Flow designer: Comparing two flow versions works again. 34 -* Create- Flow Designer: When creating my initial version of a flow, the notification pop-up shows the correct information. 35 -* Create - Flow Designer: All relevant support objects will be highlighted when selecting a support object. 11 +* When the user wants to use the Swagger resource with the correct information, one of the API flows in Create requires a flow version push. ** 12 +* Manage - Alerting - Triggers: Removed the deprecated, eMagiz-defined log trigger specified under the ‘other’ tab for Log entries. This trigger would generate an alert in the event of a runtime crash due to memory issues or failure to deliver a message. 13 +** Since the release of our new log alerting, it is possible to specify this alert rule yourself under the ‘logs’ tab if you still wish to receive these alerts. To do so, create four new log triggers as shown in our [[release blog>>doc:Main.Release Information.Release Blogs.253 - Rince Repeat.WebHome||target="blank"]] 14 +* Manage - Alerting - Triggers: Introduced a new ‘Quotas’ tab, where the quota limits for metrics, log, and error messages can be viewed per environment. 15 + 16 +==== Bug fixes ==== 17 + 18 +* Create - Flow Testing: Validation message is changed to make it more transparent to the user why they could not set the desired name for the flow test message. (#1702) 19 +* Create - Flow designer: You can no longer view the save button on a standard aggregator component while not in “Start Editing“ mode (#1703) 20 +* Deploy - Releases: Height of the release details pop-up is fixed to keep it consistent between all releases, including the Create Phase Release. (#1706) 21 +* API Management - Swagger (UI): NonEmptyString is now correctly represented in the swagger resource in Create, and therefore the Swagger UI that API users can check for details. (#1652)