Skip to Content

Changes for page 222 - Flee Frustration

Last modified by CarlijnKokkeler on 2024/06/05 09:31
From version 547.1
edited by CarlijnKokkeler
on 2024/06/03 15:57
Change comment: There is no comment for this version
To version 42.1
edited by Erik Bakker
on 2022/11/07 16:43
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -222 - Flee Frustration
1 +187 - Integration Sponsor
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.CarlijnKokkeler
1 +XWiki.ebakker
Content
... ... @@ -1,59 +1,74 @@
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, we have worked to allow cron trigggers for hours, days and months prepended by a 0. Moreover, changes in Design that will create or delete runtimes, or impact your model architecture, will trigger a warning before being put into effect in Design Architecture. We have also done several bug fixes, for example, users are not logged out from the portal anymore while deploying. Furthermore, users are now blocked from deploying at the same time on the same environment. Dive into our release blog to find out about the details and the rest of our bug fixes!
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.
7 7  
8 -== **Feedback Items** ==
9 -//__Cron triggers__//
10 -Cron triggers now allow for hours, days and months prepended by a 0, for example 05, which was not allowed before.
7 +== **Store - Next phase** ==
11 11  
12 -[[image:Main.Images.Release Blog.WebHome@release-222-cron-triggers.png]]
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.
13 13  
14 -//__Design changes__//
15 -If a user makes changes in Design that will create or delete runtimes, or impact your model architecture, that user will be warned about this before it is put into effect in Design Architecture.
11 +[[image:Main.Images.Release Blog.WebHome@187-release-blog--current-store-offering.png]]
16 16  
17 -[[image:Main.Images.Release Blog.WebHome@release-222-affect-design-architecture.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}}
18 18  
19 -== **Bug Fixes** ==
20 -//__Trigger activation__//
21 -Previously, when users were logged out from eMagiz during the execution of the deployment plan, it seemed that the portal reactived triggers, but this was not done. From now on, users are blocked from being logged out during deployment execution, so that triggers are re-enabled after the deployment plan has been executed.
15 +== **New eMagiz Mendix Connector** ==
22 22  
23 -//__Multiple users deploying__//
24 -Users are blocked from deploying at the same time on the same environment on the [[current runtime>>doc:Main.eMagiz Academy.Fundamentals.fundamental-runtime-generation3||target="blank"]] architecture.
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.
25 25  
26 -[[image:Main.Images.Release Blog.WebHome@release-222-users-deploying.png]]
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}}
27 27  
28 -//__Invalid memory configurations__//
29 -We have improved machine health calculations to prevent the creation of a machine with invalid memory configurations.
21 +== **Flow version restore** ~* ==
30 30  
31 -//__Property value synchronization__//
32 -Property values displayed in the Flow Designer and property values of your active release are now synchronized correctly.
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.
33 33  
34 -//__JMS number__//
35 -The number on the JMS container correctly displays the amount of queues present in Design.
25 +[[image:Main.Images.Release Blog.WebHome@187-release-blog--flow-version-restore.png]]
36 36  
37 -[[image:Main.Images.Release Blog.WebHome@release-222-jms.png]]
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}}
38 38  
33 +== **Feedback items ** ==
34 +
35 +We have also solved other feedback items besides the flow designer's critical updates.
36 +
37 +//__Improved help texts Kafka component__//
38 +TBA
39 +
40 +//__Improved warning message when Message redelivery cannot be properly executed__//
41 +TBA
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 +
39 39  == **Fancy Forum Answers** ==
40 40  
41 41  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:
42 42  
43 -* [[SunCertPathBuilderException using a Keystore>>https://my.emagiz.com/p/question/172825635703850115||target="blank"]]
44 -* [[Name of User in header>>https://my.emagiz.com/p/question/172825635703850290||target="blank"]]
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"]]
45 45  
46 -== **Key Takeaways** ==
60 +== **Key takeaways** ==
47 47  
48 -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:
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:
49 49  
50 50  * If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
51 51  * If you have feedback or ideas for us, talk to the Platypus
52 -* 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.
53 53  * Clear your browser cache (Ctrl + Shift + Del)
54 -* Check out the release notes [[here>>doc:Main.Release Information.Portal.222 - Flee Frustration.WebHome||target="blank"]]
68 +* Check out the release notes [here]
55 55  * Start thinking about how the license tracker can aid your development
56 56  * Start thinking about major, minor, and patch
71 +* Upgrade to the latest build number
57 57  * Keep making great integrations
58 58  
59 59  Let's stay in touch and till next time!
... ... @@ -61,11 +61,6 @@
61 61  {{info}}
62 62  ~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
63 63  
64 -{{/info}}
65 -)))
66 -
67 -(((
68 -{{toc/}}
69 -)))
79 +~*~* Indicates a GEN3-only feature.
80 +{{/info}})))((({{toc/}}))){{/container}}
70 70  {{/container}}
71 -{{/container}}