Changes for page 222 - Flee Frustration
Last modified by CarlijnKokkeler on 2024/06/05 09:31
Summary
-
Page properties (2 modified, 0 added, 0 removed)
Details
- Page properties
-
- Title
-
... ... @@ -1,1 +1,1 @@ 1 -20 6-SituationalDeployment1 +220 - Patch Parade - Content
-
... ... @@ -1,93 +1,72 @@ 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 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.6 +**Hi there, eMagiz developers!** 6 6 7 -== ** Deployment Plan** ==8 +== **Feedback Items** == 8 8 9 -//__I mproved deploymentplantomakethe process betterandmore predictable__//10 - Thealgorithmforgenaratinga defaultdeploymentplan is improvedto keepjms downtime andalertingtoaminimum. Nextto this, thestart/stop/restartmachinedeploymentstepsarenowalsoexecutedcorrectlyforawsandon-premises machines.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 -//__Editing release properties__// 13 -With this release, it will be possible to change the description of a property by editing the property. 13 +[[image:Main.Images.Release Blog.WebHome@release-220-integration-pattern.png]] 14 14 15 -//__ JMS memorysettingcheck__//16 -A changeinmemorysettings triggers redeployment ofthecontainernow.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 -//__Properties tab__// 19 -We have removed the deprecated tab Properties in the Deploy phase. 18 +[[image:Main.Images.Release Blog.WebHome@release-220-manage-history.png]] 20 20 21 -//__ Cleanupold images__//22 - Whenareleaseis removed, the related unusedimages in theon-premisesmachineswillberemovedaswell.20 +//__Search boxes__// 21 +Search boxes in the properties overview are now shown by default. 23 23 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. 23 +[[image:Main.Images.Release Blog.WebHome@release-220-search-boxes.png]] 26 26 27 -== **Store Improvements** == 25 +//__Set as mapped__// 26 +It is now possible to choose whether to set/unset all attributes of an entity as mapped in design. 28 28 29 -//__Message definition elements order__// 30 -We fixed an issue that the order of message definition elements was changed after being imported. 28 +[[image:Main.Images.Release Blog.WebHome@release-220-mapped-entity.png]] 31 31 32 -//__ Improtingastoreitem with synchronous message definitions__//33 - Wefixedanissuethat importingastoreitemwithsynchronousmessage definitionswentwrong. Now,theimported message definitionsshouldcorrespondwiththe exported message definitions.30 +//__SSL settings__// 31 +Changes can now be deployed on SSL level without creating a new version of a flow in Create. 34 34 35 -//__ Importing storeitmes containing static copies__//36 -We fixed anissue that storeitemsweremissingstatic copies.Now,storeitems withstaticcopiesareimportedcorrectly.33 +//__Machine deletion__// 34 +When trying to delete a machine that still has containers linked to it, the user will be presented with a pop-up explaining why the machine cannot be deleted. 37 37 38 - == **FeedbackItems** ==36 +[[image:Main.Images.Release Blog.WebHome@release-220-machine-deletion.png]] 39 39 40 -//__Alerting manual pause__// 41 -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. 38 +== **Bug Fixes** == 39 +//__Annotation styling__// 40 +It is now possible to use enters in Annotations, so that multiple line spaces can be added, ensuring better readability. 42 42 43 -//__Ordering of graphs in Manage__// 44 -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). 42 +[[image:Main.Images.Release Blog.WebHome@release-220-edit-annotation.png]] 45 45 46 -//__ UTC timesinGrafana panels__//47 -A llGrafanapanelsnow show UTC times,which arenormallyusedineMagiz, insteadoflocal (browser)timezones.Thisway,it iseasiertomatchgraphs with loggingevents oralerts.44 +//__Filter rejection warnings__// 45 +A discard channel is required for filter components when “Throw exception on rejection” value is set to false. 48 48 49 -//__Update flow designer version__// 50 -The framework used in the flow designer has been updated to the latest version. 47 +[[image:Main.Images.Release Blog.WebHome@release-220-discard-channel.png]] 51 51 52 -//__ Carwash track TLS versionsinlogging__//53 -A newlogging featurewillbereleased,enablingustomake betterchoicesindeprecating old encryptionstandards.49 +//__Manage Explore__// 50 +An issue has been fixed where navigating to the Explore tab in Manage would sometimes redirect users to the homepage. 54 54 55 -//__ Moving channelsin theflow designer__//56 - Movingalready attachedchannelsintheflow designerhasbeenmade sligthlyeasier.52 +//__Page refreshing__// 53 +Switching between environments refreshes the Queue browser and Redelivery pages correctly for the selected environment. 57 57 58 -//__ Topic sizes description change__//59 - Inthechangedescription(andHistory)whenalteringthetopicsize ofatopicthenewandoldvaluewereswitchedaroundcreatingconfusion,thishas been resolved.55 +//__Message redelivery__// 56 +An issue has been fixed where large messages would be shown at the bottom of the page instead of the right side of the page. 60 60 61 -//__ Password changenotification__//62 -W henanaccountpassword changerequestismade,even when thisfails,amailissenttothe accountowner toinformtheowneraboutthe action.58 +//__Deployment plan__// 59 +We have implemented changes that should prevent a discrepantion between the overview of runtimes to be deployed shown at the beginning of a deployment plan (or at individual machine-type steps) and the actual execution of relevant steps. 63 63 64 -//__Password comparison__// 65 -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. 66 - 67 -//__Inactive user alerting__// 68 -Inactivated users are now removed from all alert settings (included “disabled“ settings) to avoid undesirable notifications. 69 - 70 -//__Alphabetical sorting on user level in HTTP statistics__// 71 -Variables in the 3rd generation runtimes HTTP statistics detail pages are now sorted case insensitive. 72 - 73 -== **Bug Fixes** == 74 - 75 -//__Flow designer styling__// 76 -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. 77 - 78 -//__Partial search for messages__// 79 -It is now possible to search on messages partially in Manage Monitoring. For example, search for Uptime can be done by searching for "up" "time" "ptim". 80 - 81 -//__Disk usage after cloud template update__// 82 -Several accounts showed significantly more disk usage after the last cloud template update, this has been resolved. 83 - 84 84 == **Fancy Forum Answers** == 85 85 86 86 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: 87 87 88 -* [[Getting files from subfolders (FTP)>>https://my.emagiz.com/p/question/172825635703568575||target="blank"]] 65 +* [[Create an overview of DataFlows without any datatraffic>>https://my.emagiz.com/p/question/172825635703811872||target="blank"]] 66 +* [[Flowtest does not work>>https://my.emagiz.com/p/question/172825635703811773||target="blank"]] 67 +* [[Debugger blocks all other traffic>>https://my.emagiz.com/p/question/172825635703812013||target="blank"]] 89 89 90 -== **Key takeaways** ==69 +== **Key Takeaways** == 91 91 92 92 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: 93 93 ... ... @@ -95,10 +95,9 @@ 95 95 * If you have feedback or ideas for us, talk to the Platypus 96 96 * Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these. 97 97 * Clear your browser cache (Ctrl + Shift + Del) 98 -* Check out the release notes [here] 77 +* Check out the release notes [[here>>doc:Main.Release Information.Portal.219 - Creation Carousel.WebHome||target="blank"]] 99 99 * Start thinking about how the license tracker can aid your development 100 100 * Start thinking about major, minor, and patch 101 -* Upgrade to the latest build number 102 102 * Keep making great integrations 103 103 104 104 Let's stay in touch and till next time! ... ... @@ -106,6 +106,11 @@ 106 106 {{info}} 107 107 ~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]] 108 108 109 -~*~* Indicates a next-generation-architecture only feature. 110 -{{/info}})))((({{toc/}}))){{/container}} 87 +{{/info}} 88 +))) 89 + 90 +((( 91 +{{toc/}} 92 +))) 111 111 {{/container}} 94 +{{/container}}