Changes for page 213 - Joyful Journeys
Last modified by Carlijn Kokkeler on 2024/04/18 13:07
From version 57.1
edited by Erik Bakker
on 2022/12/06 15:57
on 2022/12/06 15:57
Change comment:
There is no comment for this version
To version 123.1
edited by Erik Bakker
on 2023/06/08 08:11
on 2023/06/08 08:11
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,73 +2,43 @@ 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 servicesmigration,including splitting them__//17 - Withthisrelease,wehave releasedthe migration processthat willallowyoutomigrateSOAP andRESTwebservicestothe 3rd generationruntime. At the same time, youcandirectly splittheall-entrytoeliminatethatconstruction. A specificmigrationpathfor 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,you canchange 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 migration for JMS flows__// 23 -This release will improve the migration of JMS flows when migrating to the 3rd generation runtime. 23 +== **Store Improvements** == 24 24 25 -{{warning}}If you already migrated your JMS flow, you should execute a "Reset" action on the JMS level to get these changes in your model{{/warning}} 25 +//__Improved importing behavior for specific use cases__// 26 +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. 26 26 27 -//__ Removedthe abilitytoadd"Debugcomponents"toa flowrunninginthe3rdgenerationruntimerchitecture__//28 - As ofthisrelease,youcan no longeradddebug componentsonaflow alreadymigratedtothe 3rd generationruntime. This functionality will not work inthe3rdgenerationruntimendwouldbreakyourflow.28 +//__Fixed bug in creating a message mapping on top of an imported system message__// 29 +It is now possbile to create a message mapping to an imported system message from the store. 29 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. 31 +== **Event Streaming - Certificate Management** == 32 32 33 -//__ Correctpropertygenerationfor Event Streaming flows using the 3rd generationruntime architecture__//34 - With thisrelease,thepropertiesgeneratedforEvent Streamingflowsunning in the3rdgeneration runtime are configuredcorrectlytomimic theonesin theimage.33 +//__Expired certification notification__// 34 +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]]. 35 35 36 -//__Added "Reset" functionality__// 37 -With this release, a new functionality has been added for 3rd generation runtimes that allows you to combine several steps into one action, called "Reset runtime." The effect of this action is the same as it currently is in the legacy runtime. 38 - 39 -== **Feedback items ** == 40 - 41 -We have also solved other feedback items besides the flow designer's critical updates. 42 - 43 -//__Improved naming convention on Store related pages__// 44 -We have improved various display names using the merge functionality within our store offering. 45 - 46 -//__Update security protocols for our internal architecture__// 47 -Parts of our internal infrastructure (i.e., docs.emagiz.com) have been updated to adhere to the latest security standards. 48 - 49 -//__Improved read-only description for "if exists" constructions in Transformations__// 50 -To make it clear what the "if exists" check does while not being in "Start Editing" mode, we have improved the description so users without edit rights or without wanting to enter the "Start Editing" mode can read and interpret what the check does. 51 - 52 - 53 -== **Bug fixes ** == 54 - 55 -//__Decent validation feedback when not filling in the property value__// 56 -We have fixed the validation feedback you get when not filling in the property value using the "Check properties" functionality. 57 - 58 -//__Incorrect resource locations__// 59 -We have fixed several instances where the resource location was not generated correctly in the 3rd generation runtime. 60 - 61 -//__Apply to environment in User Management performance improvement__// 62 -We have improved the performance of updating User Management on your environment. This way, the update functionality is more stable and faster. 63 - 64 64 == **Fancy Forum Answers** == 65 65 66 66 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: 67 67 68 -* [[Is eMagiz able to read XSD attributes>>https://my.emagiz.com/p/question/172825635703236146||target="blank"]] 69 -* [[Does eMagiz use ActiveMQ?>>https://my.emagiz.com/p/question/172825635703235780||target="blank"]] 70 -* [[Tool for test messages to eMagiz Queues>>https://my.emagiz.com/p/question/172825635703236227||target="blank"]] 71 -* [[How to Remove Cloud Container>>https://my.emagiz.com/p/question/172825635703236460||target="blank"]] 40 +* [[OpenAPI import for API Gateway system response throws error>>https://my.emagiz.com/p/question/172825635703466150||target="blank"]] 41 +* [[Api GW won't boot after adding integration>>https://my.emagiz.com/p/question/172825635703479151||target="blank"]] 72 72 73 73 == **Key takeaways** == 74 74