Changes for page 213 - Joyful Journeys

Last modified by Carlijn Kokkeler on 2024/04/18 13:07

From version 359.1
edited by Carlijn Kokkeler
on 2024/01/29 14:34
Change comment: There is no comment for this version
To version 44.1
edited by Erik Bakker
on 2022/11/08 10:05
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -213 - Joyful Journeys
1 +187 - Integration Sponsor
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.CarlijnKokkeler
1 +XWiki.ebakker
Content
... ... @@ -1,89 +1,78 @@
1 1  {{container}}
2 -{{container layoutStyle="columns"}}
3 -(((
2 +{{container layoutStyle="columns"}}(((
4 4  [[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]]
5 5  
6 -**Hi there, eMagiz developers!** This release ....
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.
7 7  
7 +== **Store - Next phase** ==
8 8  
9 -== **Feedback Items** ==
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 10  
11 -//__Property releases__//
12 -When a new property release is created, this property release can now be viewed and deleted.
11 +[[image:Main.Images.Release Blog.WebHome@187-release-blog--current-store-offering.png]]
13 13  
14 -[[image:Main.Images.Release Blog.WebHome@release-blog-213-joyful-journeys-property-release.png]]
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}}
15 15  
16 -//__Runtime deletion__//
17 -When deleting a runtime, the error message that is displayed is more descriptive. The error messages will now include the names of the flows that run on the container.
15 +== **New eMagiz Mendix Connector** ==
18 18  
19 -//__Update flows__//
20 -In Create > Resources, a button "Update flows" has been added to update versions of all flows in which a resource is used.
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.
21 21  
22 -//__Input fields__//
23 -Multiple input fields have been updated such that they expand when the amount of characters exceeds the default size. These updates were done to cater to large expressions.
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}}
24 24  
25 -//__Memory settings__//
26 -It is now possible to change the memory settings of a container before pressing "Apply to environment". Before, it was only possible to view the memory settings if a container was running on AWS or running on a docker machine.
21 +== **Flow version restore** ~* ==
27 27  
28 -//__Runtime validation__//
29 -Validation for runtimes that are moved from on premises to the cloud or vice versa has been improved.
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 30  
31 -//__UI improvements__//
32 -UI improvements for static input components have been done and the tooltip for optional/required toggles has been improved.
25 +[[image:Main.Images.Release Blog.WebHome@187-release-blog--flow-version-restore.png]]
33 33  
34 -//__Q&A forum search__//
35 -The option to search by pressing the Enter key has been added to the Q&A forum.
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}}
36 36  
37 -//__Wiretap & debug error messages__//
38 -The error messages that may be displayed when using wiretaps and the debugger have been improved, these are now more user friendly.
33 +== **Feedback items ** ==
39 39  
40 -//__Runtime overview image versions__//
41 -Insight into invented and actual deployments has been improved. If the release version number on runtimes is different compared with the release, this is shown in the runtime overview.
35 +We have also solved other feedback items besides the flow designer's critical updates.
42 42  
43 -== **Bug Fixes** ==
44 -//__Action messages__//
45 -The formatting of action messages regarding changes in retention bytes/hours has been improved. The action message will now display the correct, actual behaviour.
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.
46 46  
47 -//__Removal of onramp__//
48 -We fixed an issue where it was not possible to remove the last onramp linked to a splitted entry (that was an all-entry before).
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.
49 49  
50 -//__Component changes reversion__//
51 -In the flow designer a bug could occur where the changes to a component would be reverted if the editing pop-up would be kept open for some minutes without having saved the changes yet. This has been fixed.
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.
52 52  
53 -//__State generation statistics__//
54 -The state generation graphs will now show the correct number of cache hits and misses.
46 +[[image:Main.Images.Release Blog.WebHome@187-release-blog--alert-visualized-in-create-overview.png]]
55 55  
56 -//__Runtime statistics details__//
57 -We fixed an issue where heap memory usage data was accumulating when zooming out in the runtime statistics details dashboards.
48 +{{info}}Note that you need to open flows that are currently triggering alerts to show the alert on the Create overview{{/info}}
58 58  
59 -//__Queue browser timestamps__//
60 -All timestamp formatting in the queue browser is now aligned to yyyy-MM-dd HH:mm:ss.SSS.
50 +== **Bug Fixes** ==
61 61  
62 -//__Deployment prechecks__//
63 -During deployments prechecks will be done on runtimes that still have to be deployed from deploy architecture.
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.
64 64  
65 -//__Addition and deletion of internal recipients__//
66 -Internal recipients are now added and deleted correctly. Before, an internal recipient could be added and thereafter deleted automatically when refreshing the page.
67 -
68 68  == **Fancy Forum Answers** ==
69 69  
70 70  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:
71 71  
72 -* [[What is the eMagiz control tower?>>https://my.emagiz.com/p/question/172825635703696612||target="blank"]]
73 -* [[Deleting connector without flows gives error>>https://my.emagiz.com/p/question/172825635703696657]]
74 -* [[How to use a flowtest with path properties>>https://my.emagiz.com/p/question/172825635703696835||target="blank"]]
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"]]
75 75  
76 -== **Key Takeaways** ==
64 +== **Key takeaways** ==
77 77  
78 -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:
66 +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:
79 79  
80 80  * If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
81 81  * If you have feedback or ideas for us, talk to the Platypus
82 -* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
70 +* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
83 83  * Clear your browser cache (Ctrl + Shift + Del)
84 84  * Check out the release notes [here]
85 85  * Start thinking about how the license tracker can aid your development
86 86  * Start thinking about major, minor, and patch
75 +* Upgrade to the latest build number
87 87  * Keep making great integrations
88 88  
89 89  Let's stay in touch and till next time!
... ... @@ -91,11 +91,6 @@
91 91  {{info}}
92 92  ~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
93 93  
94 -{{/info}}
95 -)))
96 -
97 -(((
98 -{{toc/}}
99 -)))
83 +~*~* Indicates a GEN3-only feature.
84 +{{/info}})))((({{toc/}}))){{/container}}
100 100  {{/container}}
101 -{{/container}}