Changes for page 213 - Joyful Journeys
Last modified by Carlijn Kokkeler on 2024/04/18 13:07
From version 55.1
edited by Erik Bakker
on 2022/11/24 11:53
on 2022/11/24 11:53
Change comment:
There is no comment for this version
To version 345.1
edited by Carlijn Kokkeler
on 2024/01/16 16:53
on 2024/01/16 16:53
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 -1 88-CloseEncounters1 +212 - Failover Fiesta - Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki. ebakker1 +XWiki.CarlijnKokkeler - Content
-
... ... @@ -1,90 +1,50 @@ 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!** This release is characterizedmainlybyoureffortstobolsterour 3rd generation runtime andall itsinteractions.Furthermore, someminorfixesandbetafeatures willbereleasedtothecommunity.6 +**Hi there, eMagiz developers!** This release contains single and double lane cloud template updates, both non-service affecting. Moreover, work has been done to better support a failover setup. Lastly, some bug fixes were done regarding the message merging tool and catalog topic defintions. 6 6 7 -== ** 3rdgeneration runtimebolstering** ==8 +== **Cloud Template R20 - Double Lane** == 8 8 9 -This release will introducevariousimprovementsfor our3rd generationruntime.Belowyouwillfind theost noteworthyenhancements wemade to the3rdgenerationruntimeand itsinteractionwiththeportal.10 +This release introduces a new non-service affecting cloud template for all our customers running in a double-lane setup. This cloud template introduces improved auto-healing. The complete release notes on the cloud template can be found [[here>>doc:Main.Release Information.Cloud Templates.R20 - Double lane.WebHome||target="blank"]]. 10 10 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. 12 +== **Cloud Template R27 - Single Lane** == 13 13 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. 14 +This release introduces a new non-service affecting cloud template for all our customers running in a single-lane setup on the next generation architecture. This cloud template introduces improved auto-healing. The complete release notes on the cloud template can be found [[here>>doc:Main.Release Information.Cloud Templates.R27 - Single lane.WebHome||target="blank"]]. 16 16 17 -//__Autogenerated exits can be deployed at once__// 18 -This release has fixed a bug that prevented you from deploying an exit flow correctly. 16 +== **Feedback Items** == 19 19 20 -//__ Code mapping functionality availableon 3rdgeneration runtime__//21 - Asofthisrelease,codemappingfunctionalityis alsoavailable forthe3rd generationruntime.This removes the restrictiononmigratingtotheew3rd generationruntime for our clientsthatusethecodemapping functionality.18 +//__Failover setup__// 19 +New components have been created to support a failover setup. Moreover, two new deployment step types are introduced to incorporate failover actions during deployment. More information can be found [[here>>https://docs.emagiz.com/bin/view/Main/Release%20Information/Runtime%20Images/V2.1.0/||target="blank"]]. 22 22 23 -//__Failing runtimes won't be restarted indefinitely anymore__// 24 -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. 21 +== **Bug Fixes** == 25 25 26 -== **Exportable Release Audit** ~* == 23 +//__Message merging tool__// 24 +The message merging tool has been fixed to allow merging a store item message model into your own message models. In some rare cases your CDM message may be broken due to incorrect data. In those cases, the message mapping and message merge functionalities will be broken as well. If this broken data is detected when navigating to CDM-message-related pages, you will be able to clean your CDM message. 27 27 28 -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. 26 +//__Catalog topic definitions__// 27 +Before, an error would occur in the Catalog page when generating an example JSON message of a topic definition that has nested elements. This issue is now fixed and generating a sample JSON message for such topic definition is possible. 29 29 30 -[[image:Main.Images.Release Blog.WebHome@188-release-blog--exportable-release-audit.png]] 31 - 32 -{{warning}}Note that the following restrictions apply when exporting an audit document: 33 - * Works **only** for releases that are promoted and made active on **Production** 34 - * You will **only** see changes made during the **current** calendar year 35 - * On the first of April all objects of the **last** calendar year will be **removed**. 36 - ** As a consequence you cannot download this information anymore **after** the first of April{{/warning}} 37 - 38 -== **Feedback items ** == 39 - 40 -We have also solved other feedback items besides the flow designer's critical updates. 41 - 42 -//__Improved naming convention on Store related pages__// 43 -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. 44 - 45 -//__Press "Enter" to search on multiple pages__// 46 -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. 47 - 48 -* Deploy → Deployment Plan 49 -* Deploy → Properties → History 50 -* Deploy → User Management → Roles 51 -* Manage → Error Messages → Error Messages 52 -* Manage → Error Messages → Flows with Error Messages 53 -* Manage → Error Messages → Exceptions of Error Messages 54 -* Manage → Log Entries 55 -* Manage → Alerts 56 -* Manage → Triggers 57 -* Manage → Tags – Cant find (only Gen2) 58 -* Manage → Notifications 59 -* Manage → Notification Settings 60 -* Manage → Data Usage → History 61 -* Manage → Code mappings → All tabs 62 - 63 -== **Bug fixes ** == 64 - 65 -//__Loading problems of Deployment plan execution overview__// 66 -We have fixed a problem that could cause issues when trying to show the deployment plan execution overview after pressing the Deploy button in Deploy -> Releases. 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 -* [[ Synchronousfilepick-up>>https://my.emagiz.com/p/question/172825635703197660||target="blank"]]73 -* [[ Receiving e-mailviaIMAPorPOP3 - Setup>>https://my.emagiz.com/p/question/172825635703197881||target="blank"]]74 -* [[ BestwayofReceivingandSendingMail>>https://my.emagiz.com/p/question/172825635703210149||target="blank"]]33 +* [[What is the eMagiz control tower?>>https://my.emagiz.com/p/question/172825635703696612||target="blank"]] 34 +* [[Deleting connector without flows gives error>>https://my.emagiz.com/p/question/172825635703696657]] 35 +* [[How to use a flowtest with path properties>>https://my.emagiz.com/p/question/172825635703696835||target="blank"]] 75 75 76 76 == **Key takeaways** == 77 77 78 -Thanks to all thathelped build and those who tested and gave feedback to improve the product. To end this post, here are some key takeaways for you:39 +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: 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. 43 +* 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 87 -* Upgrade to the latest build number 88 88 * Keep making great integrations 89 89 90 90 Let's stay in touch and till next time! ... ... @@ -92,6 +92,11 @@ 92 92 {{info}} 93 93 ~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]] 94 94 95 -~*~* Indicates a GEN3-only feature. 96 -{{/info}})))((({{toc/}}))){{/container}} 55 +{{/info}} 56 +))) 57 + 58 +((( 59 +{{toc/}} 60 +))) 97 97 {{/container}} 62 +{{/container}}