Wiki source code of 170 - Feedback Galore

Last modified by Carlijn Kokkeler on 2024/04/18 13:29
Show last authors
1 {{container}}{{container layoutStyle="columns"}}(((
2 [[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]]
3
4 **Hi there, eMagiz developers!** In the last couple of weeks, we have started developing several larges features that we will tell more about in the future. On top of that, we have solved a lot of smaller feedback items and nuisances regarding various phases within the eMagiz platform. Among these improvements, we have various flow testing improvements, improved JSON handling within Event Processors, and transfer your model owner role yourself. So let us dive into all that we have to offer this time around!
5
6 == **Flow Testing improvements** ==
7
8 Once again, we have taken several steps to further improve the flow testing functionality within the platform. With this release, we will bring three new improvements.
9
10 //__Pretty printing JSON__//
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
13 [[image:Main.Images.Release Blog.WebHome@170-release-blog-1.jpg]]
14
15 //__All date and times displayed in UTC__//
16 Since we launched flow testing, not all dates and times have been displayed in UTC. However, there was no uniform method of displaying dates and times was confusing for users. As a result, we now show all dates and times in UTC, just as in the rest of the portal.
17
18 //__Being able to execute a flow test while having resources with a lengthy name__//
19 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.
20
21 As of now, we have removed this restriction. This allows you to execute flow tests regardless of your naming convention for custom resources.
22
23 == **Feedback items ** ==
24
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.
27
28 As of this release, we have solved this problem by visualizing the expression so that it is easy to interpret it correctly.
29
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.
32
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.
34
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.
37
38
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.
41
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.
44
45 This way, you are not dependent on a system admin anymore to transfer the role for you.
46
47 == **Fancy Forum Answers** ==
48
49 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:
50
51 * [[Groovyscript xls to csv>>https://my.emagiz.com/p/question/172825635700361387||target="blank"]]
52
53 == **Key takeaways** ==
54
55 Thanks to all that help build, those who tested and gave feedback to improve the product. To end this post, here are some key takeaways for you:
56
57 * If you have questions surrounding our Program Increment Planning, please get in touch with
58 * If you have feedback or ideas for us, talk to the Platypus
59 * Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
60 * Clear your browser cache (Ctrl + Shift + Del)
61 * Check out the release notes [[here>>doc:Main.Release Information.Portal.Feedback Galore.WebHome||target="blank"]]
62 * Start thinking about how the license tracker can aid your development
63 * Start thinking about major, minor, and patch
64 * Upgrade to the latest build number
65 * Keep making great integrations
66
67 Let's stay in touch and till next time!
68
69 {{info}}
70 ~* Indicates a Beta feature. If you would like to get access to this beta feature please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
71
72 ~*~* Indicates a GEN3-only feature.
73 {{/info}})))((({{toc/}}))){{/container}}{{/container}}