Skip to Content

Changes for page 208 - Controlled State

Last modified by Carlijn Kokkeler on 2024/04/18 13:10
From version 46.1
edited by Erik Bakker
on 2022/11/21 12:31
Change comment: There is no comment for this version
To version 243.1
edited by Danniar Firdausy
on 2023/11/06 13:28
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -188 - Close Encounters
1 +208 - Controlled State
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.ebakker
1 +XWiki.dfirdausy
Content
... ... @@ -2,80 +2,56 @@
2 2  {{container layoutStyle="columns"}}(((
3 3  [[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]]
4 4  
5 -**Hi there, eMagiz developers!** This release is characterized mainly by our efforts to bolster our 3rd generation runtime and all the interactions with it. Furthermore, some smalller fixes and beta features will be released to the community.
5 +**Hi there, eMagiz developers!** We have done much work to improve the functionality of our state generation solution so that you can be more in control of what is happening in your environment.
6 6  
7 -== **3rd generation runtime bolstering** ==
7 +{{warning}}State generation functionality is only accessible for models with an add-on state generation license.{{/warning}}
8 8  
9 -This release will introduce various improvements for our 3rd generation runtime. Below you will find the most noteworthy improvements we made to the 3rd generation runtime and the interaction with it.
9 +== **State Generation~*~*** ==
10 10  
11 -//__Migration of JMS backup configuration improved__//
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.
12 12  
13 -//__Prechecks on Upgrade option made available for 3rd generation runtime__//
15 +Added support for ... .
14 14  
15 -//__Autogenerated exits can be deployed at once__//
17 +{{info}}The components are ... .{{/info}}
16 16  
17 -//__Code mapping functionality available on 3rd generation runtime__//
19 +== **Metrics Storage Duration** ==
20 +We will ... .
18 18  
19 -//__Improved the performance of deploying or activating a release__//
22 +== **Feedback Items** ==
20 20  
21 -//__Failing runtimes won't be restarted indefinetly anymore__//
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.
22 22  
23 -== **Exportable Release Audit** ~* ==
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 +
30 +== **Bug Fixes** ==
24 24  
25 -On top of that, we will also launch a new Beta feature to the community that allows you to export an audit document of your (Production) release.
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.
26 26  
27 -[[image:Main.Images.Release Blog.WebHome@187-release-blog--flow-version-restore.png]]
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.
28 28  
29 -{{warning}}Note that the following restrictions apply when exporting an audit document:
30 - * Changes made on definition and transformation level are **not** restored
31 - * You will **not** be able to restore to any flow version that was created before October 17th, 2022
32 - * You will **not** be able to restore your flow to the original version created by eMagiz. You can use the reset function if you want this state back
33 - * Your restored flow version will **not** be automatically committed to Deploy{{/warning}}
34 -
35 -== **Feedback items ** ==
36 -
37 -We have also solved other feedback items besides the flow designer's critical updates.
38 -
39 -//__Data Sink Refactor__//
40 -We have made some infrastructural changes to how data sink messages are stored and can be retrieved from the portal. Should there be changes needed on your end we will contact your seperately.
41 -
42 -//__Improved naming convention on Store related pages__//
43 -We have improved various display names to ensure that it is clear from the naming that store content can be implemented in all integration patterns.
44 -
45 -//__Press "Enter" to search on multiple pages__//
46 -In our Daemon Switch release we added functionality that allowed you to press **Enter** to search on the property overview page. With this release we have added this functionality to many more pages across the portal. The complete list is as follows
47 -
48 -* Deploy → Deployment Plan
49 -* Deploy → Properties → History
50 -* Deploy → User Management → Roles
51 -* Manage → Error Messages → Error Messages
52 -* Manage → Error Messages → Flows with Error Messages
53 -* Manage → Error Messages → Exceptions of Error Messages
54 -* Manage → Log Entries
55 -* Manage → Alerts
56 -* Manage → Triggers
57 -* Manage → Tags – Cant find (only Gen2)
58 -* Manage → Notifications
59 -* Manage → Notification Settings
60 -* Manage → Data Usage → History
61 -* Manage → Code mappings → All tabs
62 -
63 63  == **Fancy Forum Answers** ==
64 64  
65 65  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:
66 66  
67 -* [[Get files using a command via the SFTP protocol>>https://my.emagiz.com/p/question/172825635703184726||target="blank"]]
68 -* [[Take into account API rate limits>>https://my.emagiz.com/p/question/172825635703184597||target="blank"]]
69 -* [[Flow test stuck on initializing>>https://my.emagiz.com/p/question/172825635703184786||target="blank"]]
70 -* [[HTML to XML>>https://my.emagiz.com/p/question/172825635703197357||target="blank"]]
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"]]
71 71  
47 +
72 72  == **Key takeaways** ==
73 73  
74 -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:
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:
75 75  
76 76  * If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
77 77  * If you have feedback or ideas for us, talk to the Platypus
78 -* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
54 +* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
79 79  * Clear your browser cache (Ctrl + Shift + Del)
80 80  * Check out the release notes [here]
81 81  * Start thinking about how the license tracker can aid your development
... ... @@ -88,6 +88,6 @@
88 88  {{info}}
89 89  ~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
90 90  
91 -~*~* Indicates a GEN3-only feature.
67 +~*~* Indicates a next-generation-architecture only feature.
92 92  {{/info}})))((({{toc/}}))){{/container}}
93 93  {{/container}}