Skip to Content

Changes for page 213 - Joyful Journeys

Last modified by Carlijn Kokkeler on 2024/04/18 13:07
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 133.1
edited by Erik Bakker
on 2023/08/01 14:11
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -187 - Integration Sponsor
1 +202 - New Equilibrium
Content
... ... @@ -2,64 +2,70 @@
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 crossed our t's and dotted our i's on the release properties functionality that will impact the day to day life of every user working within the platform. The focus of the release blog will consequently also be on this subject. On top of that we have several additional smaller feedback item coming from our hackathon efforts that are now released to you.
6 6  
7 -== **Store - Next phase** ==
7 +== **Release Properties** ==
8 +As of this release, we will introduce a new way of handling properties for all our clients. This change intends to solidify the relationship between a release and a property value. Before, in the current generation architecture, timing of changing properties was crucial to avoid costly mistakes on Production. On top of that it was not always clear whether a property value was indeed updated as it was not linked to something that was deployed. These considerations let us to change the property management behavior not only on our next-generation architecture but also on our current generation architecture. Having said that, there are several key changes compared to the current way of managing your properties. Most notably among these are:
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 +* The current properties tab in Deploy will disappear. The new overview of the properties (and their values) can be found under the "Create phase release" in Deploy -> Releases
11 +* Property placeholders (i.e. the names of properties as given in Create) are now automatically created for you. This to avoid mistakes when filling them in.
12 +* When adding or editing a property you can *now* select multiple runtimes for which the property applies. This is mainly beneficial for those running in a double lane setup or having a distributed landscape of containers.
13 +* A, for most, new concept of a "property release" is introduced. With the help of this functionality you can easily change a property on Production without having to create a completely new release in Test and promote it to the Production environment.
10 10  
11 -[[image:Main.Images.Release Blog.WebHome@187-release-blog--current-store-offering.png]]
15 +{{info}}For more information please check out the following microlearnings:
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}}
17 +* [[Property Management>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.crashcourse-platform-deploy-property-management-new.WebHome||target="blank"]]
18 +* [[Actualize properties - current generation architecture>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.crashcourse-platform-deploy-actualize-properties-new.WebHome||target="blank"]]
19 +* [[Actualize properties - next generation architecture>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.crashcourse-platform-deploy-actualize-properties-gen3-new.WebHome||target="blank"]]
14 14  
15 -== **New eMagiz Mendix Connector** ==
21 +Should you have any questions in advance, please get in touch with us at [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]].
22 +{{/info}}
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.
24 +== ** Manage - Next generation graphs improvements ** ==
25 +As of this release, we will create a condensed view of your metrics when zooming out in the Manage phase graphs. This will significantly improve the performance of the manage graphs as we retrieve and show less fine-grained information when zooming out.
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}}
27 +[[image:Main.Images.Release Blog.WebHome@202-release-blog--manage-graphs-zoomed-out.png]]
20 20  
21 -== **Flow version restore** ~* ==
29 +== **Feedback Items** ==
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.
31 +//__Improved editability when testing in eMagiz wihout Edit rights in Create__//
32 +Without having edit rights in the Create phase you could already do a lot on the level of flow tests in eMagiz. However, there were some oversights we missed during the implementation. These have been fixed allowing those without edit rights to now also change the name and description of the test case.
24 24  
25 -[[image:Main.Images.Release Blog.WebHome@187-release-blog--flow-version-restore.png]]
34 +//__Improved auditability on Deploy Architecture__//
35 +To improve the audtiability on Deploy Architecture we now also log when someone with Admin rights changes specific functions on this level (i.e. Fixed IP).
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}}
37 +//__Test your own exported work__//
38 +We have now made it possible to test your own exported work to the Store before it gets approved. This will increase the quality of store items we have, and our partners, have on offer within the store.
32 32  
33 -== **Feedback items ** ==
40 +{{info}}In case the concept of the store is new for you please check out this [[Fundamental>>doc:Main.eMagiz Academy.Fundamentals.fundamental-emagiz-store.WebHome||target="blank"]]{{/info}}
34 34  
35 -We have also solved other feedback items besides the flow designer's critical updates.
42 +//__Improved Audit Trail on several places__//
43 +In several places in the portal, we have improved the audit trail to specify better who changed what at which point in time.
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.
45 +//__Removed the erroneous alert on message mapping when having a passthrough API__//
46 +This release removes the erroneous alert people reported on "errors in message mapping" for a passthrough API.
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.
48 +== **Bug Fixes** ==
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.
50 +//__Avoid clicking on other components while deleting another__//
51 +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.
45 45  
46 -[[image:Main.Images.Release Blog.WebHome@187-release-blog--alert-visualized-in-create-overview.png]]
53 +//__Improved validation feedback in migrating to the next-generation architecture__//
54 +We have improved the validation feedback when migrating to the next-generation architecture.
47 47  
48 -{{info}}Note that you need to open flows that are currently triggering alerts to show the alert on the Create overview{{/info}}
56 +//__Make sure that user credentials can be viewed with view rights__//
57 +This release makes sure that the user credentials in Deploy can be considered with view rights and not only when having edit rights.
49 49  
50 -== **Bug Fixes** ==
59 +//__Refresh behavior within the deployment plan is fixed__//
60 +This release changes the refresh behavior within the deployment plan to show, once more, the "to be installed" flows before the user presses Execute.
51 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"]]
66 +* [[Replacing Legacy eMagiz-Mendix Connector: Migration Plan>>https://my.emagiz.com/p/question/172825635703517317||target="blank"]]
67 +* [[Unknown character(s) does not create error message.>>https://my.emagiz.com/p/question/172825635703517488||target="blank"]]
68 +* [[Split gateway configuration for local GEN3 gateway>>https://my.emagiz.com/p/question/172825635703517580||target="blank"]]
63 63  
64 64  == **Key takeaways** ==
65 65