Skip to Content

Changes for page 213 - Joyful Journeys

Last modified by Carlijn Kokkeler on 2024/04/18 13:07
From version 42.1
edited by Erik Bakker
on 2022/11/07 16:43
Change comment: There is no comment for this version
To version 323.1
edited by Carlijn Kokkeler
on 2023/12/21 15:19
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -187 - Integration Sponsor
1 +211 - Log Luminary
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.ebakker
1 +XWiki.CarlijnKokkeler
Content
... ... @@ -1,69 +1,83 @@
1 1  {{container}}
2 -{{container layoutStyle="columns"}}(((
2 +{{container layoutStyle="columns"}}
3 +(((
3 3  [[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]]
4 4  
5 -**Hi there, eMagiz developers!** With this release we 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 that will enable you to restore your flow to a previous version.
6 +**Hi there, eMagiz developers!** In this release, we have done much work to improve our logging and overviews. This should improve the user experience for our platform. Next to this, we have done several minor changes and bug fixes, mainly relating to the Deploy and Manage phase.
6 6  
7 -== **Store - Next phase** ==
8 +== **Logging** ==
9 +//__Missing log entries__//
10 +We improved crash handling so that log messages clearly show when and why a container failed to start.
8 8  
9 -This release will introduce the next phase of the Store to our whole community. With this new functionality you can now import data model messages (i.e. CDM, API Gateway Data model or Event Streaming data model) and transformations. This way connecting to standardized systems such as Exact Online, Microsoft Graph, Salesforce and others will become even easier.
12 +//__Runtime logging__//
13 +We fixed a bug where no new log messages were showing up, even though they were produced by the container.
10 10  
11 -[[image:Main.Images.Release Blog.WebHome@187-release-blog--current-store-offering.png]]
15 +//__Deployment execution error message__//
16 +In some cases when a machine type step in the deployment plan execution errors, the portal may give an error when trying to display the error message. This has been fixed by now showing a generic error in the deployment plan and logging the full error in the Deploy history. The Deploy history will show a summary of the error and show the full error message in a new pop-up.
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}}
18 +== **Overviews** ==
14 14  
15 -== **New eMagiz Mendix Connector** ==
20 +//__Runtime overview__//
21 +We added a new overview in the Deploy phase, called 'Runtime Overview', which shows the information of all runtimes on running machines in an overview.
16 16  
17 -With this release we introduce a new version of the eMagiz Mendix Connector. This version (6.0.0) will work both with the current runtime architecture and the new runtime architecture making the migration from the current runtime architecture to the new runtime architecture easier. The new version of the eMagiz Mendix Connector can be found in the Mendix Marketplace and in the eMagiz portal.
23 +[[image:Main.Images.Release Blog.WebHome@release-blog-211-runtime-overview.png]]
18 18  
19 -{{info}}Migrating the runtime from the eMagiz portal works the same as for any other runtime. The migration path to migrate can be found [[here>>doc:Main.eMagiz Support.Migration Paths.migration-path-emagiz-runtime-generation-3.WebHome||target="blank"]]{{/info}}
25 +//__Missing properties overview__//
26 +The missing properties overview has been updated to show the runtimes and flow versions of missing property values.
20 20  
21 -== **Flow version restore** ~* ==
28 +[[image:Main.Images.Release Blog.WebHome@release-blog-211-missing-properties-overview.png]]
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.
30 +//__Runtime restart or redeploy overview__//
31 +Before executing the deployment plan to deploy machines, a pop-up will be shown with a list of the affected runtimes.
24 24  
25 -[[image:Main.Images.Release Blog.WebHome@187-release-blog--flow-version-restore.png]]
33 +[[image:Main.Images.Release Blog.WebHome@release-blog-211-restarted-redeployed-runtimes.jpg]]
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}}
35 +== **Feedback Items** ==
32 32  
33 -== **Feedback items ** ==
37 +//__Breaking changes pop-up__//
38 +Pending changes that have a high risk level are now shown in red bold in the pop up that appears after clicking 'Apply to environment'.
34 34  
35 -We have also solved other feedback items besides the flow designer's critical updates.
40 +[[image:Main.Images.Release Blog.WebHome@release-blog-211-breaking-changes.jpg]]
36 36  
37 -//__Improved help texts Kafka component__//
38 -TBA
42 +//__External recipients emailaddress__//
43 +The overview of external recipients has been updated. External recipients are created on a model level, instead of comma separated list. This means that you can add them to your environment directly, like internal users.
39 39  
40 -//__Improved warning message when Message redelivery cannot be properly executed__//
41 -TBA
45 +//__Broker queue metrics dashboards__//
46 +It is now possible to select the MQTT broker in the queue metrics dashboards.
42 42  
43 -//__See Flow Designer errors on the Create overview__//
44 -TBA
48 +//__Runtime image version__//
49 +The version of runtime images used to prepare your containers for deployments will be the same across all environments. This holds for releases that are deployed and promoted to a next environment.
45 45  
51 +
46 46  == **Bug Fixes** ==
47 47  
48 -//__Update Swagger File when changing order of entities in gateway message__//
49 -TBA
54 +//__Message throughput__//
55 +The message throughput graph in the Manage phase will now show the correct data, independent from the selected time internal. Before, this graph would not show any data in some cases.
50 50  
57 +//__Cloud template upgrade unjust rollback__//
58 +An issue has been fixed where a cloud template upgrade would be rolled back unjustly due to failed runtime checks.
59 +
60 +//__Next generation block__//
61 +Apply to environment will now be blocked when trying to deploy Gen3 runtimes on a Gen2 model.
62 +
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 -* [[Get files using a command via the SFTP protocol>>https://my.emagiz.com/p/question/172825635703184726||target="blank"]]
56 -* [[Take into account API rate limits>>https://my.emagiz.com/p/question/172825635703184597||target="blank"]]
57 -* [[Flow test stuck on initializing>>https://my.emagiz.com/p/question/172825635703184786||target="blank"]]
58 -* [[HTML to XML>>https://my.emagiz.com/p/question/172825635703197357||target="blank"]]
67 +* [[Deleting object failed for security reasons>>https://my.emagiz.com/p/question/172825635703671061||target="blank"]]
68 +* [[How do I delete a user?>>https://my.emagiz.com/p/question/172825635703670973||target="blank"]]
69 +* [[Import RCV-Shipment & RCV-Receipt XSD from Boltrics>>https://my.emagiz.com/p/question/172825635703671171||target="blank"]]
70 +* [[Add day in XPath header enricher>>https://my.emagiz.com/p/question/172825635703671325||target="blank"]]
71 +* [[Missing Body Java type resulting in problems>>https://my.emagiz.com/p/question/172825635703683790||target="blank"]]
59 59  
73 +
60 60  == **Key takeaways** ==
61 61  
62 -Thanks to all that helped build and those who tested and gave feedback to improve the product. To end this post, here are some key takeaways for you:
76 +Thanks to all who helped build and those who tested and gave feedback to improve the product. To end this post, here are some key takeaways for you:
63 63  
64 64  * If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
65 65  * If you have feedback or ideas for us, talk to the Platypus
66 -* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
80 +* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
67 67  * Clear your browser cache (Ctrl + Shift + Del)
68 68  * Check out the release notes [here]
69 69  * Start thinking about how the license tracker can aid your development
... ... @@ -76,6 +76,12 @@
76 76  {{info}}
77 77  ~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
78 78  
79 -~*~* Indicates a GEN3-only feature.
80 -{{/info}})))((({{toc/}}))){{/container}}
93 +~*~* Indicates a next-generation-architecture only feature.
94 +{{/info}}
95 +)))
96 +
97 +(((
98 +{{toc/}}
99 +)))
81 81  {{/container}}
101 +{{/container}}