Skip to Content

Changes for page 254 - Other One

Last modified by Erik Bakker on 2025/10/09 11:13
From version 273.1
edited by Erik Bakker
on 2025/07/28 12:18
Change comment: There is no comment for this version
To version 67.1
edited by Erik Bakker
on 2023/04/13 14:28
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -250 - Fix Fest
1 +195 - Easter Party
Content
... ... @@ -1,49 +1,46 @@
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 +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.250 - Fix Fest.WebHome||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 ====
5 +=====New features=====
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
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.
18 18  
19 -==== Minor changes ====
9 +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.
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)
11 +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.
31 31  
32 -==== Bug fixes ====
13 +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.
33 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 - 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)
36 -* Create - Flow Designer: Validation in JDBC stored procedure inbound channel adapter is now shown on the right element. (#1557)
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 - Flow Designer: 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.
15 +{{info}}Important to note is that
16 +* 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.
17 +* The auto-clean release functionality is unaffected by this change, ‘property’ releases will not be counted as a release.
18 +* There is a maximum of 26 ‘property’ releases. (26 letters of the alphabet)
19 +* 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}}
20 +
21 +=====Minor changes=====
22 +
23 +* General - Control Tower: Changed several generic triggers for more predictable behavior.
24 +* Administration - License Tracker: The license tracker has been updated for new license models and features.
25 +* 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.
26 +* Capture - Settings: Editing message types are now consistent between new and existing ones. (#884)
27 +* Design - API Gateway: Default HTTP responses are generated automatically (#417)
28 +* 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)
29 +* 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.
30 +* 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.
31 +* 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.
32 +* Deploy - Deployment plan: The "Prepare release" is not scheduled automatically anymore, so you can be in control of your deployment plan.
33 +* Deploy - Architecture: Certificates only editable by system admin.
34 +* 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.
35 +
36 +====Bug fixes====
37 +
38 +* 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"]].
39 +* 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)
40 +* 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.
41 +* 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)
42 +* Create - Message: When viewing or editing an enumeration, it is no longer deleted when the cancel button is pressed.
43 +
44 +====Remarks====
45 +
46 +* Deploy - Releases: We removed the existing snapshots of release property values.