Changes for page 271 - Secure Ship
Last modified by Erik Bakker on 2026/06/29 09:20
From version 228.1
edited by Erik Bakker
on 2025/02/13 07:36
on 2025/02/13 07:36
Change comment:
There is no comment for this version
To version 343.1
edited by Erik Bakker
on 2026/06/29 09:20
on 2026/06/29 09:20
Change comment:
There is no comment for this version
Summary
-
Page properties (2 modified, 0 added, 0 removed)
Details
- Page properties
-
- Title
-
... ... @@ -1,1 +1,1 @@ 1 -2 38-PreparationParadise1 +271 - Secure Ship - Content
-
... ... @@ -1,13 +1,23 @@ 1 - In thelastsprint, we focusedon finishing thefirstiteration ofournew eMagiz Mendix Connectorandthefirstiterationof our new baseimage.Wewillfirst utilize thenew eMagizMendix Connectorto get an evenbetterfeeling ofits performance,butyouwill noticea UI change straightaway.Oncewehave passedthat hurdle, we will sharemore informationabout it andreleaseit to abroader range of customers. Regardingthebaseimage,wewill now introducethisto ourflowtesting offering toseeifanything unexpectedhappens. This is an additionalsafety measure we have put inplacetoreducethe chanceof somethingbreakingin your modeloncethenew base imageis released.Ontopof that,wehavesomeminorupdatestoimprovethequalityof theplatform.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.2 38-PreparationParadise.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 -====Minor Changes==== 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) 6 6 7 -* ILM: We defined the systems labeled as “isMendix” with the “MX“ icon, making it easier to identify the Mendix system. 8 -* Create - Flow Testing: As we are finalizing the new eMagiz runtime image that will update the Spring version to Spring boot 3.4.1 and Java to 17.0.13, we are now bringing these latest updates to flow testing. This means that any flow test you execute will run on the base image your runtimes will run on after the release of the new eMagiz runtime image. If one of your test cases suddenly exhibits weird behavior that you think is due to the update, feel free to contact us via our [[support department>>mailto:support@emagiz.com]]. 8 +==== Minor Changes ==== 9 9 10 -====Bug fixes==== 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. (#1792) 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 in line with our best practices. (#1768) 11 11 12 -* Create - Add Integrations: Integrations using the entry/exit connector, using the same message type, can now be untransferred from the create phase. (#1591) 13 -* Manage - Topic Statistics: Offsets related to topics and consumer groups are now shown even if they grow very large (#1599) 14 + 15 +==== Bug fixes ==== 16 + 17 +* Capture - Delete System: When being prevented from deleting a system by eMagiz, you no longer are confronted with an everlasting platypus. (#1771) 18 +* Deploy - System: We fixed an issue that, on some occasions, the wrong file location is set for the H2 database if the runtime runs on an on-premises machine. 19 +* Deploy - User Management: We fixed inconsistent errors in Deploy - User Management overview, making it more reliable to manage users and their credentials. 20 + 21 +==== Remarks ==== 22 + 23 +* Support employees can trigger a rollback on the intermediate certificate on the customer authorization server.