Changes for page 213 - Joyful Journeys
Last modified by Carlijn Kokkeler on 2024/04/18 13:07
From version 134.1
edited by Erik Bakker
on 2023/08/01 14:11
on 2023/08/01 14:11
Change comment:
There is no comment for this version
To version 290.1
edited by Carlijn Kokkeler
on 2023/12/06 14:25
on 2023/12/06 14:25
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 -20 2-NewEquilibrium1 +210 - Deployment Delights - Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki. ebakker1 +XWiki.CarlijnKokkeler - Content
-
... ... @@ -1,79 +1,69 @@ 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 th e lastfew weeks, we havecrossed ourt's and dottedouri'sontherelease propertiesfunctionalitythatwillimpactthedaytodaylifeofeveryuser workingwithintheplatform.The focus oftherelease blog will consequentlyalsobeonthis subject.Ontopof that wehave several additional smallerfeedback item comingfromour hackathonefforts that arenowreleased to you.6 +**Hi there, eMagiz developers!** In this release, we have invested our effort to improve the performance and experience of our platform in the Deploy phase. Next to that, we did several bug fixes, not only for the Deploy phase, but also for the Store. Lastly, we made some changes to the alerts that you may be receiving. 6 6 7 -== **Release Properties** == 8 -As of this release, we will introduce a new way of handling properties for all our clients. This change intends to solidify the relationship between a release and a property value. Before, in the current generation architecture, timing of changing properties was crucial to avoid costly mistakes on Production. On top of that it was not always clear whether a property value was indeed updated as it was not linked to something that was deployed. These considerations let us to change the property management behavior not only on our next-generation architecture but also on our current generation architecture. Having said that, there are several key changes compared to the current way of managing your properties. Most notably among these are: 8 +== **Alerts** == 9 9 10 -* The current properties tab in Deploy will disappear. The new overview of the properties (and their values) can be found under the "Create phase release" in Deploy -> Releases 11 -* Property placeholders (i.e. the names of properties as given in Create) are now automatically created for you. This to avoid mistakes when filling them in. 12 -* When adding or editing a property you can *now* select multiple runtimes for which the property applies. This is mainly beneficial for those running in a double lane setup or having a distributed landscape of containers. 13 -* A, for most, new concept of a "property release" is introduced. With the help of this functionality you can easily change a property on Production without having to create a completely new release in Test and promote it to the Production environment. 10 +//__Topic approaching max size alert__// 11 +The alert ‘topic approaching maximum size’ has been temporarily disabled due to a high number of false positives. 14 14 15 -{{info}}For more information please check out the following microlearnings: 13 +//__Missing metrics alert__// 14 +We solved an issue where the ‘missing metrics’ alert did not always contain the full container name. 16 16 17 -* [[Property Management>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.crashcourse-platform-deploy-property-management-new||target="blank"]] 18 -* [[Actualize properties - current generation architecture>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.crashcourse-platform-deploy-actualize-properties-new.WebHome||target="blank"]] 19 -* [[Actualize properties - next generation architecture>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.crashcourse-platform-deploy-actualize-properties-gen3-new.WebHome||target="blank"]] 20 - 21 -Should you have any questions in advance, please get in touch with us at [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]. 22 -{{/info}} 23 - 24 -== ** Manage - Next generation graphs improvements ** == 25 -As of this release, we will create a condensed view of your metrics when zooming out in the Manage phase graphs. This will significantly improve the performance of the manage graphs as we retrieve and show less fine-grained information when zooming out. 26 - 27 -[[image:Main.Images.Release Blog.WebHome@202-release-blog--manage-graphs-zoomed-out.png]] 28 - 29 29 == **Feedback Items** == 30 30 31 -//__Improved e ditability when testing ineMagizwihout Editrights in Create__//32 -W ithouthavingedit rights intheCreatephaseyou could alreadydoalot onthe level of flowtestsinMagiz. However,thereweresomeoversights wemissedduringtheimplementation. Thesehavebeenfixedallowing thosewithout editrights to nowalso change thename anddescriptionofthe testcase.18 +//__Improved release build process__// 19 +When a new release will be activated, no longer all containers will be rebuild but only affected containers will be rebuild. This should decrease the time for a release to be ready to be deployed. 33 33 34 -//__ Improved auditability onDeployArchitecture__//35 - To improve the audtiabilityonDeployArchitecture we nowalsologwhensomeone withAdmin rightschangesspecificfunctionsonhislevel(i.e.FixedIP).21 +//__Container version overview__// 22 +Due to the improved build process for containers, the release versions and container versions will not longer be the same anymore. Therefore we introduce a way where you can look up to see which container versions are linked to a specific release. This can help you to identify if your containers that are running have the right version according to the release. 36 36 37 -//__Test your own exported work__// 38 -We have now made it possible to test your own exported work to the Store before it gets approved. This will increase the quality of store items we have, and our partners, have on offer within the store. 24 +[[image:Main.Images.Release Blog.WebHome@release-blog-210-deployment-delights-container-overview.png]] 39 39 40 -{{info}}In case the concept of the store is new for you please check out this [[Fundamental>>doc:Main.eMagiz Academy.Fundamentals.fundamental-emagiz-store.WebHome||target="blank"]]{{/info}} 26 +//_Improved deployment process_// 27 +The improved release build process, as mentioned above, brings another major improvement to the platform. Because container versions will not be updated regularly we can identify during a deployment which container should get a new container version. Only the ones that should get a new version will be deployed and restarted, all other containers will not go down and keep running. This decreases the deployment time and improves the performance. 41 41 42 -//__ Improved AuditTrailonseveral places__//43 - In several placesin theportal,wehave improvedtheaudittrailtospecify better whochangedwhatatwhichpoint intime.29 +//__Rebuilding of images__// 30 +Changing the list of flows that should run on a container will now trigger the rebuilding of images. 44 44 45 -//__Removed the erroneous alert on message mapping when having a passthrough API__// 46 -This release removes the erroneous alert people reported on "errors in message mapping" for a passthrough API. 47 - 48 48 == **Bug Fixes** == 49 49 50 -//__ Avoid clicking on othercomponentswhiledeletinganother__//51 -T oavoid unexpected behavior, wenowensure thatnothingcanbe selectedonceyouseethe "deletion"pop-upwhenyou want to removeomethingintheflow designer.34 +//__Runtime metrics processing__// 35 +The collection and publishing of runtime metrics is no longer synchronized across containers, which improves their processing. 52 52 53 -//__ Improved validation feedback inmigrating to theext-generationarchitecture__//54 -We have improvedthevalidationfeedbackwhenmigratingto thenext-generationarchitecture.37 +//__Deployment plan__// 38 +We solved a bug where a deployment step in the execution of the deployment plan could randomly get stuck. 55 55 56 -//__ Makesure thatusercredentialscan be viewed with view rights__//57 - Thisrelease makes surethattheusercredentialsinDeploycanbeconsideredwith viewrightsandnotonly whenhavingedit rights.40 +//__View all store items__// 41 +An issue has been fixed where it was not possible to load more store items in the left panel in the Create phase Flow Designer. 58 58 59 -//__ Refreshbehaviorwithin the deployment plan is fixed__//60 - Thisreleasechangestherefreshbehaviorwithinthe deploymentplantoshow,once more,the "tobeinstalled"flowsbeforetheuserpressesExecute.43 +//__Out of memory behavior__// 44 +We improved the out of memory behavior of runtimes. Runtimes will now always restart when an out of memory error occurs. 61 61 46 +//__Max fetch size__// 47 +In the Flow Designer, we improved the help text of the advanced option of ‘max fetch size’ for the Mail Inbound Adapter component to better describe how that option affects the component's behavior. 48 + 62 62 == **Fancy Forum Answers** == 63 63 64 64 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: 65 65 66 -* [[Replacing Legacy eMagiz-Mendix Connector: Migration Plan>>https://my.emagiz.com/p/question/172825635703517317||target="blank"]] 67 -* [[Unknown character(s) does not create error message.>>https://my.emagiz.com/p/question/172825635703517488||target="blank"]] 68 -* [[Split gateway configuration for local GEN3 gateway>>https://my.emagiz.com/p/question/172825635703517580||target="blank"]] 53 +* [[Deleting object failed for security reasons>>https://my.emagiz.com/p/question/172825635703671061||target="blank"]] 54 +* [[How do I delete a user?>>https://my.emagiz.com/p/question/172825635703670973||target="blank"]] 55 +* [[Import RCV-Shipment & RCV-Receipt XSD from Boltrics>>https://my.emagiz.com/p/question/172825635703671171||target="blank"]] 56 +* [[Add day in XPath header enricher>>https://my.emagiz.com/p/question/172825635703671325||target="blank"]] 57 +* [[Missing Body Java type resulting in problems>>https://my.emagiz.com/p/question/172825635703683790||target="blank"]] 69 69 59 + 70 70 == **Key takeaways** == 71 71 72 -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:62 +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: 73 73 74 74 * If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]] 75 75 * If you have feedback or ideas for us, talk to the Platypus 76 -* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these. 66 +* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these. 77 77 * Clear your browser cache (Ctrl + Shift + Del) 78 78 * Check out the release notes [here] 79 79 * Start thinking about how the license tracker can aid your development ... ... @@ -86,6 +86,12 @@ 86 86 {{info}} 87 87 ~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]] 88 88 89 -~*~* Indicates a GEN3-only feature. 90 -{{/info}})))((({{toc/}}))){{/container}} 79 +~*~* Indicates a next-generation-architecture only feature. 80 +{{/info}} 81 +))) 82 + 83 +((( 84 +{{toc/}} 85 +))) 91 91 {{/container}} 87 +{{/container}}