Skip to Content

Changes for page 173 - Time Saver

Last modified by Carlijn Kokkeler on 2024/04/18 13:28
From version 25.1
edited by Erik Bakker
on 2022/06/16 16:53
Change comment: There is no comment for this version
To version 26.1
edited by Erik Bakker
on 2022/06/16 16:54
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -1,5 +1,5 @@
1 1  {{container}}{{container layoutStyle="columns"}}(((
2 -
2 +
3 3  [[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]]
4 4  
5 5  **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!
... ... @@ -19,15 +19,15 @@
19 19  
20 20  == **Bug Fixes** ==
21 21  
22 -//__ Being able to delete data model entities that are in use __//
22 +//__Being able to delete data model entities that are in use__//
23 23  
24 24  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.
25 25  
26 -//__ Reserved property names __//
26 +//__Reserved property names__//
27 27  
28 28  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.
29 29  
30 -//__ When importing Store items the associated resource is not always provided to the user __//
30 +//__When importing Store items the associated resource is not always provided to the user__//
31 31  
32 32  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.
33 33