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,50 +1,58 @@ 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 +//__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. 15 15 16 - 17 - 18 -== **Store Improvements** == 19 - 18 +[[image:Main.Images.Release Blog.WebHome@release-220-manage-history.png]] 20 20 21 -== **Feedback Items** == 20 +//__Search boxes__// 21 +Search boxes in the properties overview are now shown by default. 22 22 23 -//__Alerting manual pause__// 24 -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. 23 +[[image:Main.Images.Release Blog.WebHome@release-220-search-boxes.png]] 25 25 26 -//__ Orderingof graphsin Manage__//27 - ThegraphsinManage are now orderedaccordingtoimportance. Thismeansthat runtimestatistics aresortedby "ProcessCPU usage" (highestfirst),queuestatistics aresortedby "Messages inqueue" (highestfirst),and HTTPstatisticsaresortedby "Unsuccessfulrequests" (highest first).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 28 +[[image:Main.Images.Release Blog.WebHome@release-220-mapped-entity.png]] 29 29 30 +//__SSL settings__// 31 +Changes can now be deployed on SSL level without creating a new version of a flow in Create. 32 + 30 30 == **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. 31 31 32 -//__Gain the ability again to configure certificates in Deploy Architecture again__// 33 -In restricting the configuration options on the certificate level in one of our latter releases, it became impossible for normal users to add and edit certificates within Deploy Architecture. To resolve this problem we have now released a fix to resolve this issue, giving people the ability again to add and edit certificates under Deploy Architecture. 37 +[[image:Main.Images.Release Blog.WebHome@release-220-edit-annotation.png]] 34 34 35 -//__ Ensure that differing containerconfigurationsdeploy the correct configuration__//36 - Whenyou runin a multi-runtimeconfiguration and changethe actualflowsthat need torun on containerA vs. container B, it happenedbeforethat allflows werestill being deployed onall runtimes.Withthisrelease,wewill feedthis informationcorrectly toourinfrastructureto ensurethecorrectand configuredflowsare deployed on the proper containers.39 +//__Filter rejection warnings__// 40 +A discard channel is required for filter components when “Throw exception on rejection” value is set to false. 37 37 38 -//__Remove queurying options in Manage__// 39 -To avoid errors and loading problems when analyzing your statistics in Manage, we have removed the option to select a default time range spanning more than seven days. This is to guarantee the stability of the solution and to avoid users getting unnecessary errors. 42 +[[image:Main.Images.Release Blog.WebHome@release-220-discard-channel.png]] 40 40 44 +//__Manage Explore__// 45 +An issue has been fixed where navigating to the Explore tab in Manage would sometimes redirect users to the homepage. 46 + 41 41 == **Fancy Forum Answers** == 42 42 43 43 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: 44 44 45 -* [[Getting files from subfolders (FTP)>>https://my.emagiz.com/p/question/172825635703568575||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"]] 46 46 47 -== **Key takeaways** ==55 +== **Key Takeaways** == 48 48 49 49 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: 50 50 ... ... @@ -52,10 +52,9 @@ 52 52 * If you have feedback or ideas for us, talk to the Platypus 53 53 * Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these. 54 54 * Clear your browser cache (Ctrl + Shift + Del) 55 -* Check out the release notes [here] 63 +* Check out the release notes [[here>>doc:Main.Release Information.Portal.219 - Creation Carousel.WebHome||target="blank"]] 56 56 * Start thinking about how the license tracker can aid your development 57 57 * Start thinking about major, minor, and patch 58 -* Upgrade to the latest build number 59 59 * Keep making great integrations 60 60 61 61 Let's stay in touch and till next time! ... ... @@ -63,6 +63,11 @@ 63 63 {{info}} 64 64 ~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]] 65 65 66 -~*~* Indicates a next-generation-architecture only feature. 67 -{{/info}})))((({{toc/}}))){{/container}} 73 +{{/info}} 74 +))) 75 + 76 +((( 77 +{{toc/}} 78 +))) 68 68 {{/container}} 80 +{{/container}}