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 120.1
edited by Erik Bakker
on 2023/06/05 15:01
on 2023/06/05 15:01
Change comment:
There is no comment for this version
Summary
-
Page properties (2 modified, 0 added, 0 removed)
Details
- Page properties
-
- Title
-
... ... @@ -1,1 +1,1 @@ 1 -1 89 -PrivateEye1 +199 - Home Improvements - Content
-
... ... @@ -2,71 +2,45 @@ 2 2 {{container layoutStyle="columns"}}((( 3 3 [[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]] 4 4 5 -**Hi there, eMagiz developers!** OurreleaseofthePrivatestorefunctionalitycharacterizesthis release. This functionality allowssomeuserstoxportcontenttoa privatestorethat isonlyaccessiblewithinthe company and couldbepublishedtothe publicstoreof eMagiz. On top of that,weresolvedsome ofthelimitations onthe3rdgenerationruntime.Furthermore,someminorfixesandbetafeatureswill bereleasedtothecommunity.5 +**Hi there, eMagiz developers!** In the last few weeks, we have worked hard on improving various aspects of our home. Among others we have improved the logging, alerting, and security of our next-generation architecture. On top of that we have improved the inner workings of the store and the certificate management for those of us using the Event Streaming pattern. 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). 7 +== **Next generation improvements and bug fixes** == 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}} 9 +//__Enhanced overview of the HTTP Statistics__// 10 +As of now all resources that have been called atleast once since deploying them will now show up in the left-bottom graph of the HTTP Statistics. This will make it easier to see whether a particular operation was called within a timeframe. On top of that it makes comparing data on various operations easier. In here you can also filter on one (by pressing the + icon) or more by clicking on the filter icon. In case you want to sort the table in a different manner you can click on the name of the column on which you want to sort. 11 11 12 -== **3rd generation runtime bolstering** == 12 +//__Reason why runtime cannot start is now in the vast majority of cases reported back__// 13 +In this release, we have improved the way we report failures during startup of runtimes. This will ensure that it becomes much easier to pinpoint what went wrong upon startup. 13 13 14 - This releasewillintroducevariousimprovementsforour3rdgeneration runtime.Belowyou will find themostnoteworthyenhancementswemadeto the3rd generationruntime and itsinteraction with theportal.15 +{{info}}Note that this fix is part of a new runtime image for the next-generation runtimes. The release notes of this can be found [[here>>doc:Main.Release Information.Runtime Images.WebHome||target="blank"]]{{/info}} 15 15 16 -//__ SOAP and REST web servicesmigrationincluding splitting them__//17 - Withthisrelease,wehave releasedthe migration processthat willallowyoutomigrateSOAP andRESTwebservicestothe 3rd generationruntime and at the same time youcandirectly splittheall-entrytoget rid of that constructionalltogether.A specific migrationpathfor this will be published in the documentation portal.17 +//__Forced congestion control__// 18 +To reduce the number of repeating mails within a 10 minute window we have now forced congestion control on all alerts generated via the platform. 18 18 19 -//__ Changing SSLsettingsfor3rd generationruntimemodelsworks__//20 - Aswiththe currentruntimearchitecture,youcannow alsochange the SSLsettingsifneededfora modelrunninginthe3rdgenerationruntime.20 +//__Unused images are cleaned up__// 21 +This release improves the way in which images are kept. To avoid a lot of old and unused images on our systems and our systems we now (on default) cleanup old images that are not used anymore. Should you wish to keep the images and manually remove them on your own server you can deactivate this behavior per "Deploy machine" step in your deployment plan. 21 21 22 -//__Improved migrationforJMSflows__//23 -T hisrelease will improve themigrationofJMSflows when migrating to the3rdgeneration runtime.23 +//__Improved rollup and storage of metrics when running an event streaming solution__// 24 +To improve the stability of the Manage phase and, in particular, the metrics when zooming out on the provided information, we have made some structural changes that support this user functionality better. 24 24 25 -{{warning}} Ifyou alreadymigratedyourJMSflowyou should execute a"Reset"action onJMSleveltoget thesechanges inyourmodel{{/warning}}26 +{{warning}} Due to this change, the platform will remove data collected before the release date in the upcoming weeks. This process will be finished at the beginning of July. From then on, all data before the 9th of June will no longer be visible. As users generally do not look back this far back in time, we consider this an acceptable trade-off. {{/warning}} 26 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. 28 +== **Store Improvements** == 29 29 30 -//__ Deploymentplanis updated correctly whencompletly migratedtothe 3rdgenerationruntimearchitecture__//31 - Wehavefixed abugthatgenerated an incorrectdefault deploymentplanonce youwere fully migrated to the3rd generation runtime.30 +//__Improved importing behavior for specific use cases__// 31 +Before, it could happen that a certain placeholder that contained an asterisk (*) were imported incorrectly. This has now been fixed to ensure that the correct import behavior is experienced by our users. 32 32 33 -== ** Feedbackitems** ==33 +== **Event Streaming - Certificate Management** == 34 34 35 -We have also solved other feedback items besides the flow designer's critical updates. 35 +//__Expired certification notification__// 36 +As of now we have functionality in place that will inform you (and us) when a client certificate of an Event Streaming user is going to expire within the upcoming three months. This way you can take action early on and report back that the update was succesfull so we can revoke the expiring client certificate accordingly. If you want specific information on this please reach out to us at [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]. 36 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"]] 42 +* [[How to determine the system definition for this sample message in JSON?>>https://my.emagiz.com/p/question/172825635703440852||target="blank"]] 43 +* [[Instability in JMS connection>>https://my.emagiz.com/p/question/172825635703440717||target="blank"]] 70 70 71 71 == **Key takeaways** == 72 72