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

Summary

Details

Page properties
Content
... ... @@ -10,51 +10,48 @@
10 10  == ** Deploy Architecture - Apply To Environment improvements ** ==
11 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.
12 12  
13 -[[image:Main.Images.Release Blog.WebHome@201-release-blog--apply-to-environment-example.png]]
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.
14 14  
15 -== ** Breadcrumb navigation in eMagiz ** ==
16 -With this release we introduce the "breadcrumb" navigation in certain parts of eMagiz. This will mostly be noticed, and have impact, in the Create phase when you are checking out your transformation or system message on flow level. Apart from there the navigation is implemented consistently across the portal for a unified look and feel.
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}}
17 17  
18 -[[image:Main.Images.Release Blog.WebHome@201-release-blog--breadcrumb-navigation-example.png]]
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.
19 19  
20 -== **Feedback Items** ==
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}}
21 21  
22 -//__Improved layout of catalog page in Design__//
23 -We have improved the layout of the API Catalog overview in Design for our API Gateway users. Among others, we have introduced a scrollbar to get a better overview when having several operations.
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.
24 24  
25 -//__Improved layout of "Edit integration" pop-up for API Gateway integrations__//
26 -As of now the full path of your backend system will be shown when opening the "Edit integration" pop-up on your API Gateway integration.
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}}
27 27  
28 -//__Additional help texts on Design Architecture__//
29 -We have improved the help texts in Design Archicture in relation to the Event Streaming topic storage overview.
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.
30 30  
31 -//__Improved Audit Trail on several places__//
32 -In several places in the portal we have improved the audit trail to better specify who changed what at which point in time.
31 +== **Store Improvements** ==
33 33  
34 -//__Removed the erroneous alert on message mapping when having a passthrough API__//
35 -This release removes the erroneous alert people reported on "errors in message mapping" for a passthrough API.
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.
36 36  
37 37  == **Bug Fixes** ==
38 38  
39 -//__Avoid clicking on other components while deleting another__//
40 -To avoid unexpected behavior we now ensure that nothing can be selected once you see the "deletion" pop-up when you want to remove something in the flow designer.
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 41  
42 -//__Improved validation feedback in migrating to the next-generation architecture__//
43 -We have improved several things with regards to the validation feedback when migrating to the next-generation architecture.
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.
44 44  
45 -//__Make sure that user credentials can be viewed with view rights__//
46 -This release makes sure that the user credentials in Deploy can be viewed with view rights and not only when having edit rights.
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.
47 47  
48 -//__Refresh behavior within the deployment plan is fixed__//
49 -This release changes the refresh behavior within the deployment plan to show, once more, the "to be installed" flows before the user presses Execute.
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}}
50 50  
51 51  == **Fancy Forum Answers** ==
52 52  
53 53  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:
54 54  
55 -* [[Replacing Legacy eMagiz-Mendix Connector: Migration Plan>>https://my.emagiz.com/p/question/172825635703517317||target="blank"]]
56 -* [[Unknown character(s) does not create error message.>>https://my.emagiz.com/p/question/172825635703517488||target="blank"]]
57 -* [[Split gateway configuration for local GEN3 gateway>>https://my.emagiz.com/p/question/172825635703517580||target="blank"]]
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"]]
58 58  
59 59  == **Key takeaways** ==
60 60