Skip to Content

Changes for page 207 - Aligned State

Last modified by Carlijn Kokkeler on 2024/04/18 13:10
From version 44.1
edited by Erik Bakker
on 2022/11/08 10:05
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
Title
... ... @@ -1,1 +1,1 @@
1 -187 - Integration Sponsor
1 +201 - Be Informed
Content
... ... @@ -2,64 +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 will release several impactful features and enablers to our community. Among others, the next phase of the eMagiz Store will become publicly available. This means that you can now import data models and transformation on top of system messages in Design and accelerators in Create. Furthermore, we will launch a new Beta functionality through some of our clients, enabling you to restore your flow to a previous version.
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.
6 6  
7 -== **Store - Next phase** ==
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]].
8 8  
9 -This release will introduce the next phase of the Store to our whole community. With this new functionality, you can import data model messages (i.e., CDM, API Gateway Data model, or Event Streaming data model) and transformations. Connecting to standardized systems such as Exact Online, Microsoft Graph, Salesforce, and others will become even more accessible.
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.
10 10  
11 -[[image:Main.Images.Release Blog.WebHome@187-release-blog--current-store-offering.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.
12 12  
13 -{{info}}For more information on the Store please check out this [[course>>doc:Main.eMagiz Academy.Microlearnings.Novice.eMagiz Store.WebHome||target="blank"]]. As a reminder, you can find all documentation on all available Store content published by eMagiz [[here>>doc:Main.eMagiz Store.WebHome||target="blank"]].{{/info}}
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 14  
15 -== **New eMagiz Mendix Connector** ==
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.
16 16  
17 -This release introduces a new version of the eMagiz Mendix Connector. This version (6.0.0) will work with the current runtime architecture and the new runtime architecture making the migration from the existing runtime architecture to the new runtime architecture easier. The latest version of the eMagiz Mendix Connector can be found in the Mendix Marketplace and the eMagiz portal.
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}}
18 18  
19 -{{info}}Migrating the runtime from the eMagiz portal works the same as for any other runtime. The migration path can be found [[here>>doc:Main.eMagiz Support.Migration Paths.migration-path-emagiz-runtime-generation-3.WebHome||target="blank"]]{{/info}}
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.
20 20  
21 -== **Flow version restore** ~* ==
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}}
22 22  
23 -On top of that, we will also launch a new Beta feature to the community that allows you to restore your flow to a previous version. This way, you can quickly undo changes made that were incorrect.
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.
24 24  
25 -[[image:Main.Images.Release Blog.WebHome@187-release-blog--flow-version-restore.png]]
31 +== **Store Improvements** ==
26 26  
27 -{{warning}}Note that the following restrictions apply when restoring to a previous version:
28 - * Changes made on definition and transformation level are **not** restored
29 - * You will **not** be able to restore to any flow version that was created before October 17th, 2022
30 - * 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
31 - * Your restored flow version will **not** be automatically committed to Deploy{{/warning}}
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.
32 32  
33 -== **Feedback items ** ==
36 +== **Bug Fixes** ==
34 34  
35 -We have also solved other feedback items besides the flow designer's critical updates.
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.
36 36  
37 -//__Improved help texts Kafka component__//
38 -The help texts on various configuration options and the general help text on multiple Kafka components have been updated to clarify how they work and how you ought to configure them to achieve the best possible result when sending and receiving messages to and from topics within eMagiz.
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.
39 39  
40 -//__Improved warning message when Message redelivery cannot be adequately executed__//
41 -We have improved the warning you get when you cannot retrieve the messages waiting to be redelivered. This helps clarify what is going wrong when a user sees this warning.
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.
42 42  
43 -//__See Flow Designer errors on the Create overview__//
44 -To improve our offering surrounding the new Flow Designer functionality, we now show on the Create overview which of the flows you still have alerts due to a misconfiguration of the flow. This will help to identify ongoing work much more manageable.
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}}
45 45  
46 -[[image:Main.Images.Release Blog.WebHome@187-release-blog--alert-visualized-in-create-overview.png]]
47 -
48 -{{info}}Note that you need to open flows that are currently triggering alerts to show the alert on the Create overview{{/info}}
49 -
50 -== **Bug Fixes** ==
51 -
52 -//__Update Swagger File when changing the order of entities in gateway message__//
53 -In our previous release, we improved how the Swagger file is generated when changing the order of attributes of your gateway message. To make this functionality work for entities, we have made several additional changes to the platform supporting this.
54 -
55 55  == **Fancy Forum Answers** ==
56 56  
57 57  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:
58 58  
59 -* [[Get files using a command via the SFTP protocol>>https://my.emagiz.com/p/question/172825635703184726||target="blank"]]
60 -* [[Take into account API rate limits>>https://my.emagiz.com/p/question/172825635703184597||target="blank"]]
61 -* [[Flow test stuck on initializing>>https://my.emagiz.com/p/question/172825635703184786||target="blank"]]
62 -* [[HTML to XML>>https://my.emagiz.com/p/question/172825635703197357||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"]]
63 63  
64 64  == **Key takeaways** ==
65 65