Skip to Content

Changes for page 203 - Fast Paced

Last modified by Carlijn Kokkeler on 2024/04/18 13:12
From version 144.1
edited by Erik Bakker
on 2023/08/15 10:23
Change comment: There is no comment for this version
To version 145.1
edited by Erik Bakker
on 2023/08/15 11:35
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -2,26 +2,26 @@
2 2  {{container layoutStyle="columns"}}(((
3 3  [[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]]
4 4  
5 -**Hi there, eMagiz developers!** In the last few weeks, we have processed some of the early feedback on the release properties. On top of that we have improved the scalability of our complete solution and solved various smaller feedback items.
5 +**Hi there, eMagiz developers!** We have processed some early feedback on the release properties in the last few weeks. On top of that, we have improved the scalability of our complete solution and solved various smaller feedback items.
6 6  
7 7  == **Release Properties - Early Feedback** ==
8 -The release property functionality was well received by the community. However, there was still room for improvement based on some of the early feedback we received from the community. Some of these early feedback items have been addressed in this release. As a result we have updated the layout of the edit screen of a property and have updated our checks on nested properties to avoid missing properties.
8 +The community well received the release property functionality. However, there was still room for improvement based on some of the early feedback from the community. Some of these early feedback items have been addressed in this release. As a result, we have updated the layout of a property's edit screen and our checks on nested properties to avoid missing properties.
9 9  
10 10  == **Feedback Items** ==
11 11  
12 12  //__"All entries" are now cleaned up as part of the migration__//
13 -To avoid problems when removing integrations after the migration towards the next-generation architecture we now clean-up the "all-entries" as part of the migration towards the next-generation architecture.
13 +To avoid problems when removing integrations after migrating toward the next-generation architecture, we now clean up the "all-entries" as part of the migration towards the next-generation architecture.
14 14  
15 15  //__Trigger ID added to our alerting on the next-generation architecture__//
16 -We have added a unique trigger ID to each alert configuration to make the interpretation for our support desk much easier and better manageable.
16 +We added a unique trigger ID to each alert configuration to make the interpretation for our support desk much easier and more manageable.
17 17  
18 18  == **Bug Fixes** ==
19 19  
20 20  //__Ensure no flow can be in a release twice__//
21 -We have fixed a bug that could cause one flow to end up in the same release with two different flow versions. As this will break your solution on various occasions we fixed this.
21 +We have fixed a bug that could cause one flow to end up in the same release with two different flow versions. As this will break your solution on various occasions, we fixed this.
22 22  
23 23  //__Ensure no flow can be in a release twice__//
24 -We have fixed a bug that could cause one flow to end up in the same release with two different flow versions. As this will break your solution on various occasions we fixed this.
24 +We have fixed a bug that could cause one flow to end up in the same release with two different flow versions. As this will break your solution on various occasions, we fixed this.
25 25  
26 26  == **Fancy Forum Answers** ==
27 27