Skip to Content

Changes for page 170 - Feedback Galore

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

Summary

Details

Page properties
Content
... ... @@ -9,6 +9,7 @@
9 9  
10 10  //__Pretty printing JSON__//
11 11  To make the comparison between your expected and actual message easier when dealing with JSON messaging, we will now “pretty-print” your JSON to make it more easily readable.
12 +
12 12  [[image:Main.Images.Release Blog.WebHome@171-release-blog-1.jpg]]
13 13  
14 14  //__All date and times displayed in UTC__//
... ... @@ -18,44 +18,30 @@
18 18  Before, it was not possible to execute a flow test when one of the resources linked to your flow had a big name (more than 100 characters). Therefore, you needed to rename your resource to use the flow testing functionality in these situations.
19 19  
20 20  As of now, we have removed this restriction. This allows you to execute flow tests regardless of your naming convention for custom resources.
21 -
22 22  
23 -
24 -==** Data models and transformations in eMagiz Store** ==
25 -//The following feature is a Beta feature and is therefor available upon request. Don’t hesitate to contact us at productmanagement@emagiz.com if you are interested in becoming an early adopter.//
23 +== **Feedback items ** ==
26 26  
27 -With this release, we will make the last set of improvements to the eMagiz Store, and we’ll start to provide content within the eMagiz Store. We can unlock the latest advances, including content to the public in the upcoming release. So keep your eyes open for more information!
25 +//__Correctly display expression in view mode - Create Transformation__//
26 +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.
28 28  
29 -== **Old Transformation Tooling - Deprecated **==
30 -As a gentle reminder to all, we would like to highlight that the old transformation tooling will be deprecated after the 1st of June. We will execute the migration to update the resources in each flow on that day. Note that the migration will not create a new flow version or change the user that changed the resource last as we make no functional changes to the resources themselves. For detailed information, please keep an eye out for updates on https://status.emagiz.com.
31 -
32 -== **Bug Fixes** ==
28 +As of this release, we have solved this problem by visualizing the expression so that it is easy to interpret it correctly.
33 33  
34 -//__Improved Loading Time Flow Designer__//
35 -As of this release, you cannot define the same port twice in the routes you can configure in the eMagiz Cloud. This is done to prevent situations that will break the setup within the eMagiz Cloud.
30 +//__JSON related transformations - Event processors__//
31 +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.
36 36  
37 -//__Block adding the same port twice in the eMagiz Cloud route__//
38 -As of now, you will be able to press Enter even when you forgot to enter an MFA code the first time or filled in an incorrect MFA code, for example. Furthermore, we have slightly improved the look and feel of the login through MFA.
39 -
40 -//__Removing all-entry components__//
41 -Before, it could happen that specific components remained in an all-entry once you removed an onramp. This will ensure that all parts that need to be deleted are indeed deleted.
42 -
43 -== **Feedback items ** ==
33 +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.
44 44  
45 -Apart from the key updates around functionality, we have also solved other feedback items.
35 +//__Option to hide 'auto-delete' release pop-up__//
36 +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.
46 46  
47 -//__Disable data model rights for a model owner__//
48 -With this release, we have made it possible for the model owner to revoke their access to the eMagiz data models (i.e., CDM, API Gateway Model, and Event Streaming Model).
49 49  
50 -//__Masking properties of type password in flow testing__//
51 -As of now, we will mask all properties of type password within our flow testing offering. This to mimic the behavior of handling properties in the Deploy phase of eMagiz.
52 -
53 -//__Topic limits are not changeable for users anymore__//
54 -As there are contractual agreements between customers and eMagiz that define the limits to using storage within our Event Streaming offering, we want to prevent any user from exceeding those limits without us knowing. Instead, we ensure the platform’s stability and prevent misuse of the offered functionality by enforcing this.
39 +//__Validation UI Error for missing technical name Tenant__//
40 +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.
55 55  
56 -//__Refresh button on the transformation__//
57 -The refresh button on the transformation in Create is back again to be used if needed.
42 +//__Transfer model owner role to another individual__//
43 +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.
58 58  
45 +This way, you are not dependent on a system admin anymore to transfer the role for you.
59 59  
60 60  == **Fancy Forum Answers** ==
61 61