Changes for page 222 - Flee Frustration
Last modified by CarlijnKokkeler on 2024/06/05 09:31
From version 94.1
edited by Erik Bakker
on 2023/03/17 08:35
on 2023/03/17 08:35
Change comment:
There is no comment for this version
To version 500.1
edited by CarlijnKokkeler
on 2024/05/06 13:06
on 2024/05/06 13:06
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 - 194-GiantLeap1 +220 - Patch Parade - Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki. ebakker1 +XWiki.CarlijnKokkeler - Content
-
... ... @@ -1,82 +1,68 @@ 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!** In the last few weeks, we have worked around the clock to release various improvement points within the 3rd generation runtime and elsewhere. We have improved the feedback provided when a flow can't start due to an incorrect transformation, improved when specific logging is triggered, and improved the stability of our internal infrastructure. On top of that, we fixed several bugs surrounding other parts of the platform. So without further ado, let us look at all these improvements.6 +**Hi there, eMagiz developers!** 6 6 7 -== ** 3rd generationimprovements** ==8 +== **Feedback Items** == 8 8 9 -//__ Betterfeedbackin theerror log whena corruptstylesheetis encountered__//10 - We have improvedthelogging within a 3rd generation runtime thatidentifiesthebroken resourceby namewithinacontainerand informsyou tonavigate toCreate-> Resourcestoseein which flowstheresourceis usedso youcantaketheappropriateaction.10 +//__Integration pattern information__// 11 +Integration pattern information of the selected message type has been added to the pop-up that is shown in Capture when creating a new integration. 11 11 12 -//__Better internal error handling to avoid unnecessary alerting and notifications__// 13 -We have improved the internal error handling when sending metrics from the runtime to our monitoring stack. This will gravely reduce the alerts you receive on this topic when your model runs on the 3rd generation monitoring stack. 13 +[[image:Main.Images.Release Blog.WebHome@release-220-integration-pattern.png]] 14 14 15 -//__ ImprovedManageDashboard__//16 - This releaseimproveswhatyoucanseeintheManageDashboardafteryoumigrateyourmodeltothe3rdgenerationruntime architecture.15 +//__Message queue history__// 16 +All events that relate to message queues (delete message, delete all messages or delete queue) are logged in the Manage phase instead of the Deploy phase. 17 17 18 -//__Improved process surrounding "slot standby" and "slot wakeup" for 3rd generation runtimes__// 19 -When a slot is put into standby mode, we also stop all on-premise runtimes to avoid excessive logging (and alerting) on your models with this functionality. The opposite happens when the slot wakeup is triggered. As a result, not only the cloud runtimes are started but also all on-premise runtimes. 18 +[[image:Main.Images.Release Blog.WebHome@release-220-manage-history.png]] 20 20 21 -//__ Improved processof deploy preparation__//22 - With this release, wehaveimprovedthe process through which your deploymentaction ispreparedby eMagiz. As aresult,the chancesofunexpected behavior occurringinyourmodelare drastically reduced.20 +//__Search boxes__// 21 +Search boxes in the properties overview are now shown by default. 23 23 24 -//__Improved migration of Streaming container__// 25 -When migrating your streaming container, we now consider whether "custom error handling" is used within one of the event processors. Based on that determination, additional components are added to ensure that the streaming container will work after migrating without manual intervention. 23 +[[image:Main.Images.Release Blog.WebHome@release-220-search-boxes.png]] 26 26 27 -//__ Add Historyto Notificationsin Manage__//28 - Toimprovethe auditabilityofour platform, we haveintroduced an audit trailtotheNotificationsectionin Manage for modelsrunning on our 3rd generation monitoring stack. Thisway,it isalways visible whenthenotificationswere pausedand whopausedor unpausedthenotifications.25 +//__Set as mapped__// 26 +It is now possible to choose whether to set/unset all attributes of an entity as mapped in design. 29 29 30 -//__Improved Manage phase for Event Streaming__// 31 -Based on the feedback on our first iteration of the Manage phase for Event Streaming, we have improved the graphs and the calculations that fill the graphs with values. On top of that, we have added help texts to clarify what each chart our table displays to you. 28 +[[image:Main.Images.Release Blog.WebHome@release-220-mapped-entity.png]] 32 32 33 -//__ Improvedhelptextfornetwork volumes__//34 - Withthisrelease,wehaveimprovedthehelptext that explainsnetworkvolumesandhowtouse themwithinoursolution.30 +//__SSL settings__// 31 +Changes can now be deployed on SSL level without creating a new version of a flow in Create. 35 35 36 -{{warning}}Should you be interested in migrating your model to our new 3rd generation architecture, don't hesitate to contact us at [[productmanagement@emagiz.com>>mailto:productmanagement@emagiz.com]] or read our [[documentation>>doc:Main.eMagiz Academy.Fundamentals.fundamental-runtime-generation3||target="blank"]] on the subject.{{/warning}} 33 +== **Bug Fixes** == 34 +//__Annotation styling__// 35 +It is now possible to use enters in Annotations, so that multiple line spaces can be added, ensuring better readability. 37 37 38 - == **Feedbackitems** ==37 +[[image:Main.Images.Release Blog.WebHome@release-220-edit-annotation.png]] 39 39 40 -//__ Generationof security logicAPI Gatewayincase of API Key as security method is improved__//41 - Withthisrelease,wehave improved thegenerationof securitylogicwithinthe CreatephaserelatedtoAPI Gatewaysthat usetheAPI Key methodastheir security mechanism.39 +//__Filter rejection warnings__// 40 +A discard channel is required for filter components when “Throw exception on rejection” value is set to false. 42 42 43 -//__User Roles are sorted alphabetically__// 44 -All user roles under User Management are now also sorted alphabetically. 42 +[[image:Main.Images.Release Blog.WebHome@release-220-discard-channel.png]] 45 45 46 -//__ Name of keystore for user managementnow includes the environment__//47 - To improve thenamingof the downloaded keystorethat needstobedistributedtoexternal parties,we haveaddedthenameoftheenvironmenttothe filename.Youcandistinguishbetweenthevariousenvironmentsby lookingatthefilename.44 +//__Manage Explore__// 45 +An issue has been fixed where navigating to the Explore tab in Manage would sometimes redirect users to the homepage. 48 48 49 -//__Improved Topic calculations in Design Architecture__// 50 -Following our earlier improvements on the best practice configuration of topics we have now additionally updated the calculations on "Topic Storage" level to ensure that the configuration of a user is related to the total Assigned Size on "Topic Storage" level. 51 - 52 -== **Bug fixes ** == 53 - 54 -//__Consolidated upgrade process cloud template__// 55 -With this release, we have removed some specific update options that could cause mismatches between what was visually displayed and what was happening in the cloud. 56 - 57 -//__Ensure users can deploy release on environments they have edit rights on__// 58 -Currently, users with limited rights in Deploy, for example, only edit rights in Test, can now activate and deploy releases ready for other environments but need to be deployed on the environment for which they have the rights to do so. 59 - 60 60 == **Fancy Forum Answers** == 61 61 62 62 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: 63 63 64 -* [[ APISecuritynotupdatedinall entry flow>>https://my.emagiz.com/p/question/172825635703363718||target="blank"]]65 -* [[ Preventingexceptionstriggeringon HTTP 400 statuscode>>https://my.emagiz.com/p/question/172825635703351155||target="blank"]]66 -* [[De ployment of 3rdgenruntimestoAzureKubernetes Service(AKS containers)>>https://my.emagiz.com/p/question/172825635703350980||target="blank"]]51 +* [[Create an overview of DataFlows without any datatraffic>>https://my.emagiz.com/p/question/172825635703811872||target="blank"]] 52 +* [[Flowtest does not work>>https://my.emagiz.com/p/question/172825635703811773||target="blank"]] 53 +* [[Debugger blocks all other traffic>>https://my.emagiz.com/p/question/172825635703812013||target="blank"]] 67 67 68 -== **Key takeaways** ==55 +== **Key Takeaways** == 69 69 70 -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:57 +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: 71 71 72 72 * If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]] 73 73 * If you have feedback or ideas for us, talk to the Platypus 74 -* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these. 61 +* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these. 75 75 * Clear your browser cache (Ctrl + Shift + Del) 76 -* Check out the release notes [here] 63 +* Check out the release notes [[here>>doc:Main.Release Information.Portal.219 - Creation Carousel.WebHome||target="blank"]] 77 77 * Start thinking about how the license tracker can aid your development 78 78 * Start thinking about major, minor, and patch 79 -* Upgrade to the latest build number 80 80 * Keep making great integrations 81 81 82 82 Let's stay in touch and till next time! ... ... @@ -84,6 +84,11 @@ 84 84 {{info}} 85 85 ~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]] 86 86 87 -~*~* Indicates a GEN3-only feature. 88 -{{/info}})))((({{toc/}}))){{/container}} 73 +{{/info}} 74 +))) 75 + 76 +((( 77 +{{toc/}} 78 +))) 89 89 {{/container}} 80 +{{/container}}