Skip to Content

Changes for page 169 - Check, Act

Last modified by Carlijn Kokkeler on 2024/04/18 13:30
From version 1.1
edited by eMagiz
on 2022/06/17 11:37
Change comment: There is no comment for this version
To version 2.1
edited by eMagiz
on 2022/06/17 11:40
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -11,6 +11,9 @@
11 11  
12 12  See below to illustrate how that will look in the Design and Create phase of eMagiz.
13 13  
14 + [[image:Main.Images.Release Blog.WebHome@169-release-blog-1.jpg]]
15 + [[image:Main.Images.Release Blog.WebHome@169-release-blog-2.jpg]]
16 +
14 14  == **Flow Testing improvements** ==
15 15  
16 16  On the flow testing functionality, we will release two improvements. All improvements will enhance the overall experience when using the flow testing functionality.
... ... @@ -18,38 +18,27 @@
18 18  //__Visual indicator missing properties__//
19 19  As of this release, you will get notified by eMagiz when there are properties needed in your flow that are not yet filled in for this specific flow test. When pressing play, eMagiz will check whether properties are filled in. In cases where this does not hold, eMagiz will show the following pop-up.
20 20  
24 + [[image:Main.Images.Release Blog.WebHome@169-release-blog-3.jpg]]
21 21  //__Easier generation of test messages__//
22 22  Before this release, you could not use the topic definitions as defined for your Event processor as a blueprint for your test message. With this release, we fixed this oversight to make sure that also for your event processors, you can use the message definitions beloning to that pattern.
23 23  
28 +== **API gateway Gen3 Default** =
29 +
30 +As of this release, your newly created API Gateway solutions will run on the latest generation runtime (Gen3) by default. Note that this only applies to new solutions. However, existing solutions will not be changed and remain on the current architecture until the migration is planned and executed. If you want more information on the migration, please contact us at productmanagement@emagiz.com.
31 +
24 24  == **Feedback items ** ==
25 25  
26 -//__Correctly display expression in view mode - Create Transformation__//
27 -Within the Create transformation, it could happen that when you check out any of the added transformation components in view mode to see the expression that a ‘fake’ space was shown within the expression. This opened up the possibility for confusion when reading the expression.
34 +//__eMagiz Kafka Connector__//
35 +*We have made a new eMagiz Kafka Connector available. We have reduced the dependencies towards other modules. We have brought the explorer function back to see which topics are available within your organization and test the connectivity.
36 +*About the dependencies, this means that you do not need any other Mendix modules anymore to run the eMagiz Kafka Connector. This makes it easier to update and more secure as we fully control what happens within the eMagiz Kafka Connector. y.
28 28  
29 -As of this release, we have solved this problem by visualizing the expression so that it is easy to interpret it correctly.
30 -
31 -//__JSON related transformations - Event processors__//
32 -When you used the new JSON transformation functionality within the platform, various unique aspects of JSON, such as arrays, decimals, and integers were not formatted correctly in the output message.
33 -
34 -This was a discrepancy compared to the JSON transformations within the Messaging and API Management patterns. With this release, we have unified the behavior of the portal within Design. This means that when you select JSON as the message format for your system or your message definition, the transformation will be changed to output valid JSON.
35 -
36 -//__Option to hide 'auto-delete' release pop-up__//
37 -As of this release, you will have the option to hide the pop-up you get when you create a new release that notifies you that other releases might be deleted. Activate the check box and press Confirm.
38 -
39 -
40 -//__Validation UI Error for missing technical name Tenant__//
41 -To further improve the validation UI, we will also show an error in Design when you have not defined the technical name of a Tenant related to a particular system.
42 -
43 -//__Transfer model owner role to another individual__//
44 -As of this release, it is once more possible to transfer your model owner role to someone else that has rights on the model for which you want to transfer the rights. Simply navigate to Administration -> User Management -> Model permission. Here you can search for the model, and once selected, press the button called Change contact. Via the pop-up that follows, you will select another user and transfer the model owner role to that user.
45 -
46 -This way, you are not dependent on a system admin anymore to transfer the role for you.
47 -
48 48  == **Fancy Forum Answers** ==
49 49  
50 50  As always, a gentle reminder to all to ask questions via the Q&A forum. The Q&A forum is available in the eMagiz iPaaS portal, so we can all benefit from the knowledge within the community. For some inspiration, take a look at these forum answers:
51 51  
52 -* [[Groovyscript xls to csv>>https://my.emagiz.com/p/question/172825635700361387||target="blank"]]
42 +* [[Mendix ‘current user property’ vs eMagiz connector v5>>https://my.emagiz.com/p/question/172825635700361185||target="blank"]]
43 +* [[eMagiz warning : Thread dump: *************************************************>>https://my.emagiz.com/p/question/172825635700361286||target="blank"]]
44 +* [[Trimming our backup folder, removing files on local disk.>>https://my.emagiz.com/p/question/172825635700361285||target="blank"]]
53 53  
54 54  == **Key takeaways** ==
55 55