Skip to Content

Changes for page 207 - Aligned State

Last modified by Carlijn Kokkeler on 2024/04/18 13:10
From version 48.1
edited by Erik Bakker
on 2022/11/21 13:11
Change comment: There is no comment for this version
To version 119.1
edited by Erik Bakker
on 2023/06/05 14:27
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -188 - Close Encounters
1 +199 - Home Improvements
Content
... ... @@ -2,77 +2,44 @@
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!** In the last few weeks, we have worked hard on improving various aspects of our home. Among others we have improved the logging, alerting, and security of our next-generation architecture. On top of that we have improved the inner workings of the store and the certificate management for those of us using the Event Streaming pattern.
6 6  
7 -== **3rd generation runtime bolstering** ==
7 +== **Next generation improvements and bug fixes** ==
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 +//__Enhanced overview of the HTTP Statistics__//
10 +As of now all resources that have been called atleast once since deploying them will now show up in the left-bottom graph of the HTTP Statistics. This will make it easier to see whether a particular operation was called within a timeframe. On top of that it makes comparing data on various operations easier. In here you can also filter on one (by pressing the + icon) or more by clicking on the filter icon. In case you want to sort the table in a different manner you can click on the name of the column on which you want to sort.
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.
12 +//__Reason why runtime cannot start is now in the vast majority of cases reported back__//
13 +In this release, we have improved the way we report failures during startup of runtimes. This will ensure that it becomes much easier to pinpoint what went wrong upon startup.
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}}Note that this fix is part of a new runtime image for the next-generation runtimes. The release notes of this can be found [[here>>doc:Main.Release Information.Runtime Images.WebHome||target="blank"]]{{/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 +//__Forced congestion control__//
18 +To reduce the number of repeating mails within a 10 minute window we have now forced congestion control on all alerts generated via the platform.
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.
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.
21 +//__Improved validation errors on the invalid configuration of HTTP outbound components__//
22 +This release fixes and re-introduces the option to execute your actions on the eMagiz per zone or all at once when running in a double-lane Docker setup.
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.
24 +//__Improved migration behavior__//
25 +This release introduces several improvements concerning the migration behavior via "Transfer settings from Design." Among these are:
26 +A smoother migration of your JMS (and backup JMS) process.
27 +Shortening of names that otherwise would be too long, additional feedback given to the user.
28 +Feedback when the migration process is finished.
28 28  
29 -== **Exportable Release Audit** ~* ==
30 +//__Additional checks when deploying__//
31 +This release introduces additional checks when deploying. Among others, we have added a check to prevent you from deploying two flows that use the same resource with differing versions. Not stopping this can cause issues with deployments and even worse with the functional behavior of the flows, as it leads to the situation in which a validation error might trigger on one offramp but not on the other.
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 +== **Store Improvements** ==
32 32  
33 -[[image:Main.Images.Release Blog.WebHome@187-release-blog--flow-version-restore.png]]
35 +== **Event Streaming - Certificate Management** ==
34 34  
35 -{{warning}}Note that the following restrictions apply when exporting an audit document:
36 - * Changes made on definition and transformation level are **not** restored
37 - * You will **not** be able to restore to any flow version that was created before October 17th, 2022
38 - * 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
39 - * Your restored flow version will **not** be automatically committed to Deploy{{/warning}}
40 -
41 -== **Feedback items ** ==
42 -
43 -We have also solved other feedback items besides the flow designer's critical updates.
44 -
45 -//__Data Sink Refactor__//
46 -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 you separately.
47 -
48 -//__Improved naming convention on Store related pages__//
49 -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.
50 -
51 -//__Press "Enter" to search on multiple pages__//
52 -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.
53 -
54 -* Deploy → Deployment Plan
55 -* Deploy → Properties → History
56 -* Deploy → User Management → Roles
57 -* Manage → Error Messages → Error Messages
58 -* Manage → Error Messages → Flows with Error Messages
59 -* Manage → Error Messages → Exceptions of Error Messages
60 -* Manage → Log Entries
61 -* Manage → Alerts
62 -* Manage → Triggers
63 -* Manage → Tags – Cant find (only Gen2)
64 -* Manage → Notifications
65 -* Manage → Notification Settings
66 -* Manage → Data Usage → History
67 -* Manage → Code mappings → All tabs
68 -
69 69  == **Fancy Forum Answers** ==
70 70  
71 71  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:
72 72  
73 -* [[Synchronous file pick-up>>https://my.emagiz.com/p/question/172825635703197660||target="blank"]]
74 -* [[Receiving e-mail via IMAP or POP3 - Set up>>https://my.emagiz.com/p/question/172825635703197881||target="blank"]]
75 -* [[Best way of Receiving and Sending Mail>>https://my.emagiz.com/p/question/172825635703210149||target="blank"]]
41 +* [[How to determine the system definition for this sample message in JSON?>>https://my.emagiz.com/p/question/172825635703440852||target="blank"]]
42 +* [[Instability in JMS connection>>https://my.emagiz.com/p/question/172825635703440717||target="blank"]]
76 76  
77 77  == **Key takeaways** ==
78 78