Skip to Content

Changes for page 180 - Deck Paint

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

Summary

Details

Page properties
Content
... ... @@ -3,29 +3,35 @@
3 3  
4 4  **Hi there, eMagiz developers!** In the last couple of weeks, we have worked on various main platform features. Sadly they are not yet ready enough to release to you guys. We did, however, improve the platform in different more minor ways. Among these improvements, we have improved the speed of handling error messages and creating models by hand. Furthermore, we have several more minor improvements and bug fixes for you. So let us dive into all that we have to offer this time around!
5 5  
6 -== **nfrastructure Update** ==
6 +== **Save and Add Attributes** ==
7 7  
8 -As you might already have seen via the notifications sent from our status page (https://status.emagiz.com), we will update our infrastructure with our upcoming release. This will lay the foundation for more infrastructural changes in our future. For specific information, please check out the notifications via our status page.
8 +When adding multiple attributes by hand to a data model, you need to access the context menu, select the option Add attribute, add the attribute, Save the attribute and repeat that process for every single attribute. We have now introduced a new option when adding attributes to your data models and system messages to speed up this process. This way, you can save and add another attribute by pressing the “Save and add new” button. This way, you don't have to navigate via the context menu for every attribute you want to save.
9 9  
10 -[[image:Main.Images.Release Blog.WebHome@178-release-blog-1.jpg]]
10 +[[image:Main.Images.Release Blog.WebHome@time-saver--save-and-add-attributes.png]]
11 11  
12 - == **Bug Fixes** ==
12 +== **Other Feedback items ** ==
13 13  
14 -//__Update eMagiz Slot Status does not lead to logging errors__//
15 -With this release, we have made several improvements in retrieving the eMagiz Slot Status when a user executes an action on the eMagiz Cloud. These improvements will resolve logging errors within the platform.
16 -
17 -== ** Feedback items ** ==
14 +Apart from the hide/show tasks functionality, we have also solved other feedback items.
18 18  
19 -Apart from the key updates around functionality, we have also solved other feedback items.
16 +//__Make Flow Testing available for the new generation runtime__//
17 +As of this release, the flow testing functionality is also made available for all processes that already run the new generation runtime (GEN3).
20 20  
21 -//__Notify model owner when mails are sent to deactivated users__//
22 -We will notify model owners via mail that their alerting sends emails to deactivated users within the platform with this release. Furthermore, once we encounter a notification setting in which a deactivated user is part of the recipients, we will remove the user from the notifications (if possible).
19 +== **Bug Fixes** ==
23 23  
24 -//__Updated infographic Capture__//
25 -As of now, we have updated the infographic on the Capture phase to incorporate the new look and feel and explain the updated functionality in Capture.
21 +//__Being able to delete data model entities that are in use__//
26 26  
27 - == **Fancy Forum Answers** ==
23 +Previously, it was possible to delete an entity on the data model level that was still in use in a transformation. This could lead to catastrophic problems when someone unintentionally deleted an essential entity for many transformations. As of this release, we have implemented a check that prevents you from deleting any entity still in use in a message or transformation.
28 28  
25 +//__Reserved property names__//
26 +
27 +As of this release, we have defined various forbidden names for properties. One example is creating any property that starts with emagiz. This way, we prevent problems when starting up your solution.
28 +
29 +//__When importing Store items the associated resource is not always provided to the user__//
30 +
31 +Previously, you could import items from the store without receiving the associated resource rendering the import useless. With this release, we made sure that you also get the resource with it when importing the store item.
32 +
33 +== **Fancy Forum Answers** ==
34 +
29 29  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:
30 30  
31 31  * [[Is it possible to split a JSON message into multiple smaller messages and how is this possible?>>https://my.emagiz.com/p/question/172825635700362585||target="blank"]]