Changes for page 213 - Joyful Journeys
Last modified by Carlijn Kokkeler on 2024/04/18 13:07
From version 358.1
edited by Carlijn Kokkeler
on 2024/01/29 14:19
on 2024/01/29 14:19
Change comment:
There is no comment for this version
To version 160.1
edited by Carlijn Kokkeler
on 2023/10/11 09:25
on 2023/10/11 09:25
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,64 +1,76 @@ 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!** This release ....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 7 +== **Deployment Plan** == 8 8 9 -== **Feedback Items** == 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. 10 10 11 -//__ Propertyreleases__//12 -Wh ena new propertyrelease is created,this propertyrelease can nowbeviewedanddeleted.12 +//__Editing release properties__// 13 +With this release, it will be possible to change the description of a property by editing the property. 13 13 14 -[[image:Main.Images.Release Blog.WebHome@release-blog-213-joyful-journeys-property-release.png]] 15 +//__JMS memory setting check__// 16 +A change in memory settings triggers redeployment of the container now. 15 15 16 -//__ Runtimedeletion__//17 -W hendeletingaruntime,the error message thatis displayed is more descriptive. The error messageswillnowincludethenames of the flowsthat run on thecontainer.18 +//__Properties tab__// 19 +We have removed the deprecated tab Properties in the Deploy phase. 18 18 19 -//__ Updateflows__//20 - InCreate>Resources,a button"Updateflows"hasbeenaddedtoupdate versionsof all flows in whicharesourceisused.21 +//__Cleanup old images__// 22 +When a release is removed, the related unused images in the on-premises machines will be removed as well. 21 21 22 -//__ Input fields__//23 - Multipleinputfields have beenupdatedsuchthattheyexpand whenthe amountofcharactersexceedsthedefault size.Theseupdatesweredonetocaterto large expressions.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. 24 24 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. 27 +== **Store Improvements** == 27 27 28 -//__ Runtimevalidation__//29 - Validationfor runtimes thataremovedfromonpremises tothecloud or viceversahasbeenimproved.29 +//__Message definition elements order__// 30 +We fixed an issue that the orders of message definition’s elements were changed after imported. 30 30 31 -//__UI improvements__// 32 -UI improvements for static input components have been done and the tooltip for optional/required toggles has been improved. 32 +== **Feedback Items** == 33 33 34 -//__ Q&Aforum search__//35 - The option to searchby pressingtheEnterkey has been added to theQ&Aforum.34 +//__Alerting manual pause__// 35 +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. 36 36 37 -//__ Wiretap &debugerrormessages__//38 -The error mes sages that may bedisplayedwhenusingwiretaps andtheebuggerhavebeenimproved, thesearenow moreuserfriendly.37 +//__Ordering of graphs in Manage__// 38 +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). 39 39 40 -//__ Runtimeoverviewimageversions__//41 - Insightinto inventedandactualdeploymentshasbeen improved.Ifthe releaseversionnumberonruntimes isdifferentcompared withtherelease, this is shownintheruntimeoverview.40 +//__UTC times in Grafana panels__// 41 +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. 42 42 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. 43 +//__Update flow designer version__// 44 +The framework used in the flow designer has been updated to the latest version. 46 46 47 -//__ Removalofonramp__//48 - Wefixedanissue whereit was not possibletoremove thelastonramp linkedtoa splitted entry(thatwasll-entry before).46 +//__Carwash track TLS versions in logging__// 47 +A new logging feature will be released, enabling us to make better choices in deprecating old encryption standards. 49 49 50 -//__ Componentchangesreversion__//51 - In the flow designer a bugcould occurwherethe changes to a component wouldbe revertediftheediting pop-upwouldbekept open forsome minuteswithout havingsavedthechangesyet. Thishasbeen fixed.49 +//__Moving channels in the flow designer__// 50 +Moving already attached channels in the flow designer has been made sligthly easier. 52 52 52 +//__Topic sizes description change__// 53 +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. 54 + 55 +//__Password change notification__// 56 +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. 57 + 58 +//__Password comparison__// 59 +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. 60 + 61 + 62 +== **Bug Fixes** == 63 + 64 +//__Flow designer styling__// 65 +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. 66 + 53 53 == **Fancy Forum Answers** == 54 54 55 55 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: 56 56 57 -* [[What is the eMagiz control tower?>>https://my.emagiz.com/p/question/172825635703696612||target="blank"]] 58 -* [[Deleting connector without flows gives error>>https://my.emagiz.com/p/question/172825635703696657]] 59 -* [[How to use a flowtest with path properties>>https://my.emagiz.com/p/question/172825635703696835||target="blank"]] 71 +* [[Getting files from subfolders (FTP)>>https://my.emagiz.com/p/question/172825635703568575||target="blank"]] 60 60 61 -== **Key Takeaways** ==73 +== **Key takeaways** == 62 62 63 63 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: 64 64 ... ... @@ -69,6 +69,7 @@ 69 69 * Check out the release notes [here] 70 70 * Start thinking about how the license tracker can aid your development 71 71 * Start thinking about major, minor, and patch 84 +* Upgrade to the latest build number 72 72 * Keep making great integrations 73 73 74 74 Let's stay in touch and till next time! ... ... @@ -76,11 +76,6 @@ 76 76 {{info}} 77 77 ~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]] 78 78 79 -{{/info}} 80 -))) 81 - 82 -((( 83 -{{toc/}} 84 -))) 92 +~*~* Indicates a next-generation-architecture only feature. 93 +{{/info}})))((({{toc/}}))){{/container}} 85 85 {{/container}} 86 -{{/container}}