Changes for page 222 - Flee Frustration
Last modified by CarlijnKokkeler on 2024/06/05 09:31
From version 486.1
edited by CarlijnKokkeler
on 2024/04/23 15:19
on 2024/04/23 15:19
Change comment:
There is no comment for this version
To version 53.1
edited by Erik Bakker
on 2022/11/21 13:48
on 2022/11/21 13:48
Change comment:
There is no comment for this version
Summary
-
Page properties (3 modified, 0 added, 0 removed)
Details
- Page properties
-
- Title
-
... ... @@ -1,1 +1,1 @@ 1 - 219- CreationCarousel1 +188 - Close Encounters - Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki. CarlijnKokkeler1 +XWiki.ebakker - Content
-
... ... @@ -1,73 +1,88 @@ 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 ,wehaveanew versionofour eMagiz Mendix connectoravailable,that will supportMendixversion10 and higher. Furthermore,the pathlengthin OpenAPI spec importshas beenincreasedto a maximumof300 characters. Lastly,we have done manybugfixes,oneofwhich willensurethat SFTPsessionswill beclosedagain after completion.Forthis fix, a new[[runtime image>>doc:Main.Release Information.Runtime Images.V304.WebHome||target="blank"]] has been published.5 +**Hi there, eMagiz developers!** This release is characterized mainly by our efforts to bolster our 3rd generation runtime and all its interactions. Furthermore, some minor fixes and beta features will be released to the community. 7 7 8 -== ** FeedbackItems** ==7 +== **3rd generation runtime bolstering** == 9 9 10 -//__eMagiz Mendix connector__// 11 -We released a new version of our eMagiz Mendix connector that will support Mendix version 10 and higher. 9 +This release will introduce various improvements for our 3rd generation runtime. Below you will find the most noteworthy enhancements we made to the 3rd generation runtime and its interaction with the portal. 12 12 13 -//__ ImprovedOpenAPIimport__//14 - Thepath length inOpenAPIspec importshas beenincreasedtoamaximumof300characters.11 +//__Migration of JMS backup configuration improved__// 12 +With this release, the configuration of the JMS backup configuration is improved to prevent potential connectivity issues after migrating to the 3rd generation runtime. 15 15 16 -//__ Flowteststacktrace__//17 - Ifa flow testcreatesa log linewith level‘Warning’or‘Error’andthereisastacktracecreated, thenwe showthe stacktraceinsidethelogmessageona separatetab.14 +//__Prechecks on Upgrade option made available for 3rd generation runtime__// 15 +As with the current runtime architecture, you can now also execute the prechecks before automatically upgrading to the latest cloud template on the 3rd generation runtime architecture. 18 18 19 -[[image:Main.Images.Release Blog.WebHome@release-219-creation-carousel-stack-trace.png]] 17 +//__Autogenerated exits can be deployed at once__// 18 +This release has fixed a bug that prevented you from deploying an exit flow correctly. 20 20 21 -{{info}}With the release of Spring 6 in our previous release, some users reported that their filters have begun logging warnings about discarding messages even though the filter is configured to not throw an exception on rejection. For flows that process high numbers of messages (and potentially discard a lot of messages as well) this can significantly disturb the overview of the logs in the manage phase. 20 +//__Code mapping functionality available on 3rd generation runtime__// 21 +As of this release, code mapping functionality is also available for the 3rd generation runtime. This removes the restriction on migrating to the new 3rd generation runtime for our clients that use the code mapping functionality. 22 22 23 -To mitigate this, you can change the filter that throws the warning so it specifically refers to a discard channel. Given the chosen configuration, we advice to use the nullChannel option. This will silently drop the message without registering a warning in the log. In case you find the warning in the log a nice addition, we suggest to add an explicit discard channel leading to a logging outbound channel adapter. This log component can then be configured to throw a warning. 23 +//__Improved the performance when activating a release__// 24 +With this release, the performance of activating a release has improved considerably. This means less waiting time when activating a release. 24 24 25 -In the next release, we will aid you by adding a validation check that will force you to select a discard channel when it is currently not selected once you edit the flow to create a new version. More on this in the next release blog. {{/info}} 26 +//__Failing runtimes won't be restarted indefinitely anymore__// 27 +We have put a cap on this behavior to prevent your logs from exploding due to a failing runtime being restarted indefinitely. As of this release, five attempts will be made to restart a failing runtime. If the runtime can not start correctly after these attempts, the runtime will be stopped. 26 26 29 +== **Exportable Release Audit** ~* == 27 27 28 -== **Bug Fixes** == 29 -//__Error handling__// 30 -When migrating to the current generation architecture, the default error handling will now also be migrated correctly, so that no manual changes have to be done for this. 31 +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. 31 31 32 -//__Volume mapping passwords__// 33 -Passwords for network volumes are hidden on the machine after deployment. 33 +[[image:Main.Images.Release Blog.WebHome@188-release-blog--exportable-release-audit.png]] 34 34 35 -//__Create integration removal__// 36 -When removing an integration from Create, the Create phase is now correctly updated. 35 +{{warning}}Note that the following restrictions apply when exporting an audit document: 36 + * Works **only** for releases that are promoted and made active on **Production** 37 + * You will **only** see changes made during the **current** calendar year 38 + * On the first of April all objects of the **last** calendar year will be **removed**. 39 + ** As a consequence you cannot download this information anymore **after** the first of April{{/warning}} 37 37 38 -//__Legacy statistics__// 39 -Legacy pages are now correctly hidden when running on the current runtime architecture. 41 +== **Feedback items ** == 40 40 41 -//__Unused properties__// 42 -Users are not able to edit or delete eMagiz properties, so now they will also not be shown in the 'Unused property overview' anymore. 43 +We have also solved other feedback items besides the flow designer's critical updates. 43 43 44 -//__ Enumerationvalues__//45 - Enumerationvaluesforeventprocessorscan nowbeedited inCreate.45 +//__Improved naming convention on Store related pages__// 46 +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. 46 46 47 -[[image:Main.Images.Release Blog.WebHome@release-219-creation-carousel-event-processor.png]] 48 +//__Press "Enter" to search on multiple pages__// 49 +In our Daemon Switch release, we added functionality that allowed you to press **Enter** to search on the property overview page. This release has added this functionality to many more pages across the portal. The complete list is as follows. 48 48 49 -//__SFTP sessions__// 50 -SFTP session factories did not close their connection after it was complete. This could cause connection starvation on the SFTP server, and was especially noticable when using the SFTP Session Factory without caching, as that factory opens a new connection for every call. For this, a new [[runtime image>>doc:Main.Release Information.Runtime Images.V304.WebHome||target="blank"]] has been released. 51 +* Deploy → Deployment Plan 52 +* Deploy → Properties → History 53 +* Deploy → User Management → Roles 54 +* Manage → Error Messages → Error Messages 55 +* Manage → Error Messages → Flows with Error Messages 56 +* Manage → Error Messages → Exceptions of Error Messages 57 +* Manage → Log Entries 58 +* Manage → Alerts 59 +* Manage → Triggers 60 +* Manage → Tags – Cant find (only Gen2) 61 +* Manage → Notifications 62 +* Manage → Notification Settings 63 +* Manage → Data Usage → History 64 +* Manage → Code mappings → All tabs 51 51 52 52 == **Fancy Forum Answers** == 53 53 54 54 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: 55 55 56 -* [[ Create anoverviewof DataFlowswithoutany datatraffic>>https://my.emagiz.com/p/question/172825635703811872||target="blank"]]57 -* [[ Flowtestdoesnotwork>>https://my.emagiz.com/p/question/172825635703811773||target="blank"]]58 -* [[ Debuggerblocksallothertraffic>>https://my.emagiz.com/p/question/172825635703812013||target="blank"]]70 +* [[Synchronous file pick-up>>https://my.emagiz.com/p/question/172825635703197660||target="blank"]] 71 +* [[Receiving e-mail via IMAP or POP3 - Set up>>https://my.emagiz.com/p/question/172825635703197881||target="blank"]] 72 +* [[Best way of Receiving and Sending Mail>>https://my.emagiz.com/p/question/172825635703210149||target="blank"]] 59 59 60 -== **Key Takeaways** ==74 +== **Key takeaways** == 61 61 62 -Thanks to all whohelped 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 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: 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 -* Check out the release notes [ [here>>doc:Main.Release Information.Portal.219 - Creation Carousel.WebHome||target="blank"]]82 +* Check out the release notes [here] 69 69 * Start thinking about how the license tracker can aid your development 70 70 * Start thinking about major, minor, and patch 85 +* Upgrade to the latest build number 71 71 * Keep making great integrations 72 72 73 73 Let's stay in touch and till next time! ... ... @@ -75,11 +75,6 @@ 75 75 {{info}} 76 76 ~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]] 77 77 78 -{{/info}} 79 -))) 80 - 81 -((( 82 -{{toc/}} 83 -))) 93 +~*~* Indicates a GEN3-only feature. 94 +{{/info}})))((({{toc/}}))){{/container}} 84 84 {{/container}} 85 -{{/container}}