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 285.1
edited by Carlijn Kokkeler
on 2023/12/04 15:23
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -187 - Integration Sponsor
1 +210 - Deployment Delights
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.ebakker
1 +XWiki.CarlijnKokkeler
Content
... ... @@ -1,69 +1,69 @@
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!** We have have done much work for the Deploy phase. Moreover, we did several bug fixes, mainly relating to the Deploy phase again, but also several for the Store. Lastly, we made some changes to the alerts that you may be receiving.
6 6  
7 -== **Store - Next phase** ==
8 +== **Alerts** ==
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.
10 +//__Topic approaching max size alert__//
11 +The alert ‘topic approaching maximum size’ alert has been temporarily disabled due to a high number of false positives.
10 10  
11 -[[image:Main.Images.Release Blog.WebHome@187-release-blog--current-store-offering.png]]
13 +//__Missing metrics alert__//
14 +We solved an issue where the ‘missing metrics’ alert did not always contain the full container name.
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 +== **Feedback Items** ==
14 14  
15 -== **New eMagiz Mendix Connector** ==
18 +//__Container version overview__//
19 +In Deploy > Releases, it is now possible to see the container versions in the release details. This can be viewed by clicking the three dots in the Create phase section.
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.
21 +[[image:Main.Images.Release Blog.WebHome@release-blog-210-deployment-delights-container-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}}
23 +//__Unchanged containers__//
24 +When deploying a new release, containers that have no changes between the deployed release and the new release will not be deployed and restarted.
20 20  
21 -== **Flow version restore** ~* ==
26 +//__Rebuilding of images__//
27 +Changing the list of flows that should run on a container will now trigger the rebuilding of images.
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.
29 +== **Bug Fixes** ==
24 24  
25 -[[image:Main.Images.Release Blog.WebHome@187-release-blog--flow-version-restore.png]]
31 +//__Runtime metrics processing__//
32 +The collection and publishing of runtime metrics is no longer synchronized across containers, which improves their processing.
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}}
34 +//__Deployment plan__//
35 +We solved a bug where a deployment step in the deployment plan could randomly get stuck.
32 32  
33 -== **Feedback items ** ==
37 +//__Store message merging__//
38 +The message merging tool has been fixed to allow merging of your message definitions from the Store to existing data model messages.
34 34  
35 -We have also solved other feedback items besides the flow designer's critical updates.
40 +//__View all store items__//
41 +An issue has been fixed where it was not possible to load more store items in the left panel in the Create phase Flow Designer.
36 36  
37 -//__Improved help texts Kafka component__//
38 -TBA
43 +//__Out of memory behavior__//
44 +We improved the out of memory behavior of runtimes. Runtimes will now always restart when an out of memory error occurs.
39 39  
40 -//__Improved warning message when Message redelivery cannot be properly executed__//
41 -TBA
46 +//__Max fetch size__//
47 +We improved the help text of the advanced option of ‘max fetch size’ for the mail inbound adapter to better describe how that option affects its behavior.
42 42  
43 -//__See Flow Designer errors on the Create overview__//
44 -TBA
45 -
46 -== **Bug Fixes** ==
47 -
48 -//__Update Swagger File when changing order of entities in gateway message__//
49 -TBA
50 -
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"]]
53 +* [[Deleting object failed for security reasons>>https://my.emagiz.com/p/question/172825635703671061||target="blank"]]
54 +* [[How do I delete a user?>>https://my.emagiz.com/p/question/172825635703670973||target="blank"]]
55 +* [[Import RCV-Shipment & RCV-Receipt XSD from Boltrics>>https://my.emagiz.com/p/question/172825635703671171||target="blank"]]
56 +* [[Add day in XPath header enricher>>https://my.emagiz.com/p/question/172825635703671325||target="blank"]]
57 +* [[Missing Body Java type resulting in problems>>https://my.emagiz.com/p/question/172825635703683790||target="blank"]]
59 59  
59 +
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:
62 +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.
66 +* 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}}
79 +~*~* Indicates a next-generation-architecture only feature.
80 +{{/info}}
81 +)))
82 +
83 +(((
84 +{{toc/}}
85 +)))
81 81  {{/container}}
87 +{{/container}}