Skip to Content
Last modified by Carlijn Kokkeler on 2024/04/18 13:11
From version 131.1
edited by Erik Bakker
on 2023/08/01 13:48
Change comment: There is no comment for this version
To version 56.1
edited by Erik Bakker
on 2022/12/06 14:58
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -202 - New Equilibrium
1 +189 - Private Eye
Content
... ... @@ -2,68 +2,71 @@
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 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.
5 +**Hi there, eMagiz developers!** Our release of the Private store functionality characterizes this release. This functionality allows some users to export content to a private store that is only accessible within the company and could be published to the public store of eMagiz. On top of that, we resolved some of the limitations on the 3rd generation runtime. Furthermore, some minor fixes and beta features will be released to the community.
6 6  
7 -== **Release Properties** ==
8 -As of this release, we will introduce a new way of handling properties for all our clients. There are several key changes compared to the current way of managing your properties.
7 +== **Private Store** ==
8 +On top of our general store, in which eMagiz currently publishes Store content relevant to both the Design and Create phases of eMagiz, we have added the private store functionality. This store works precisely the same as the general store. However, only users belonging to the same company as the exporter can import the store content (after it is approved).
9 9  
10 -{{info}}For more information please check out the following microlearnings:
10 +{{warning}}Other users can see the store content but are not able to import the store content. They will be notified to them when they try to do so.{{/warning}}
11 11  
12 -*
13 -*
14 -*
12 +== **3rd generation runtime bolstering** ==
15 15  
16 -Should you have any questions in advance, please get in touch with us at [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]].
17 -{{/info}}
14 +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.
18 18  
19 -== ** Deploy Architecture - Apply To Environment improvements ** ==
20 -As of this release, we will show you a list of all changes about to be changed once you press "Apply to the environment" in Deploy Architecture. This will make it clearer for users, especially those working in teams, what will change when pressing this button.
16 +//__SOAP and REST web services migration including splitting them__//
17 +With this release, we have released the migration process that will allow you to migrate SOAP and REST web services to the 3rd generation runtime and at the same time you can directly split the all-entry to get rid of that construction alltogether. A specific migration path for this will be published in the documentation portal.
21 21  
22 -[[image:Main.Images.Release Blog.WebHome@201-release-blog--apply-to-environment-example.png]]
19 +//__Changing SSL settings for 3rd generation runtime models works__//
20 +As with the current runtime architecture, you can now also change the SSL settings if needed for a model running in the 3rd generation runtime.
23 23  
24 -== ** Breadcrumb navigation in eMagiz ** ==
25 -This release introduces the "breadcrumb" navigation in certain parts of eMagiz. This will mostly be noticed and impact the Create phase when you check out your transformation or system message on the flow level. Apart from there, the navigation is implemented consistently across the portal for a unified look and feel.
22 +//__Improved migration for JMS flows__//
23 +This release will improve the migration of JMS flows when migrating to the 3rd generation runtime.
26 26  
27 -[[image:Main.Images.Release Blog.WebHome@201-release-blog--breadcrumb-navigation-example.png]]
25 +{{warning}}If you already migrated your JMS flow you should execute a "Reset" action on JMS level to get these changes in your model{{/warning}}
28 28  
29 -== **Feedback Items** ==
27 +//__Removed the ability to add "Debug components" to a flow running in the 3rd generation runtime architecture__//
28 +As of this release, you cannot add debug components anymore on a flow that is already migrated to the 3rd generation runtime. This is because this functionality will not work in the 3rd generation runtime and would break your flow.
30 30  
31 -//__Improved layout of catalog page in Design__//
32 -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 of several operations.
30 +//__Deployment plan is updated correctly when completly migrated to the 3rd generation runtime architecture__//
31 +We have fixed a bug that generated an incorrect default deployment plan once you were fully migrated to the 3rd generation runtime.
33 33  
34 -//__Improved layout of "Edit integration" pop-up for API Gateway integrations__//
35 -Currently, the full path of your backend system will be shown when opening the "Edit integration" pop-up on your API Gateway integration.
33 +== **Feedback items ** ==
36 36  
37 -//__Additional help texts on Design Architecture__//
38 -We have improved the help texts in Design Architecture concerning the Event Streaming topic storage overview.
35 +We have also solved other feedback items besides the flow designer's critical updates.
39 39  
40 -//__Improved Audit Trail on several places__//
41 -In several places in the portal, we have improved the audit trail to specify better who changed what at which point in time.
37 +//__Improved naming convention on Store related pages__//
38 +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.
42 42  
43 -//__Removed the erroneous alert on message mapping when having a passthrough API__//
44 -This release removes the erroneous alert people reported on "errors in message mapping" for a passthrough API.
40 +//__Press "Enter" to search on multiple pages__//
41 +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.
45 45  
46 -== **Bug Fixes** ==
43 +* Deploy → Deployment Plan
44 +* Deploy → Properties → History
45 +* Deploy → User Management → Roles
46 +* Manage → Error Messages → Error Messages
47 +* Manage → Error Messages → Flows with Error Messages
48 +* Manage → Error Messages → Exceptions of Error Messages
49 +* Manage → Log Entries
50 +* Manage → Alerts
51 +* Manage → Triggers
52 +* Manage → Tags – Cant find (only Gen2)
53 +* Manage → Notifications
54 +* Manage → Notification Settings
55 +* Manage → Data Usage → History
56 +* Manage → Code mappings → All tabs
47 47  
48 -//__Avoid clicking on other components while deleting another__//
49 -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.
58 +== **Bug fixes ** ==
50 50  
51 -//__Improved validation feedback in migrating to the next-generation architecture__//
52 -We have improved the validation feedback when migrating to the next-generation architecture.
60 +//__Loading problems of Deployment plan execution overview__//
61 +We have fixed a problem that could cause issues when trying to show the deployment plan execution overview after pressing the Deploy button in Deploy -> Releases.
53 53  
54 -//__Make sure that user credentials can be viewed with view rights__//
55 -This release makes sure that the user credentials in Deploy can be considered with view rights and not only when having edit rights.
56 -
57 -//__Refresh behavior within the deployment plan is fixed__//
58 -This release changes the refresh behavior within the deployment plan to show, once more, the "to be installed" flows before the user presses Execute.
59 -
60 60  == **Fancy Forum Answers** ==
61 61  
62 62  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:
63 63  
64 -* [[Replacing Legacy eMagiz-Mendix Connector: Migration Plan>>https://my.emagiz.com/p/question/172825635703517317||target="blank"]]
65 -* [[Unknown character(s) does not create error message.>>https://my.emagiz.com/p/question/172825635703517488||target="blank"]]
66 -* [[Split gateway configuration for local GEN3 gateway>>https://my.emagiz.com/p/question/172825635703517580||target="blank"]]
67 +* [[Synchronous file pick-up>>https://my.emagiz.com/p/question/172825635703197660||target="blank"]]
68 +* [[Receiving e-mail via IMAP or POP3 - Set up>>https://my.emagiz.com/p/question/172825635703197881||target="blank"]]
69 +* [[Best way of Receiving and Sending Mail>>https://my.emagiz.com/p/question/172825635703210149||target="blank"]]
67 67  
68 68  == **Key takeaways** ==
69 69