Skip to Content

Changes for page 220 - Patch Parade

Last modified by Carlijn Kokkeler on 2024/05/22 13:30
From version 100.1
edited by Erik Bakker
on 2023/08/01 15:02
Change comment: There is no comment for this version
To version 23.1
edited by Erik Bakker
on 2022/11/21 13:13
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -202 - New Equilibrium
1 +188 - Close Encounters
Content
... ... @@ -1,36 +1,25 @@
1 -In the last sprint cycle, we focused on finishing our work on the release properties functionality introduced in this release. On top of that, we have some additional smaller feedback items and bug fixes coming out of the Hackathon for you.
1 +The release brings several improvements to our 3rd generation runtime and the interaction with it. On top of that, we have several feedback items and bug fixes.
2 2  
3 -Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.202 - New Equilibrium.WebHome||target= "blank"]].
3 +Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.188 - Close Encounters.WebHome||target="blank"]].
4 4  
5 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 also be opened from the Mapping and Data Model screens.
8 +** The Design Store now offers search options for store items, including Transformations and Data Models.
9 +** When importing a Store item with a Transformation 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 easier installation of multiple Store items with the same data model.
6 6  
7 -* Deploy - Releases: We removed two unnecessary release options: “Set release properties” and “Check properties. “ You can quickly update your properties via the Release properties overview.
8 -* Deploy - Releases: Before activating or deploying a new release, you should fill in all properties that relate to your deployment. If there are any properties without value, we will show them to you. Then you can update them and continue your deployment.
9 -* Deploy - Properties: This tab 'Properties' for managing properties is deprecated as of Release 202. As a result, it cannot be used anymore to manage properties. You can manage your properties via the 'Releases' overview. On this overview, you can select the wrench icon on the 'Create phase release' to find the property management overview. For more information about the management of properties and the related features, click on the right-bottom corner on 'Help and check out our documentation.
10 -* Deploy - Cloud Template: We have introduced new functionality for our next-generation architecture to host a MQTT broker in a failover (i.e., double lane) architecture. Please check out the cloud template [[release notes>>Main.Release Information.Cloud Templates.WebHome||target="blank"]] for more information.
11 -
12 12  =====Minor changes=====
13 13  
14 -* Store - Export: "Store exporter" users can test their exported store items immediately without waiting for approval. (#1001)
15 -* Deploy - Releases: The infographic has been updated.
16 -* Deploy - Release Properties: Required properties are checked if they contain nested properties and are not missing values.
17 -* Deploy - Property release: Names of properties can be created/removed/edited.
18 -* Deploy - History: We deprecated the old page History, which displays the property changes in your model. The properties' history is on the Deploy phase's History page.
19 -* Deploy - Architecture: Changes made to AWS Slot settings are recorded in history. (#966)
20 -* Manage - Monitoring: Improved performance of 3rd generation runtime dashboards.
21 -* Infrastructure: Tightened security policies for a more secure infrastructure.
14 +* Create - Flow Designer: Code mapping is now available for models migrating to the 3rd generation runtime
15 +* Create - eMagiz Mendix Connector exit: Download buttons are added for non-legacy eMagiz Mendix connectors.
16 +* Create - Overview: You will now see your errors within a flow but on the Create - Overview. To activate this, open 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.
22 22  
23 -====Bug fixes====
24 24  
25 -* Design - Import: Import into design from the store is possible, even if the integration is not in Create yet.
26 -* Create - Flow Designer: Improved validation on XPath header enricher. (#1005)
27 -* Create - Flow Designer: We fixed an issue that your flow fragment metadata disappeared when you canceled your changes of the existing flow fragment in your new version of the store item. (#989)
28 -* Create - Flow Designer: In some cases, when copying/pasting components into a flow, validation alerts would be displayed that did not belong to a component. This problem is now fixed. (#955)
29 -* Create - Flow Designer: We fixed an issue that prevents dragging and dropping an annotation from the left panel after a search from the search box. The speed of creating the dialog to enter the component’s name is also improved.
30 -* Create - Flow Testing: Properties will not disappear from the list when canceling changes on a default property value. (#913)
31 -* Create - Flow Testing: Users with view rights can edit test case names, descriptions, and property values. (#973)
32 -* Deploy - Architecture: The runtimes will display the number of connected flows, not "Zero."
33 -* Deploy - Architecture (Runtime Settings): Moved the delete button to the right side of the page and fixed the bug in the help text.
34 -* Deploy - Releases: We fixed an issue that prevented you from seeing a comparison message when hovering over an exit gate flow of the API pattern if you compare two release versions in Deploy. (#839)
35 -* Deploy - Releases: We improved the loading buttons of releases on the right pane by Order (Ascending).
36 -
19 +====Bug fixes====
20 +* Design - Store: Importing store items from response messages doesn't cause issues anymore.
21 +* Design - Store: Importing response messages and transformation to API integration is possible.
22 +* Design - API Gateway: The order of attributes in gateway messages was sometimes different than in the generated Open API document. (#783)
23 +* Create - Flow Designer: Ensure that the copy and pasting experience works for all flows.
24 +* Create - Flow Designer - Store: We fixed the maintaining selection of flow fragments from the store.
25 +* Manage - Exceptions of error messages: The count of error messages per exception class is now displayed. (#744)