Skip to Content

Changes for page 208 - Controlled State

Last modified by Carlijn Kokkeler on 2024/04/18 13:10
From version 244.1
edited by Danniar Firdausy
on 2023/11/06 13:29
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
Title
... ... @@ -1,1 +1,1 @@
1 -208 - Controlled State
1 +203 - Fast Paced
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.dfirdausy
1 +XWiki.ebakker
Content
... ... @@ -2,56 +2,40 @@
2 2  {{container layoutStyle="columns"}}(((
3 3  [[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]]
4 4  
5 -**Hi there, eMagiz developers!** We have done much work to improve the functionality of our state generation solution so that you can have a better overview of what is happening in your environment.
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 -{{warning}}State generation functionality is only accessible for models with an add-on state generation license.{{/warning}}
7 +== **Release Properties - Early Feedback** ==
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.
8 8  
9 -== **State Generation~*~*** ==
10 -
11 -//__New Page__//
12 -The following page has been added:
13 -* Aggregator: reverse of the splitter, used to combine multiple messages into a single one.
14 -
15 -Added support for ... .
16 -
17 -{{info}}The components are ... .{{/info}}
18 -
19 -== **Metrics Storage Duration** ==
20 -We will ... .
21 -
22 22  == **Feedback Items** ==
23 23  
24 -//__Import from store__//
25 -The button 'Import from Store' in Design will directly open the store instead of showing a pop up asking whether the store should be opened.
12 +//__"All entries" are now cleaned up as part of the migration__//
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.
26 26  
27 -//__Import from store__//
28 -The button 'Import from Store' in Design will directly open the store instead of showing a pop up asking whether the store should be opened.
29 -
15 +//__Trigger ID added to our alerting on the next-generation architecture__//
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 +
30 30  == **Bug Fixes** ==
31 31  
32 -//__Topic and event-processor names__//
33 -The styling of the event streaming canvas in the Create and Deploy phases has been altered slightly to make topic and event-processor names more readable.
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.
34 34  
35 -//__Topic and event-processor names__//
36 -The styling of the event streaming canvas in the Create and Deploy phases has been altered slightly to make topic and event-processor names more readable.
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.
37 37  
38 38  == **Fancy Forum Answers** ==
39 39  
40 40  As always, this is a gentle reminder 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:
41 41  
42 -* [[Message Redelivery blank error message>>https://my.emagiz.com/p/question/172825635703619933||target="blank"]]
43 -* [[Timeout error kafka batch creation>>https://my.emagiz.com/p/question/172825635703620012||target="blank"]]
44 -* [[SFTP Connectivity: Transfering a whole folder structure>>https://my.emagiz.com/p/question/172825635703632587||target="blank"]]
45 -* [[Next generation architecture with dynamic file pickup / filedrop>>https://my.emagiz.com/p/question/172825635703632732||target="blank"]]
30 +* [[Issue with mail server dropping messages>>https://my.emagiz.com/p/question/172825635703530232||target="blank"]]
46 46  
47 -
48 48  == **Key takeaways** ==
49 49  
50 -Thanks to all who helped build and those who tested and gave feedback to improve the product. To end this post, here are some key takeaways for you:
34 +Thanks to all that helped build and those who tested and gave feedback to improve the product. To end this post, here are some key takeaways for you:
51 51  
52 52  * If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
53 53  * If you have feedback or ideas for us, talk to the Platypus
54 -* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
38 +* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
55 55  * Clear your browser cache (Ctrl + Shift + Del)
56 56  * Check out the release notes [here]
57 57  * Start thinking about how the license tracker can aid your development