Changes for page 173 - Time Saver
Last modified by Carlijn Kokkeler on 2024/04/18 13:28
From version 36.1
edited by Carlijn Kokkeler
on 2024/04/18 13:28
on 2024/04/18 13:28
Change comment:
There is no comment for this version
Summary
-
Page properties (3 modified, 0 added, 0 removed)
Details
- Page properties
-
- Title
-
... ... @@ -1,1 +1,1 @@ 1 - 173 -Time Saver1 +Time Saver - Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki. CarlijnKokkeler1 +XWiki.eMagiz - Content
-
... ... @@ -1,4 +1,5 @@ 1 1 {{container}}{{container layoutStyle="columns"}}((( 2 + 2 2 [[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]] 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! ... ... @@ -18,15 +18,15 @@ 18 18 19 19 == **Bug Fixes** == 20 20 21 -//__Being able to delete data model entities that are in use__// 22 +//__ Being able to delete data model entities that are in use __// 22 22 23 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. 24 24 25 -//__Reserved property names__// 26 +//__ Reserved property names __// 26 26 27 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 28 29 -//__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 __// 30 30 31 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 32 ... ... @@ -46,7 +46,7 @@ 46 46 * If you have feedback or ideas for us, talk to the platypus 47 47 * Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these. 48 48 * Clear your browser cache (Ctrl + Shift + Del) 49 -* Check out the release notes [ [here>>doc:Main.Release Information.Portal.Time Saver.WebHome||target="blank"]]50 +* Check out the release notes [here] 50 50 * Start thinking about how the license tracker can aid your development 51 51 * Start thinking about major, minor, and patch 52 52 * Upgrade to the latest build number ... ... @@ -58,4 +58,4 @@ 58 58 ~* Indicates a Beta feature. If you would like to get access to this beta feature please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]] 59 59 60 60 ~*~* Indicates a GEN3-only feature. 61 -{{/info}})))((( {{toc/}}))){{/container}}{{/container}}62 +{{/info}})))((())){{/container}}{{/container}}