Changes for page 213 - Joyful Journeys
Last modified by Carlijn Kokkeler on 2024/04/18 13:07
From version 373.1
edited by Carlijn Kokkeler
on 2024/04/18 13:07
on 2024/04/18 13:07
Change comment:
There is no comment for this version
To version 159.1
edited by Carlijn Kokkeler
on 2023/10/11 09:22
on 2023/10/11 09:22
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 -2 13-Joyful Journeys1 +206 - Situational Deployment - Content
-
... ... @@ -1,83 +1,74 @@ 1 1 {{container}} 2 -{{container layoutStyle="columns"}} 3 -((( 2 +{{container layoutStyle="columns"}}((( 4 4 [[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]] 5 5 6 -**Hi there, eMagiz developers!** In th is release,severalimprovementsforpop-upshavebeen madesothat moreuserfriendlymessagesareshown thatreflectactualbehaviour.Moreover,formattingand alignmentmprovementshavebeen madetoimprovethe user journey. Lastly, we haveworkedonsomemorefeedback itemsand severalmorebugfixes havebeen done.5 +**Hi there, eMagiz developers!** In the last few weeks, we have done much work for the Deploy phase. On top of that, we have worked on several store functionalities. Next to this, we have several smaller feedback items from our hackathon efforts that are now released to you. 7 7 8 -== ** Pop-up Improvements** ==7 +== **Deployment Plan** == 9 9 10 -//__ Propertyreleases__//11 - Whenanew propertyreleaseiscreated,this propertyreleasecan nownot onlybeviewedbutalso releasepropertiescanbedeleted.9 +//__Improved deployment plan to make the process better and more predictable__// 10 +The algorithm for genarating a default deployment plan is improved to keep jms downtime and alerting to a minimum. Next to this, the start/stop/restart machine deployment steps are now also executed correctly for aws and on-premises machines. 12 12 13 -[[image:Main.Images.Release Blog.WebHome@release-blog-213-joyful-journeys-property-release.png]] 12 +//__Editing release properties__// 13 +With this release, it will be possible to change the description of a property by editing the property. 14 14 15 -//__ Runtimedeletion__//16 - Whendeletinga runtime, the errormessagemore descriptive. The errormessagewill now includehenamesof theflows that run on thecontainer.15 +//__JMS memory setting check__// 16 +A change in memory settings triggers redeployment of the container now. 17 17 18 -//__ Wiretap& debug error messages__//19 - The errormessagesthat may be displayed when using wiretaps andtheebuggerhavebeenimproved,thesearenowmoreuser friendly.18 +//__Properties tab__// 19 +We have removed the deprecated tab Properties in the Deploy phase. 20 20 21 -//__ Action messages__//22 - Theformattingofactionmessages regardingchangesinretentionbytes/hourshasbeenimproved. The actionmessagewillnow display thecorrect,actualbehaviour.21 +//__Cleanup old images__// 22 +When a release is removed, the related unused images in the on-premises machines will be removed as well. 23 23 24 -== **Formatting & Alignments** == 24 +//__Performance improvements for loading releases__// 25 +Performance improvements have been implemented for loading releases in Deploy. Releases should now load faster than before. All functionality should remain exactly the same as before. 25 25 26 - //__Inputfields__//27 - Multipleinputfields have been updated such that they expand when the amount of characters exceeds the default size. These updates were done to cater to large expressions.27 +== **Store Improvements** == 28 + 28 28 29 -//__UI improvements__// 30 -UI improvements for static input components have been done and the tooltip for optional/required toggles has been improved. 30 +== **Feedback Items** == 31 31 32 -//__ Componentchangesreversion__//33 - Intheflowdesignerabugcouldoccurwherethechangesto acomponentwouldberevertedifthe editingpop-upwouldbekeptopenfor some minutes without havingsaved thechangesyet.This has beenfixed.32 +//__Alerting manual pause__// 33 +A few releases ago we changed the behavior of alerting in the deployment plan. Now each time when a deployment plan is executed the alerting will be automatically re-enabled when the deployer closes the deployment plan or closes the web browser. The majority of the users are happy with the new behavior, but there are some use cases that you do not want start the alerting immediately. With this release, if alerting has been paused manually, this will not be activated automatically after a release deployment. 34 34 35 -//__ State generationstatistics__//36 -The s tategenerationphswillnowshowthe correctnumber ofcache hits andmisses.35 +//__Ordering of graphs in Manage__// 36 +The graphs in Manage are now ordered according to importance. This means that runtime statistics are sorted by "Process CPU usage" (highest first), queue statistics are sorted by "Messages in queue" (highest first), and HTTP statistics are sorted by "Unsuccessful requests" (highest first). 37 37 38 -//__ Queuebrowsertimestamps__//39 -All times tampformatting inhequeuebrowser isnow alignedtoyyyy-MM-ddHH:mm:ss.SSS.38 +//__UTC times in Grafana panels__// 39 +All Grafana panels now show UTC times, which are normally used in eMagiz, instead of local (browser) time zones. This way, it is easier to match graphs with logging events or alerts. 40 40 41 -//__ Additionanddeletionof internalrecipients__//42 - Internalrecipientsarenowaddedanddeletedcorrectly. Before,aninternalrecipientcouldbeaddedandthereafterdeleted automaticallywhenrefreshing the page.41 +//__Update flow designer version__// 42 +The framework used in the flow designer has been updated to the latest version. 43 43 44 -== **Feedback Items** == 44 +//__Carwash track TLS versions in logging__// 45 +A new logging feature will be released, enabling us to make better choices in deprecating old encryption standards. 45 45 46 -//__ Update flows__//47 - InCreate > Resources,abutton "Updateflows"hasbeenaddedto updateversions ofall flowsinwhich a resourceis used. This is particularly usefulwhenchanging a resouceused across multipleflows such as topic message definitionsnevent processors.47 +//__Moving channels in the flow designer__// 48 +Moving already attached channels in the flow designer has been made sligthly easier. 48 48 49 -//__ Q&A forumsearch__//50 - Theoptiontosearch bypressing theEnterkeyhasbeen addedtotheQ&Aforum.50 +//__Topic sizes description change__// 51 +In the change description (and History) when altering the topic size of a topic the new and old value were switched around creating confusion, this has been resolved. 51 51 52 -//__ Memorysettings__//53 - Itisnowpossible to changethe memorysettingsof anewlyaddedcontainerbeforepressing"Apply to environment".53 +//__Password change notification__// 54 +When an account password change request is made, even when this fails, a mail is sent to the account owner to inform the owner about the action. 54 54 55 -//__ Runtime validation__//56 - Validationforruntimesthat aremovedfromonpremisesto thecloud orviceversahasbeenimproved.56 +//__Password comparison__// 57 +When changing a password, it is compared to a list of known database breaches for security. A warning is shown when the password corresponds with a password in the database. 57 57 58 -//__Runtime overview image versions__// 59 -Insight into intended and actual deployments has been improved. If the release version number on runtimes is different compared with the release, this is shown in the runtime overview. 60 60 61 61 == **Bug Fixes** == 62 62 63 -//__ Removalfonramp__//64 - Wefixed anissuewhereitwasnot possible toremovehelastonramplinkedtoasplittedentry(thatwas an all-entry before).62 +//__Flow designer styling__// 63 +The styling of the flow designer's left component panel has been restructured, solving a rare bug which would break the styling of certain functionalities. 65 65 66 -//__Runtime statistics details__// 67 -We fixed an issue where heap memory usage data was accumulating when zooming out in the runtime statistics details dashboards. 68 - 69 -//__Deployment prechecks__// 70 -During deployments, prechecks can be executed on runtimes level for runtimes that still have to be deployed. These prechecks can be executed via Deploy > Architecture. 71 - 72 72 == **Fancy Forum Answers** == 73 73 74 74 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: 75 75 76 -* [[Changing filename based on attribute>>https://my.emagiz.com/p/question/172825635703696968||target="blank"]] 77 -* [[Payload must be an instance of a Map>>https://my.emagiz.com/p/question/172825635703709401||target="blank"]] 78 -* [[Promoting a system to a split gateway>>https://my.emagiz.com/p/question/172825635703722185||target="blank"]] 69 +* [[Getting files from subfolders (FTP)>>https://my.emagiz.com/p/question/172825635703568575||target="blank"]] 79 79 80 -== **Key Takeaways** ==71 +== **Key takeaways** == 81 81 82 82 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: 83 83 ... ... @@ -85,9 +85,10 @@ 85 85 * If you have feedback or ideas for us, talk to the Platypus 86 86 * Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these. 87 87 * Clear your browser cache (Ctrl + Shift + Del) 88 -* Check out the release notes [ [here>>doc:Main.Release Information.Portal.213 - Joyful Journeys.WebHome||target="blank"]]79 +* Check out the release notes [here] 89 89 * Start thinking about how the license tracker can aid your development 90 90 * Start thinking about major, minor, and patch 82 +* Upgrade to the latest build number 91 91 * Keep making great integrations 92 92 93 93 Let's stay in touch and till next time! ... ... @@ -95,11 +95,6 @@ 95 95 {{info}} 96 96 ~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]] 97 97 98 -{{/info}} 99 -))) 100 - 101 -((( 102 -{{toc/}} 103 -))) 90 +~*~* Indicates a next-generation-architecture only feature. 91 +{{/info}})))((({{toc/}}))){{/container}} 104 104 {{/container}} 105 -{{/container}}