Skip to Content

Changes for page 271 - Secure Ship

Last modified by Erik Bakker on 2026/06/29 09:20
From version 18.1
edited by Erik Bakker
on 2022/11/08 08:30
Change comment: There is no comment for this version
To version 342.1
edited by Erik Bakker
on 2026/06/29 09:03
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -187 - Integration Sponsor
1 +271 - Secure Ship
Content
... ... @@ -1,25 +1,22 @@
1 -The release brings the next step of the Design store to the public and releases a new version of the eMagiz Mendix Connector that unlocks those using it to migrate to the next generation runtime. On top of that, we have several feedback items and bug fixes.
1 +This release includes improvements to our certificate rotation mechanism that affect all customers using our event streaming offering. On top of that, new **[[environment templates>>Main.Release Information.Cloud Templates.WebHome||target="blank"]]** are released. Furthermore, additional accelerants for all integration developers are here. This includes improvements in how we assist users in Design, Create, and Deploy.
2 2  
3 -Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.187 - Integration Sponsor.WebHome||target="blank"]].
3 +Please find out more on our [[Release blog>>doc:Main.Release Information.Release Blogs.271 - Secure Ship.WebHome||target="blank"]].
4 4  
5 -=====New features=====
6 -* Design - Store: It is now possible to import Transformations and Data Models from the Store into a model.
7 -** The Design Store can now be opened from the Mapping and Data Model screens as well.
8 -** The Design Store now offers search options to find store items that include Transformations and/or Data Models.
9 -** When importing a Store item with a Transformation and/or Data Model a new merge tool is available to link the Store Items data model to the users data model or to add new attributes/entities to the user data model.
10 -** When importing a Store item with a data model that has been previously linked the links are automatically restored allowing for easy updating of store based Integrations and for easier installation of multiple Store items with the same data model.
5 +==== New Features ====
6 +* Create - Flow Designer: When copy-pasting flow components with support objects, if a similar support object exists in the target flow, you can choose whether to copy the support object or re-use the existing one. (#978)
11 11  
12 -=====Minor changes=====
8 +==== Minor Changes ====
13 13  
14 -* Create - Flow designer: Improved the help texts of the Kafka components to better explain certain performance and load-balancing considerations, and added detailed information how messages (including headers) are converted to/from Kafka records.
15 -* Create - eMagiz Mendix Connector exit: Download buttons are added for non legacy eMagiz Mendix connectors
16 -* Create - Overview: You will now be able to see the errors that you have within a flow but on the integration widget. To do this, go into your flow and the number of errors you have in it, if any, will update so that next time you don’t have to navigate inside the flow to check how many alerts you have.
10 +* Design - API Catalog: Removed the “Server” button from this overview, along with all unique configuration related to it, as the button no longer served a function. (#)
11 +* Create - Flow Designer: Selecting a parameter when configuring the XSLT parameters of the XSLT transformer can be done with a dropdown. (#1026)
12 +* Deploy - Containers: The “flows that should run on” overview has been restructured to display the main information by default, with an option to show additional information if needed. Furthermore, updated the styling according to our best practices. (#1768)
17 17  
18 18  
19 -====Bug fixes====
20 -* Design - Store: Importing store item from response messages doesn't cause issues anymore
21 -* Design - Store: Importing response message and transformation to Api integration is possible
22 -* Design - API Gateway: The order of attributes in gateway messages were not always the same as the order in the generated Open API document.
23 -* Create - Flow Designer: Fix bugs when copy and paste components in G3 configuration
24 -* Create - Flow designer - Store: We fixed the maintaining selection of flow flagment from Store.
25 -* Manage - Exceptions of error messages: The count of error messages per exception class are now displayed (#744)
15 +==== Bug fixes ====
16 +
17 +* Create - Add Integrations: A more informative message is shown to the user if and when an automated flow configuration has failed. Additionally, the SOAP integrations can be recreated and edited. (#1377)
18 +* Create - Add Integrations: Fixed a specific case where changing a system to be a Mendix connector in the design phase did not correctly influence the deploy phase.
19 +* Create - Overview: We allow users to open (and reset) connector infra flows for on-premises API systems via the context menu. This makes the navigation to these connector infra flows consistent across patterns. (#1297)
20 +* Create - Flow Designer: A JMS outbound channel adapter can be saved without getting an alert when using a destination expression.
21 +* Create - Flow testing: XML test messages created based on a message definition will now contain randomized data.
22 +* Deploy - Releases (Swagger UI): Ensure that when you click the “Swagger UI” button in Deploy Releases, you are always redirected to the corresponding Swagger UI page, not the home page of our platform. (#1797)