Changes for page 232 - Bug Busters

Summary

• Page properties (3 modified, 0 added, 0 removed)

Details

Page properties

Title

...	...	@@ -1,1 +1,1 @@
1		-187 - Integration Sponsor
	1	+227 - Fix Frenzy

Author

...	...	@@ -1,1 +1,1 @@
1		-XWiki.ebakker
	1	+XWiki.CarlijnKokkeler

Content

...	...	@@ -1,25 +1,16 @@
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	+During our recent sprint cycle, we have ......
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>>Main.Release Information.Release Blogs.227 - Fix Frenzy||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	+====Minor changes====
	6	+* Deploy - Architecture: The user is now able to search in the Start/Stop flows overview.
11	11
12		-=====Minor changes=====
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.
17		-
18		-
19	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)
	9	+* Create - Flow Designer: We fixed an issue where certain areas were selected in the flow designer when only hovering over them, without clicking.
	10	+* Create - Flow Testing: The tracing information for errorChannel messages has been improved.
	11	+* Create - Message Definitions: The "last changed by" and "last changed date" values of additional namespace resources are now updated correctly when you make changes to your namespaces in your message definitions.
	12	+* Deploy - Releases: We fixed a bug where runtimes that did not change appeared in the deployment plan in the list of flows that will be restarted.
	13	+* Deploy - Runtime Overview: We fixed a bug such that the runtime overview now shows the correct container version.
	14	+* Manage - Alerting: We have implemented a fix that allows you to activate and test queue triggers per environment when you are migrating your model to the current runtime architecture. You will be able to test the queue triggers of any environment that is fully migrated, even if another environment is still in the process of migrating.
	15	+* Manage - Alerting: You can now add internal and external recipients to your default trigger configuration at the same time, and they will be applied to your triggers correctly.
	16	+* Manage - Alerting: We have fixed a case where a tenant-queue-trigger could be activated on a hybrid environment, before the JMS of that environment had been deployed to the current runtime.