Skip to Content

Changes for page 189 - Private Eye

Last modified by Carlijn Kokkeler on 2024/04/18 13:20
From version 45.1
edited by Erik Bakker
on 2022/11/21 12:00
Change comment: There is no comment for this version
To version 46.1
edited by Erik Bakker
on 2022/11/21 12:31
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -2,29 +2,31 @@
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 is characterized mainly by our efforts to bolster our 3rd generation runtime and all the interactions with it. Furthermore, some small bug fixes and beta features will be released to the community.
5 +**Hi there, eMagiz developers!** This release is characterized mainly by our efforts to bolster our 3rd generation runtime and all the interactions with it. Furthermore, some smalller fixes and beta features will be released to the community.
6 6  
7 -== **Store - Next phase** ==
7 +== **3rd generation runtime bolstering** ==
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.
9 +This release will introduce various improvements for our 3rd generation runtime. Below you will find the most noteworthy improvements we made to the 3rd generation runtime and the interaction with it.
10 10  
11 -[[image:Main.Images.Release Blog.WebHome@187-release-blog--current-store-offering.png]]
11 +//__Migration of JMS backup configuration improved__//
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}}
13 +//__Prechecks on Upgrade option made available for 3rd generation runtime__//
14 14  
15 -== **New eMagiz Mendix Connector** ==
15 +//__Autogenerated exits can be deployed at once__//
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.
17 +//__Code mapping functionality available on 3rd generation runtime__//
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}}
19 +//__Improved the performance of deploying or activating a release__//
20 20  
21 -== **Flow version restore** ~* ==
21 +//__Failing runtimes won't be restarted indefinetly anymore__//
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.
23 +== **Exportable Release Audit** ~* ==
24 24  
25 +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.
26 +
25 25  [[image:Main.Images.Release Blog.WebHome@187-release-blog--flow-version-restore.png]]
26 26  
27 -{{warning}}Note that the following restrictions apply when restoring to a previous version:
29 +{{warning}}Note that the following restrictions apply when exporting an audit document:
28 28   * Changes made on definition and transformation level are **not** restored
29 29   * You will **not** be able to restore to any flow version that was created before October 17th, 2022
30 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
... ... @@ -34,24 +34,30 @@
34 34  
35 35  We have also solved other feedback items besides the flow designer's critical updates.
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.
39 +//__Data Sink Refactor__//
40 +We have made some infrastructural changes to how data sink messages are stored and can be retrieved from the portal. Should there be changes needed on your end we will contact your seperately.
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.
42 +//__Improved naming convention on Store related pages__//
43 +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 -//__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.
45 +//__Press "Enter" to search on multiple pages__//
46 +In our Daemon Switch release we added functionality that allowed you to press **Enter** to search on the property overview page. With this release we have added this functionality to many more pages across the portal. The complete list is as follows
45 45  
46 -[[image:Main.Images.Release Blog.WebHome@187-release-blog--alert-visualized-in-create-overview.png]]
48 +* Deploy → Deployment Plan
49 +* Deploy → Properties → History
50 +* Deploy → User Management → Roles
51 +* Manage → Error Messages → Error Messages
52 +* Manage → Error Messages → Flows with Error Messages
53 +* Manage → Error Messages → Exceptions of Error Messages
54 +* Manage → Log Entries
55 +* Manage → Alerts
56 +* Manage → Triggers
57 +* Manage → Tags – Cant find (only Gen2)
58 +* Manage → Notifications
59 +* Manage → Notification Settings
60 +* Manage → Data Usage → History
61 +* Manage → Code mappings → All tabs
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}}
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: