Changes for page 232 - Bug Busters
Last modified by Carlijn Kokkeler on 2024/11/04 11:23
From version 68.1
edited by Erik Bakker
on 2023/04/13 14:31
on 2023/04/13 14:31
Change comment:
There is no comment for this version
To version 262.1
edited by Carlijn Kokkeler
on 2024/06/19 09:27
on 2024/06/19 09:27
Change comment:
There is no comment for this version
Summary
-
Page properties (3 modified, 0 added, 0 removed)
Details
- Page properties
-
- Title
-
... ... @@ -1,1 +1,1 @@ 1 - 195-EasterParty1 +223 - Idyllic Image - Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki. ebakker1 +XWiki.CarlijnKokkeler - Content
-
... ... @@ -1,43 +1,17 @@ 1 - Asthequarter hasended, we went silentfor acoupleofweeksto planfortheupcomingquarter duringourPIrituals. Thistimeweaddedthefamous"Hackathon" to the end ofthePIweekso wecould start theEasterbreak withexcellentspiritafter solvingseveralsmaller feedbackitems andbugsreported by you. Several of thosetorieswill be included inthisandthepcoming release. Ontopof that, weintroducevarious improvementsto ourAPI Gatewaypattern andour3rd generationruntimearchitecture. Subsequently,we willrelease aewruntimeimagesupportingthemultiple improvements.1 +In the last sprint cycle, we have worked on releasing a new [[runtime image>>doc:Main.Release Information.Runtime Images.V310.WebHome||target="blank"]], which contains several bug fixes, and increases the debugger duration. Moreover, we have worked on our SwaggerUI settings, filtering, and SpEL Expressions. Find out all features and fixes below. 2 2 3 -Please find out more on our [[Release blog>>Main.Release Information.Release Blogs. 195-EasterParty.WebHome||target=3 +Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.223 - Idyllic Image||target="blank"]]. 4 4 5 -=====New features===== 5 +====New features==== 6 +* Design - API management: Model contacts are now able to select a default SwaggerUI environment from the API management settings in Design phase. The environment selected here will be the first and the default value of SwaggerUI server dropdown. (#438) 7 +* Capture - Settings: It is now possible to filter the message types in Capture on whether they are used. (#1281) 8 +* Manage - Monitoring: Wiretaps and debugging sessions will now collect messages for 10 minutes, this used to be 5. Note that the JMS server needs to be updated in order to also store the messages for 10 minutes instead of 5. For this, a new [[runtime image>>doc:Main.Release Information.Runtime Images.V310.WebHome||target="blank"]] is available. Moreover, helptexts have been added for clarification. 6 6 7 -* Deploy - Releases: 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. 9 -** 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. 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 -** 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. 11 - 12 -{{info}}Important to note is that 13 -* 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. 14 -* The auto-clean release functionality is unaffected by this change, ‘property’ releases will not be counted as a release. 15 -* There is a maximum of twenty-six ‘property’ releases. (twenty-six letters of the alphabet) 16 -* 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}} 17 - 18 -=====Minor changes===== 19 - 20 -* General - Control Tower: Changed several generic triggers for more predictable behavior. 21 -* Administration - License Tracker: The license tracker has been updated for new license models and features. 22 -* 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. 23 -* Capture - Settings: Editing message types are now consistent between new and existing ones. (#884) 24 -* Design - API Gateway: Default HTTP responses are generated automatically (#417) 25 -* 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) 26 -* 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. 27 -* 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. 28 -* 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. 29 -* Deploy - Deployment plan: The "Prepare release" is not scheduled automatically anymore, so you can be in control of your deployment plan. 30 -* Deploy - Architecture: Certificates only editable by system admin. 31 -* 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. 32 - 33 33 ====Bug fixes==== 11 +* Create - Flow Designer: The SMB outbound gateway with the GET command did not work, this has been resolved. For this, a new [[runtime image>>doc:Main.Release Information.Runtime Images.V310.WebHome||target="blank"]] is available. Moreover, helptexts have been added for clarification. 12 +* Create - Flow designer: We fixed a transformation tooling issue where it was not possible to view an XSLT in certain cases. 13 +* Create - Flow Designer: In rare occurences, when a TaskScheduler was used, a deadlock situation could occur due to thread starvation. The number of threads available to the TaskScheduler has been increased to resolve this issue. For this, a new [[runtime image>>doc:Main.Release Information.Runtime Images.V310.WebHome||target="blank"]] is available. Moreover, helptexts have been added for clarification. 14 +* Create - Flow Designer: The recommended SpEL expression used for contructing a multipart/form-data HTTP request was no longer valid. The [[documentation>>doc:Main.eMagiz Academy.Microlearnings.Expert Level.Data Handling.expert-data-handling-multipart-form-data.WebHome||target="blank"]] has been updated with the new standard and the updated expression is now part of our default test suite. (#1215) 15 +* Create - Properties: Support has been added to provide the SFTP session factories with a known_hosts in string format rather than file format, so it is easier to setup SFTP. For this, a new [[runtime image>>doc:Main.Release Information.Runtime Images.V310.WebHome||target="blank"]] is available. Moreover, helptexts have been added for clarification. 34 34 35 -* 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"]]. 36 -* 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) 37 -* 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. 38 -* 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) 39 -* Create - Message: When viewing or editing an enumeration, it is no longer deleted when the cancel button is pressed. 40 40 41 -====Remarks==== 42 - 43 -* Deploy - Releases: We removed the existing snapshots of release property values.