Changes for page 213 - Joyful Journeys
Last modified by Carlijn Kokkeler on 2024/04/18 13:07
From version 56.1
edited by Erik Bakker
on 2022/12/06 14:58
on 2022/12/06 14:58
Change comment:
There is no comment for this version
To version 338.1
edited by Carlijn Kokkeler
on 2024/01/15 14:34
on 2024/01/15 14:34
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 89-PrivateEye1 +212 - Failover Fiesta - Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki. ebakker1 +XWiki.CarlijnKokkeler - Content
-
... ... @@ -1,85 +1,41 @@ 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!** Our release of the Private store functionality characterizes this release.Thisfunctionality allows some users toexport content to a private store that is only accessible within the company and could be published to the public store of eMagiz.On top of that, we resolved some of the limitations on the 3rd generation runtime.Furthermore, some minor fixes and beta features will be released to the community.6 +**Hi there, eMagiz developers!** This release... 6 6 7 -== **Private Store** == 8 -On top of our general store, in which eMagiz currently publishes Store content relevant to both the Design and Create phases of eMagiz, we have added the private store functionality. This store works precisely the same as the general store. However, only users belonging to the same company as the exporter can import the store content (after it is approved). 8 +== **Feedback Items** == 9 9 10 -{{warning}}Other users can see the store content but are not able to import the store content. They will be notified to them when they try to do so.{{/warning}} 10 +//__Failover setup__// 11 +New components have been created to support a failover setup. More information can be found [[here>>https://docs.emagiz.com/bin/view/Main/Release%20Information/Runtime%20Images/V2.1.0/||target="blank"]]. 11 11 12 -== **3rd generation runtime bolstering** == 13 13 14 - Thisrelease will introduce various improvements for our 3rd generation runtime.Below youwill find the most noteworthy enhancements we made to the 3rdgenerationruntimeand itsinteraction with the portal.14 +== **Bug Fixes** == 15 15 16 -//__ SOAP and REST webservices migration includingsplitting them__//17 - Withthis release,we havereleased themigration processthatwillallowyouto migrateSOAPandRESTwebservicestothe3rdgenerationruntimeandsame timeyou can directly splittheall-entrytogetridof that construction alltogether.A specificmigrationpath forthis will bepublishedinthe documentationportal.16 +//__Message merging tool__// 17 +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. 18 18 19 -//__C hangingSSL settingsfor 3rdgenerationruntime modelsworks__//20 - As withthecurrentruntime architecture,youcannowalsochangetheSSLsettingsifneededfor amodelrunninginthe3rdgenerationruntime.19 +//__Catalog topic definitions__// 20 +It is now possible to generate a JSON Example of a topic whose schema has nested elements. Before, an error would occur when trying to generate a JSON example in this case. 21 21 22 -//__Improved migration for JMS flows__// 23 -This release will improve the migration of JMS flows when migrating to the 3rd generation runtime. 24 - 25 -{{warning}}If you already migrated your JMS flow you should execute a "Reset" action on JMS level to get these changes in your model{{/warning}} 26 - 27 -//__Removed the ability to add "Debug components" to a flow running in the 3rd generation runtime architecture__// 28 -As of this release, you cannot add debug components anymore on a flow that is already migrated to the 3rd generation runtime. This is because this functionality will not work in the 3rd generation runtime and would break your flow. 29 - 30 -//__Deployment plan is updated correctly when completly migrated to the 3rd generation runtime architecture__// 31 -We have fixed a bug that generated an incorrect default deployment plan once you were fully migrated to the 3rd generation runtime. 32 - 33 -== **Feedback items ** == 34 - 35 -We have also solved other feedback items besides the flow designer's critical updates. 36 - 37 -//__Improved naming convention on Store related pages__// 38 -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. 39 - 40 -//__Press "Enter" to search on multiple pages__// 41 -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. 42 - 43 -* Deploy → Deployment Plan 44 -* Deploy → Properties → History 45 -* Deploy → User Management → Roles 46 -* Manage → Error Messages → Error Messages 47 -* Manage → Error Messages → Flows with Error Messages 48 -* Manage → Error Messages → Exceptions of Error Messages 49 -* Manage → Log Entries 50 -* Manage → Alerts 51 -* Manage → Triggers 52 -* Manage → Tags – Cant find (only Gen2) 53 -* Manage → Notifications 54 -* Manage → Notification Settings 55 -* Manage → Data Usage → History 56 -* Manage → Code mappings → All tabs 57 - 58 -== **Bug fixes ** == 59 - 60 -//__Loading problems of Deployment plan execution overview__// 61 -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. 62 - 63 63 == **Fancy Forum Answers** == 64 64 65 65 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: 66 66 67 -* [[Synchronous file pick-up>>https://my.emagiz.com/p/question/172825635703197660||target="blank"]] 68 -* [[Receiving e-mail via IMAP or POP3 - Set up>>https://my.emagiz.com/p/question/172825635703197881||target="blank"]] 69 -* [[Best way of Receiving and Sending Mail>>https://my.emagiz.com/p/question/172825635703210149||target="blank"]] 26 +* [[Save header as class 'long'>>https://my.emagiz.com/p/question/172825635703683851||target="blank"]] 70 70 71 71 == **Key takeaways** == 72 72 73 -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:30 +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: 74 74 75 75 * If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]] 76 76 * If you have feedback or ideas for us, talk to the Platypus 77 -* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these. 34 +* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these. 78 78 * Clear your browser cache (Ctrl + Shift + Del) 79 79 * Check out the release notes [here] 80 80 * Start thinking about how the license tracker can aid your development 81 81 * Start thinking about major, minor, and patch 82 -* Upgrade to the latest build number 83 83 * Keep making great integrations 84 84 85 85 Let's stay in touch and till next time! ... ... @@ -87,6 +87,11 @@ 87 87 {{info}} 88 88 ~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]] 89 89 90 -~*~* Indicates a GEN3-only feature. 91 -{{/info}})))((({{toc/}}))){{/container}} 46 +{{/info}} 47 +))) 48 + 49 +((( 50 +{{toc/}} 51 +))) 92 92 {{/container}} 53 +{{/container}}