Changes for page 213 - Joyful Journeys
Last modified by Carlijn Kokkeler on 2024/04/18 13:07
From version 161.1
edited by Carlijn Kokkeler
on 2023/10/11 09:30
on 2023/10/11 09:30
Change comment:
There is no comment for this version
To version 359.1
edited by Carlijn Kokkeler
on 2024/01/29 14:34
on 2024/01/29 14:34
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 06-SituationalDeployment1 +213 - Joyful Journeys - Content
-
... ... @@ -1,79 +1,79 @@ 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 releasedto you.6 +**Hi there, eMagiz developers!** This release .... 6 6 7 -== **Deployment Plan** == 8 8 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. 9 +== **Feedback Items** == 11 11 12 -//__ Editingreleaseproperties__//13 -W ith thisrelease,it will be possibletochange the descriptionof aproperty byeditingtheproperty.11 +//__Property releases__// 12 +When a new property release is created, this property release can now be viewed and deleted. 14 14 15 -//__JMS memory setting check__// 16 -A change in memory settings triggers redeployment of the container now. 14 +[[image:Main.Images.Release Blog.WebHome@release-blog-213-joyful-journeys-property-release.png]] 17 17 18 -//__ Propertiestab__//19 -We have removedthedeprecatedtabProperties in theDeployphase.16 +//__Runtime deletion__// 17 +When deleting a runtime, the error message that is displayed is more descriptive. The error messages will now include the names of the flows that run on the container. 20 20 21 -//__ Cleanupoldimages__//22 - Whenareleaseisremoved, therelatedunusedimagesinthe on-premisesmachineswillberemovedaswell.19 +//__Update flows__// 20 +In Create > Resources, a button "Update flows" has been added to update versions of all flows in which a resource is used. 23 23 24 -//__ Performance improvementsfor loading releases__//25 - Performanceimprovements have beenimplementedforloadingreleases inDeploy.Releasesshouldnowloadfaster thanbefore. All functionalityshould remainexactlythesameas before.22 +//__Input fields__// 23 +Multiple input fields 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. 26 26 27 -== **Store Improvements** == 25 +//__Memory settings__// 26 +It is now possible to change the memory settings of a container before pressing "Apply to environment". Before, it was only possible to view the memory settings if a container was running on AWS or running on a docker machine. 28 28 29 -//__ Message definition elementsorder__//30 - We fixedissue thatthe ordersofmessagedefinition’selementswerechangedaftertheywere imported.28 +//__Runtime validation__// 29 +Validation for runtimes that are moved from on premises to the cloud or vice versa has been improved. 31 31 32 -//__ Messagedefinitionelementsorder__//33 - Wefixed anissuethat importingastore itemwithsynchronousmessagedefinitions wentwrong.Now,the importedmessage definitions should correspondwith the exported messagedefinitions.31 +//__UI improvements__// 32 +UI improvements for static input components have been done and the tooltip for optional/required toggles has been improved. 34 34 35 -== **Feedback Items** == 34 +//__Q&A forum search__// 35 +The option to search by pressing the Enter key has been added to the Q&A forum. 36 36 37 -//__ Alerting manualpause__//38 - A fewreleaseso wechangedthe behavior of alertingin the deployment plan.Noweachtime when adeployment plan is executedthealerting will beautomaticallyre-enabledwhenthe deployercloses thedeploymentplan orclosestheweb browser.The majority of theusers are happy with thenewbehavior, but thereare someusecases that you do not want startthe alerting immediately. With this release, ifalerting has beenpausedmanually, this will not be activated automatically after a release deployment.37 +//__Wiretap & debug error messages__// 38 +The error messages that may be displayed when using wiretaps and the debugger have been improved, these are now more user friendly. 39 39 40 -//__ Orderingof graphsinManage__//41 - ThegraphsinManagearenow ordered accordingtoimportance. Thismeansthatruntimestatistics are sortedby"ProcessCPU usage" (highestfirst),queuestatisticsaresortedby "Messagesinqueue" (highestfirst),and HTTP statisticsaresortedby "Unsuccessfulrequests" (highestfirst).40 +//__Runtime overview image versions__// 41 +Insight into invented 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. 42 42 43 -//__UTC times in Grafana panels__// 44 -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. 43 +== **Bug Fixes** == 44 +//__Action messages__// 45 +The formatting of action messages regarding changes in retention bytes/hours has been improved. The action message will now display the correct, actual behaviour. 45 45 46 -//__ Updateflowdesigner version__//47 - The framework usedintheflowdesigner hasbeenupdated tothe latestversion.47 +//__Removal of onramp__// 48 +We fixed an issue where it was not possible to remove the last onramp linked to a splitted entry (that was an all-entry before). 48 48 49 -//__Ca rwashtrack TLSversions in logging__//50 - Anewloggingfeature willbe released,enabling ustomakebetterchoices indeprecatingold encryptionstandards.50 +//__Component changes reversion__// 51 +In the flow designer a bug could occur where the changes to a component would be reverted if the editing pop-up would be kept open for some minutes without having saved the changes yet. This has been fixed. 51 51 52 -//__ Moving channelsintheflowdesigner__//53 - Moving alreadyattachedchannelsintheflowdesignerhasbeenmadesligthlyeasier.53 +//__State generation statistics__// 54 +The state generation graphs will now show the correct number of cache hits and misses. 54 54 55 -//__ Topicsizes description change__//56 - In thechangeescription(andHistory)when alteringthetopicsizeofa topictheewandold valuewere switchedaround creating confusion,thishaseen resolved.56 +//__Runtime statistics details__// 57 +We fixed an issue where heap memory usage data was accumulating when zooming out in the runtime statistics details dashboards. 57 57 58 -//__ Password changenotification__//59 - Whenan accountpassword change requestismade, even when thisfails,amailis sentto theaccountownertoinform the ownerabout theaction.59 +//__Queue browser timestamps__// 60 +All timestamp formatting in the queue browser is now aligned to yyyy-MM-dd HH:mm:ss.SSS. 60 60 61 -//__ Password comparison__//62 - When changingapassword, itiscompared to a listof knowndatabasebreachesforsecurity.A warningisshown whenthe passwordcorrespondswithapasswordinthedatabase.62 +//__Deployment prechecks__// 63 +During deployments prechecks will be done on runtimes that still have to be deployed from deploy architecture. 63 63 65 +//__Addition and deletion of internal recipients__// 66 +Internal recipients are now added and deleted correctly. Before, an internal recipient could be added and thereafter deleted automatically when refreshing the page. 64 64 65 -== **Bug Fixes** == 66 - 67 -//__Flow designer styling__// 68 -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. 69 - 70 70 == **Fancy Forum Answers** == 71 71 72 72 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: 73 73 74 -* [[Getting files from subfolders (FTP)>>https://my.emagiz.com/p/question/172825635703568575||target="blank"]] 72 +* [[What is the eMagiz control tower?>>https://my.emagiz.com/p/question/172825635703696612||target="blank"]] 73 +* [[Deleting connector without flows gives error>>https://my.emagiz.com/p/question/172825635703696657]] 74 +* [[How to use a flowtest with path properties>>https://my.emagiz.com/p/question/172825635703696835||target="blank"]] 75 75 76 -== **Key takeaways** ==76 +== **Key Takeaways** == 77 77 78 78 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: 79 79 ... ... @@ -84,7 +84,6 @@ 84 84 * Check out the release notes [here] 85 85 * Start thinking about how the license tracker can aid your development 86 86 * Start thinking about major, minor, and patch 87 -* Upgrade to the latest build number 88 88 * Keep making great integrations 89 89 90 90 Let's stay in touch and till next time! ... ... @@ -92,6 +92,11 @@ 92 92 {{info}} 93 93 ~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]] 94 94 95 -~*~* Indicates a next-generation-architecture only feature. 96 -{{/info}})))((({{toc/}}))){{/container}} 94 +{{/info}} 95 +))) 96 + 97 +((( 98 +{{toc/}} 99 +))) 97 97 {{/container}} 101 +{{/container}}