Changes for page 208 - Controlled State

Last modified by Carlijn Kokkeler on 2024/04/18 13:10

From version 53.1
edited by Erik Bakker
on 2022/11/21 13:48
Change comment: There is no comment for this version
To version 250.3
edited by Danniar Firdausy
on 2023/11/06 17:11
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,82 +2,57 @@
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 its interactions. Furthermore, some minor 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 have a better overview of its implementation in your environment. This overview covers a visibility towards the statistics for Retrieve Latency, Cache Size, Successful and Failed Retrieves. Next to the monitoring for the state generation implementation in your model, several feedback items revolving around user interfacing components in our platform that can improve the user experience are also released. Lastly, some performance improvements and bug fixes have also been implemented.
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 enhancements we made to the 3rd generation runtime and its interaction with the portal.
9 +== **State Generation~*~*** ==
10 10  
11 -//__Migration of JMS backup configuration improved__//
12 -With this release, the configuration of the JMS backup configuration is improved to prevent potential connectivity issues after migrating to the 3rd generation runtime.
11 +//__New Page__//
12 +The following page has been added:
13 +* State generation statistics: Contains the statistics for state generation implementation in your model. This page can be found under Manage->Monitoring, right under the Topic statistics navigation menu. This page provides you with graphs that explains the Retrieve Latency, Cache Size, Successful and Failed Retrieves, which are coming from flows using state generation components. **Note** that this menu will only show for models that has the add-on license for state generation.
13 13  
14 -//__Prechecks on Upgrade option made available for 3rd generation runtime__//
15 -As with the current runtime architecture, you can now also execute the prechecks before automatically upgrading to the latest cloud template on the 3rd generation runtime architecture.
15 +{{info}}The graphs are configured with the same behaviour as graphs in the other statistics pages, meaning that you can also change the time range, zoom in zoom out to the time frame, etc.{{/info}}
16 16  
17 -//__Autogenerated exits can be deployed at once__//
18 -This release has fixed a bug that prevented you from deploying an exit flow correctly.
17 +== **Feedback Items** ==
19 19  
20 -//__Code mapping functionality available on 3rd generation runtime__//
21 -As of this release, code mapping functionality is also available for the 3rd generation runtime. This removes the restriction on migrating to the new 3rd generation runtime for our clients that use the code mapping functionality.
19 +//__Improved Information on Removing a Release Version__//
20 +Users are now informed with a more comprehensive information of why removing a release version that is still active on all environments (i.e., Test, Acceptance, and Production) is failed. Users are now informed in which environment(s) that runs in which runtime(s) that the release version under deletion is still running.
22 22  
23 -//__Improved the performance when activating a release__//
24 -With this release, the performance of activating a release has improved considerably. This means less waiting time when activating a release.
22 +//__Wider and Expandable Fields for XPath Expressions__//
23 +Input fields for XPath expressions located in the Create phase are now made wider and also capable of expanding when the expression registered by the user is too long.
25 25  
26 -//__Failing runtimes won't be restarted indefinitely anymore__//
27 -We have put a cap on this behavior to prevent your logs from exploding due to a failing runtime being restarted indefinitely. As of this release, five attempts will be made to restart a failing runtime. If the runtime can not start correctly after these attempts, the runtime will be stopped.
25 +//__Old Images Cleanup Mechanism__//
26 +We implemented a functionality that removes related unused images upon removal of a release version for on-premises machines. This prevents eMagiz to take resources of the customer’s machine due to the unattended old images.
28 28  
29 -== **Exportable Release Audit** ~* ==
28 +//__Consistent Toggle Switches__//
29 +We are now implementing eMagiz Design System module in our platform and, in this release, we updated all instances of the toggle switch to have a more consistent performance and look & feel.
30 +
31 +== **Bug Fixes** ==
30 30  
31 -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.
33 +//__Topic and event-processor names__//
34 +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.
32 32  
33 -[[image:Main.Images.Release Blog.WebHome@188-release-blog--exportable-release-audit.png]]
36 +//__Topic and event-processor names__//
37 +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.
34 34  
35 -{{warning}}Note that the following restrictions apply when exporting an audit document:
36 - * Works **only** for releases that are promoted and made active on **Production**
37 - * You will **only** see changes made during the **current** calendar year
38 - * On the first of April all objects of the **last** calendar year will be **removed**.
39 - ** As a consequence you cannot download this information anymore **after** the first of April{{/warning}}
40 -
41 -== **Feedback items ** ==
42 -
43 -We have also solved other feedback items besides the flow designer's critical updates.
44 -
45 -//__Improved naming convention on Store related pages__//
46 -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.
47 -
48 -//__Press "Enter" to search on multiple pages__//
49 -In our Daemon Switch release, we added functionality that allowed you to press **Enter** to search on the property overview page. This release has added this functionality to many more pages across the portal. The complete list is as follows.
50 -
51 -* Deploy → Deployment Plan
52 -* Deploy → Properties → History
53 -* Deploy → User Management → Roles
54 -* Manage → Error Messages → Error Messages
55 -* Manage → Error Messages → Flows with Error Messages
56 -* Manage → Error Messages → Exceptions of Error Messages
57 -* Manage → Log Entries
58 -* Manage → Alerts
59 -* Manage → Triggers
60 -* Manage → Tags – Cant find (only Gen2)
61 -* Manage → Notifications
62 -* Manage → Notification Settings
63 -* Manage → Data Usage → History
64 -* Manage → Code mappings → All tabs
65 -
66 66  == **Fancy Forum Answers** ==
67 67  
68 68  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:
69 69  
70 -* [[Synchronous file pick-up>>https://my.emagiz.com/p/question/172825635703197660||target="blank"]]
71 -* [[Receiving e-mail via IMAP or POP3 - Set up>>https://my.emagiz.com/p/question/172825635703197881||target="blank"]]
72 -* [[Best way of Receiving and Sending Mail>>https://my.emagiz.com/p/question/172825635703210149||target="blank"]]
43 +* [[Message Redelivery blank error message>>https://my.emagiz.com/p/question/172825635703619933||target="blank"]]
44 +* [[Timeout error kafka batch creation>>https://my.emagiz.com/p/question/172825635703620012||target="blank"]]
45 +* [[SFTP Connectivity: Transfering a whole folder structure>>https://my.emagiz.com/p/question/172825635703632587||target="blank"]]
46 +* [[Next generation architecture with dynamic file pickup / filedrop>>https://my.emagiz.com/p/question/172825635703632732||target="blank"]]
73 73  
48 +
74 74  == **Key takeaways** ==
75 75  
76 -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 +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:
77 77  
78 78  * If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
79 79  * If you have feedback or ideas for us, talk to the Platypus
80 -* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
55 +* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
81 81  * Clear your browser cache (Ctrl + Shift + Del)
82 82  * Check out the release notes [here]
83 83  * Start thinking about how the license tracker can aid your development
... ... @@ -90,6 +90,6 @@
90 90  {{info}}
91 91  ~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
92 92  
93 -~*~* Indicates a GEN3-only feature.
68 +~*~* Indicates a next-generation-architecture only feature.
94 94  {{/info}})))((({{toc/}}))){{/container}}
95 95  {{/container}}