Wiki source code of 251 - Molten Morph
Last modified by Maria on 2025/08/26 15:16
Hide last authors
| author | version | line-number | content |
|---|---|---|---|
 |
274.1 | 1 | This release features various updates to our platform, focusing on maintainability and caring about models throughout their lifecycle. In this release, we worked on several items still in our pipeline and concentrated on making the lives of our day-to-day platform users easier. |
| |
1.1 | 2 | |
| |
274.1 | 3 | Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.251 - Molten Morph.WebHome||target="blank"]]. |
| |
35.1 | 4 | |
| |
267.1 | 5 | ==== Minor changes ==== |
| 6 | |||
| |
274.1 | 7 | * Create - API Security: Users are informed about what will happen when they press the Update Security button for the API gateway infra by a confirmation pop-up. (#1510) |
| |
278.1 | 8 | * Create - Add Integrations: The transfer and untransfer processes for event processors have been fixed. Users can now add or remove integrations for an event processor one at a time. |
| |
274.1 | 9 | ** When adding integrations, the associated topics are automatically added if they do not already exist in **Create**. Once both the input and output topics of a processor exist in **Create**, the processor itself is added to **Create**, and both the processor and its topics are pushed to **Deploy**. |
| |
276.1 | 10 | ** For the untransfer process, integrations can be removed individually again. When the last integration of a processor is selected for removal, the processor and its topics are also removed. This action is confirmed through a pop-up, which displays what will be deleted and requests confirmation from the user. |
| |
274.1 | 11 | *** This approach allows users to identify which processor they want to remove by selecting all its integrations. They can choose to remove them one by one or select all at once. |
| |
278.4 | 12 | * Deploy - Releases overview: Merged all pattern infographics into one popup. |
| |
270.1 | 13 | |
| 14 | ==== Bug fixes ==== | ||
| 15 | |||
| |
274.1 | 16 | * Create - Add Integrations: Users can remove flows containing test cases with "live mode" activated. |
| 17 | * Create - Flow Designer: Flat file to XML transformer pop-up is updated correctly. The validation errors are displayed on the side panel accordingly, based on what the user has filled in. (#1477) | ||
| 18 | * Create - Flow Designer: Groovy scripts are automatically recognised as part of the “used resources“ when attached to one of the standard components. (#1514) | ||
| 19 | * Create - Flow Designer -> Rest Template: Unnecessary values are no longer saved to the support object to prevent misuse. (#1693) | ||
| |
277.1 | 20 | * Create - Flow Designer: Sustainers can view properties from create without facing an error message. (#1468) |
| |
274.1 | 21 | * Create - Transformation: A visual warning is shown when trying to edit the default transformation if it is not used in any flow component. (#1558) |
| 22 | * Manage - Alerting -> Triggers: Improved help text for the error trigger pop-up page. (#1588) | ||
| 23 | * Manage - Alerting -> Triggers: Sustainers can visually see and copy the identifier of the new alerts for logs, errors, and queues. (#1598) | ||
| |
278.1 | 24 | * Create – Flow Tester – Selecting the option to view all test messages correctly displays all imported messages on the screen.(#1696) |
| 25 | * Create - Flow designer - XSLT transformer - The edit button used for navigating to the transformation tab is not available when using a custom imported resource for the XSLT.(#1701) | ||
| 26 | * Capture → Settings: Changes to message types update instantly on the dashboard after saving. (#1548) |