Skip to Content

Changes for page 256 - Power Up

Last modified by Erik Bakker on 2025/11/04 12:44
From version 272.1
edited by Erik Bakker
on 2025/07/28 11:29
Change comment: There is no comment for this version
To version 78.1
edited by Erik Bakker
on 2023/05/12 08:02
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -250 - Fix Fest
1 +197 - Pay Attention
Content
... ... @@ -1,49 +1,21 @@
1 -This release features numerous updates to our platform, with a user-centric focus. This release, we once again embarked on our traditional Hackathon journey, focused on making the lives of our day-to-day platform users easier.
1 +Another couple of weeks have passed, so it is time for a new release. We have delivered additional minor (bug) fixes in this release and released the event streaming alerting. The last is a real improvement in managing your event streaming solution. Furthermore, you will find several enhancements in working in nextGen environments.
2 2  
3 -Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.250 - Fix Fest.WebHome||target="blank"]].
3 +Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.197 - Pay Attention.WebHome||target= "blank"]].
4 4  
5 -==== New features ====
5 +=====New features=====
6 +* Deploy - Cloud Templates: New Cloud Templates are available for single-lane and double-lane environments. Please check out the cloud template [[release notes>>Main.Release Information.Cloud Templates.WebHome||target="blank"]] for more information.
7 +* Manage - Alerting: Added support for providing alerts on event streaming topics: consumer lag, topic approaching maximum size & messages added to the topic under the threshold. Two new alerts are introduced to send alerting messages to the user when messages added to the topic is greater than a threshold or when topic messages consumed is below a threshold. These new alerts are applied for all runtime architectures we support. Please check out the runtime [[release notes>>Main.Release Information.Runtime Images.WebHome||target="blank"]] for additional information.
6 6  
7 -* Create - Flow Designer: Custom resources in the form of XSLT files and Groovy scripts can be previewed and edited directly in the flow designer. (#1115)
8 -* Create - Flow Designer: Two navigation buttons (Start/Stop editing and “Open in Design“) are added to the following pages. (#1607)
9 -** Messaging:
10 -*** System message
11 -*** CDM message
12 -** API gateway:
13 -*** Gateway message
14 -*** System message
15 -** Event streaming:
16 -*** Topic in
17 -*** Topic out
9 +=====Minor changes=====
18 18  
19 -==== Minor changes ====
11 +* Create - Flow Testing: we add some minor UI improvements and validation to prevent a test case from being in live mode and automated.
12 +* Deploy - Deployment plan: If you run the deployment plan to deploy machines and run into issues, your deployment plan will be stopped at the step that gets a warning, and you can see a warning message on the left side. That is easier for you to figure out problems and fix them. Afterward, you can run that step again by selecting "Refresh" and "Execute."
13 +* Deploy - Architecture: We increased the grace period for shutting down runtimes when they run on Docker environments.
20 20  
21 -* General - Export: When exporting to PNG, the filename now has a logical name, containing the technical name of your model, the phase that was exported, and the time of the export. (#266)
22 -* Capture - Settings: This overview will now show the technical names, when known, of systems as well as their display name. (#810)
23 -* Capture - System: Users can quickly create multiple tenants in a multi-tenant system by using the new button called “Save and add new”. The button saves the previously created tenant and opens a new page to create a new tenant. (#1527)
24 -* Design - Settings: Make clear that only the model owner can alter the settings displayed under Design - Settings (#1638)
25 -* Create - Flow Designer: The expressions of recipient routers are visible in the grid to show the conditions along with them. Additionally, the grid has been updated to Data Grid 2, which offers a more visually appealing display. (#1649)
26 -* Create - Transformation: When viewing a transformation with a datatype conversion from or to ‘date’, ‘time’, or ‘datetime’, the time zone used in the formatting is now shown without the need to enter edit mode. (#945)
27 -* Deploy - Releases: We have updated the UI and user experience in Release > Details > Flow versions and Integrations tabs. Furthermore, we have added the option to display the integration name rather than the message type name, allowing you to see which API operation you are adding or removing from a release. (#1581)
28 -* Deploy - Architecture: Cloudslots that do not have an active environment will not be planned to be upgraded anymore, removing unnecessary emails being delivered to model owners. (#1594)
29 -* Deploy - Properties: Updated hover text of the generate button to reflect that values will be replaced. (#1160)
30 -* Manage - Error Messages: Users with view rights in Manage can now change the status of error messages. (#1669)
15 +====Bug fixes====
31 31  
32 -==== Bug fixes ====
33 -
34 -* Design - Message Tree: Attribute order is exchanged between the moved attributes rather than making an algebraic calculation to obtain a new value to avoid double jumps during the movement. (#1593)
35 -* Create - Flow Designer: Validation in JDBC stored procedure inbound channel adapter is now shown on the right element. (#1557)
36 -* Create - Message Definition: A Longer time is given to the user to change the fields. Additionally, the pattern field is no longer time-bound, as it requires a longer input. (#1575)
37 -* Create - Flow Designer: Wiretap channel does not cause an error when its ID is too long. (#1606)
38 -* Create - Flow Designer: When changing a filter with a discard channel to start throwing exceptions on rejection instead of sending them to the discard channel, the UI will now correctly reflect this. (#1621)
39 -* Create - Flow Designer: when copying a component which have a field value longer than 64 characters and contains the flow’s name, then pasting, the field will not be limited to 64 characters. (#1398)
40 -* Create - Components: Linetokenizer -> Strict of the Flat file to XML transformer and 'Allow empty array' of the system message are not editable anymore when not in 'start editing'. (#1612)
41 -* Create - Transformation: Users are now able to switch between “Custom XPath” and “Convert datatype” options for the “Transform from date/time” transformer. (#1662)
42 -* Create - Transformation: Users can return to the correct design phase message mapping. (#1348)
43 -* Create - Transformation: User permissions are modified for the From Boolean Transformer so that the user can see the Value Mappings. (#1622)
44 -* Create - Flow Testing: Flow tests that contain Kafka Message Listener Adapter components can be executed again. (#1672)
45 -* Create - Create Flow Version: We fixed an issue where you got an error, which requires Deploy permission, when you create and transfer the new API operation to Deploy, since you only have permission in Capture, Design, and Create. (#1677)
46 -* Deploy - Architecture: You were able to remove pending changes from Deploy Architecture without applying them when pressing cancel after applying changes for a double lane model. (#1651)
47 -* Deploy - Architecture: Resolved the issue where enabling/disabling SSL-configuration in runtime settings could lead to duplicated help text. (#1455)
48 -* Deploy - User Management: We fixed an issue where the list of API operations did not show since these API operations were assigned to the related user. (#1678)
49 -** Additionally, help text is converted to the latest help text format.
17 +* Create - Store: We fixed an issue that you sometimes do not see the list of message definitions or the list of transformations when you export new or update your store item.
18 +* Deploy - Architecture: You can apply your changes to only one or both zones on 3rd generation double-lane models.
19 +* Deploy - Architecture: We fixed an issue where runtimes were not removed from a machine, while this was expected behavior according to the architecture.
20 +* Deploy - Architecture: The gen two karaf container will now exit when an Out-of-memory error occurs for gen three cloud environments. This will cause an auto-healing restart, after which the container can run properly again.
21 +* Design - Message Definitions: "Message format" button is also available in view mode. (#919)