Changes for page 207 - Aligned State
Last modified by Carlijn Kokkeler on 2024/04/18 13:10
From version 132.1
edited by Erik Bakker
on 2023/08/01 13:50
on 2023/08/01 13:50
Change comment:
There is no comment for this version
To version 91.1
edited by Erik Bakker
on 2023/03/14 06:52
on 2023/03/14 06:52
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 - 202-New Equilibrium1 +194 - Big Leap - Content
-
... ... @@ -2,68 +2,66 @@ 2 2 {{container layoutStyle="columns"}}((( 3 3 [[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]] 4 4 5 -**Hi there, eMagiz developers!** In the last fewweeks, we havecrossed our t's anddottedouri'sonthereleaseproperties functionalitythat willimpactthe daytoday lifeofevery userworkingwithinthe platform.The focusofthereleaseblogwillconsequentlyalsobeon thissubject. On top of that wehave severaladditionalsmallerfeedbackitemcomingfromourhackathonefforts thatarenowreleasedtoyou.5 +**Hi there, eMagiz developers!** In the last couple of weeks, we have worked around the clock to release various improvements points within the 3rd generation runtime and elsewhere. Among others we have improved the feedback provided when a flow can't start due to an incorrect transformation. Improved when certain logging is triggerd and improved the stability of our internal infrastructure. On top of that we fixed several bug fixes surrounding other parts of the platform. So without further ado let us take a look at all these improvements. 6 6 7 -== **Release Properties** == 8 -As of this release, we will introduce a new way of handling properties for all our clients. There are several key changes compared to the current way of managing your properties. 7 +== **3rd generation improvements** == 9 9 10 -{{info}}For more information please check out the following microlearnings: 9 +//__Better feedback in error log when a corrupt stylesheet is encountered__// 10 +We have improved the logging within a 3rd generation runtime that identifies the broken resource by name within a container and informs you to navigate to Create -> Resources to see in which flows the resource is used so you can take the appropriate action. 11 11 12 -* [[microlearning>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.crashcourse-platform-deploy-property-management-new.WebHome||target="blank"]] 13 -* [[microlearning>>doc:Main.eMagiz Academy.Microlearnings.Novice.eMagiz Store.novice-emagiz-store-merge-store-data-model.WebHome||target="blank"]] 14 -* [[microlearning>>doc:Main.eMagiz Academy.Microlearnings.Novice.eMagiz Store.novice-emagiz-store-merge-store-data-model.WebHome||target="blank"]] 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 number of alerts you will receive on this topic when your model runs on the 3rd generation monitoring stack. 15 15 16 - Should you have any questions inadvance,please get in touchwith usat [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]].17 - {{/info}}15 +//__Improved Manage Dashboard__// 16 +This release improves what you can see in the Manage Dashboard after you migrated your model to the 3rd generation runtime architecture. 18 18 19 - == ** DeployArchitecture- ApplyToEnvironmentprovements** ==20 - Asofthisrelease,wewill showyouaistofallchangesabout tobechanged onceyoupress"Applytotheenvironment"inDeployArchitecture. This willmake itclearerfor users,especially thoseworkinginteams,what willchange whenpressing thisbutton.18 +//__Improved process surrounding "slot standby" and "slot wakeup" for 3rd generation runtimes__// 19 +When a slot is put into standby mode we now also stop all on-premise runtimes to avoid excessive logging (and alerting) on your models that have this functionality activated. 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. 21 21 22 -[[image:Main.Images.Release Blog.WebHome@201-release-blog--apply-to-environment-example.png]] 21 +//__Improved process of deploy preparation__// 22 +With this release we have improved the process through which your deploy action is preparated by eMagiz. As a result the chances of unexpected behavior occuring in your model are drastically reduced. 23 23 24 - == ** BreadcrumbnavigationineMagiz** ==25 - Thisreleaseintroducesthe "breadcrumb" navigationincertainpartsofeMagiz.Thiswillmostly be noticedand impacttheCreate phasewhen youcheck outyourtransformationorsystemmessage on theflow level.Apart from there,thenavigationis implementedconsistentlyacrosstheportalfor aunifiedlookandfeel.24 +//__Improved migration of Streaming container__// 25 +When migrating your streaming container we now take into account whether "custom error handling" is used within one of the event processors. Based on that determination specific additional components are added to ensure that the streaming container will work after migrating without any manual intervention. 26 26 27 -[[image:Main.Images.Release Blog.WebHome@201-release-blog--breadcrumb-navigation-example.png]] 27 +//__Add History to Notifications in Manage__// 28 +To improve the auditability of our platform we have introduced an audit trail to the Notification section in Manage for models running on our 3rd generation monitoring stack. This way it is always visible when the notifications were paused and who paused or unpaused the notifications. 28 28 29 -== **Feedback Items** == 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 helptexts to clarify what each graph our table displays to you. 30 30 31 -//__Improved l ayoutofcatalogpagein Design__//32 -We have improved the l ayoutoftheAPI Catalogoverview inDesignfor our API Gateway users. Among others,we have introduceda scrollbartogeta betteroverview of severaloperations.33 +//__Improved help text for network volumes__// 34 +With this release we have improved the help text that explains network volumes and how to use them within our solution. 33 33 34 -//__Improved layout of "Edit integration" pop-up for API Gateway integrations__// 35 -Currently, the full path of your backend system will be shown when opening the "Edit integration" pop-up on your API Gateway integration. 36 +{{warning}}Should you be interested in migrating your model to our new 3rd generation architecture, don't hesistate 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}} 36 36 37 -//__Additional help texts on Design Architecture__// 38 -We have improved the help texts in Design Architecture concerning the Event Streaming topic storage overview. 38 +== **Feedback items ** == 39 39 40 -//__ ImprovedAuditTrailonseveralplaces__//41 - In several placesintheportal, we haveimproved the audittrailto specifybetterwhochanged whatatwhichpointin time.40 +//__Removed OData as option for an API Gateway operation__// 41 +With this release, we have removed the OData operation option as it was not used and was not fully supported anymore by the platform. 42 42 43 -//__ Removedthe erroneousalerton messagemappingwhenhavingapassthrough API__//44 - This releaseremovestheerroneousalertpeoplereportedon"errorsin messagemapping"for apassthrough API.43 +//__Changes in API Gateway operation paths is automatically updated in Create__// 44 +When you change your path on a hosted API Gateway we will now automatically update the accompanying component in your Create (all-)entry. 45 45 46 - ==**BugFixes**==46 +{{warning}}Make sure to check the changes and create a new version afterward to deploy the changes.{{/warning}} 47 47 48 -//__Avoid clicking on other components while deleting another__// 49 -To avoid unexpected behavior, we now ensure that nothing can be selected once you see the "deletion" pop-up when you want to remove something in the flow designer. 48 +== **Bug fixes ** == 50 50 51 -//__ Improvedvalidationfeedbackinmigratingtothenext-generationrchitecture__//52 -We have improved thevalidationfeedbackwhen migrating to the next-generationarchitecture.50 +//__Prevent endless loop in Deploy -> User Management__// 51 +With this release, we have changed the way we update properties when user management is updated for an API gateway using the API Key security mechanisms. This will prevent the endless loop that could now happen on occasion. 53 53 54 -//__Make sure that user credentials can be viewed with view rights__// 55 -This release makes sure that the user credentials in Deploy can be considered with view rights and not only when having edit rights. 53 +{{warning}}Any operation that is incorrectly deleted from Deploy while still end up in the logic and could cause issue so pay attention when removing API Gateway operations.{{/warning}} 56 56 57 -//__ Refreshbehaviorwithin the deployment plan is fixed__//58 - Thisreleasechangestherefresh behaviorwithinthedeploymentplanto show,once more,the"to be installed"flowsbeforetheuserpressesExecute.55 +//__Update error handling during migration to the 3rd generation runtime__// 56 +As of now the error handling of all flows is correctly updated whilst migrating to the 3rd generation runtime configuration. 59 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 -* [[ ReplacingLegacy eMagiz-MendixConnector:MigrationPlan>>https://my.emagiz.com/p/question/172825635703517317||target="blank"]]65 -* [[ Unknowncharacter(s)doesnot createerrormessage.>>https://my.emagiz.com/p/question/172825635703517488||target="blank"]]66 -* [[S plitgatewayconfigurationfor local GEN3 gateway>>https://my.emagiz.com/p/question/172825635703517580||target="blank"]]62 +* [[Access Spring ApplicationContext within Groovy Script>>https://my.emagiz.com/p/question/172825635703325469||target="blank"]] 63 +* [[Configuration problem: Failed to locate '$autoCreateChannelCandidates'>>https://my.emagiz.com/p/question/172825635703312551||target="blank"]] 64 +* [[503 on SOAP Webservice hosted in eMagiz>>https://my.emagiz.com/p/question/172825635703325386||target="blank"]] 67 67 68 68 == **Key takeaways** == 69 69