Skip to Content
Last modified by Carlijn Kokkeler on 2024/04/18 13:11
From version 128.1
edited by Erik Bakker
on 2023/07/17 14:47
Change comment: There is no comment for this version
To version 53.1
edited by Erik Bakker
on 2022/11/21 13:48
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -201 - Be Informed
1 +188 - Close Encounters
Content
... ... @@ -2,56 +2,74 @@
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 worked hard on planning the upcoming Q and finishing up features of the last Q. More on that later. On top of that we have several smaller items as a result of our hackathon efforts to present to you.
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.
6 6  
7 -== **Announcement - Release Properties** ==
8 -As of the next release (202) we will introduce a completely new way of handling properties for all our clients. In the upcoming weeks we will publish additional information on the process, what changes, and how you best manage your properties as of then within the documentation portal. Should you have any questions in advance please contact us at [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]].
7 +== **3rd generation runtime bolstering** ==
9 9  
10 -== ** Deploy Architecture - Apply To Environment improvements ** ==
11 -As of this release we will show you a list of all change that are about to be changed once you press "Apply to environment" in Deploy Architecture. This will ensure that it becomes clearer for users, especially those working together in teams, what will change when pressing this button.
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.
12 12  
13 -//__Enhanced right-hand view within Deployment Plan context__//
14 -When executing your deployment plan we will show specific log entries of the info category that indicate that a container (i.e. runtime) has started up correctly. On top of that we show the warnings and errors in this overview.
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.
15 15  
16 -{{info}}Note that when the JMS container gets restarted connection errors in the logs are a normal thing to witness so keep your eyes peeled for the startup logging on JMS level to gain confidence in the deployment.{{/info}}
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.
17 17  
18 -//__Improved timeout settings when deploying__//
19 -To avoid mismatches between various parts of the infrastructure we have improved the timeout configuration on certain deployment plan steps to reduce the chance that these mismatches occur.
17 +//__Autogenerated exits can be deployed at once__//
18 +This release has fixed a bug that prevented you from deploying an exit flow correctly.
20 20  
21 -{{info}}Note that this fix is part of a new runtime image for the current-generation runtimes. The release notes of this can be found [[here>>doc:Main.Release Information.Runtime Images.WebHome||target="blank"]]{{/info}}
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 -//__Detailed HTTP Statistics now show user info in specific additional cases__//
24 -To solve a bug for a specific client we changed the logic to show the user info (i.e. first part of the api key) in a specific implementation just as we already do in our standard implementations.
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.
25 25  
26 -{{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}}
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.
27 27  
28 -//__Improved loading speed of Manage Dashboard__//
29 -This release improves the loading speed with which all the dashboards in Manage are shown to the user. This will enhance the user experience within the Manage phase.
29 +== **Exportable Release Audit** ~* ==
30 30  
31 -== **Store Improvements** ==
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.
32 32  
33 -//__Importing in Design is improved__//
34 -We have solved a bug that could cause issues when importing something in Design while the accompanying integration was not yet in Create.
33 +[[image:Main.Images.Release Blog.WebHome@188-release-blog--exportable-release-audit.png]]
35 35  
36 -== **Bug Fixes** ==
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}}
37 37  
38 -//__Deprecated reminder pop-up removed__//
39 -We have removed a reminder pop-up on a pending cloud template as it was deprecated and could cause issues when using it in communication with other systems.
41 +== **Feedback items ** ==
40 40  
41 -//__Improved selection area in Flow Designer__//
42 -When working on a large flow you can now select specific areas easily while you are scrolled down further down the flow.
43 +We have also solved other feedback items besides the flow designer's critical updates.
43 43  
44 -//__Improved Kafka settings__//
45 -For all flows that use a Kafka related component within the flow designer we will run a migration to update every single one of them to the new best practices and create a new flow version for them.
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.
46 46  
47 -{{info}}We strongly encourage all users that use these components to update to these new best practices as they increase stability of the cluster and throughput of the solution{{/info}}
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.
48 48  
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 +
49 49  == **Fancy Forum Answers** ==
50 50  
51 51  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:
52 52  
53 -* [[HTTP URL must not be null>>https://my.emagiz.com/p/question/172825635703491908||target="blank"]]
54 -* [[removing the curled brackets in a JSON payload>>https://my.emagiz.com/p/question/172825635703479276||target="blank"]]
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"]]
55 55  
56 56  == **Key takeaways** ==
57 57