Changes for page 213 - Joyful Journeys
Last modified by Carlijn Kokkeler on 2024/04/18 13:07
From version 360.1
edited by Carlijn Kokkeler
on 2024/01/29 14:41
on 2024/01/29 14:41
Change comment:
There is no comment for this version
To version 156.1
edited by Carlijn Kokkeler
on 2023/10/10 13:56
on 2023/10/10 13:56
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,81 +1,54 @@ 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 8 -== **Pop-up Improvements** == 9 -//__Property releases__// 10 -When a new property release is created, this property release can now be viewed and deleted. 7 +== **Deployment Plan** == 11 11 12 -[[image:Main.Images.Release Blog.WebHome@release-blog-213-joyful-journeys-property-release.png]] 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. 13 13 14 -//__ Runtimedeletion__//15 -W hen deleting a runtime, theerror messagethatisdisplayed ismoredescriptive.Theerror messages willnowinclude thenames oftheflowsthatrunon thecontainer.12 +//__Editing release properties__// 13 +With this release, it will be possible to change the description of a property by editing the property. 16 16 17 -//__ Wiretap& debug errormessages__//18 - The errormessagesthatmay be displayed whenusingwiretapsandthe debuggerhavebeenimproved,thesearenow moreuserfriendly.15 +//__JMS memory setting check__// 16 +A change in memory settings triggers redeployment of the container now. 19 19 20 -//__Action messages__// 21 -The formatting of action messages regarding changes in retention bytes/hours has been improved. The action message will now display the correct, actual behaviour. 18 +//__Properties tab__// 19 +We have removed the deprecated tab Properties in the Deploy phase. 20 + 21 +//__Cleanup old images__// 22 + 23 +== **Store Improvements** == 24 + 22 22 23 -== **User Journey** == 24 -//__Update flows__// 25 -In Create > Resources, a button "Update flows" has been added to update versions of all flows in which a resource is used. 26 +== **Feedback Items** == 26 26 27 -//__ Inputfields__//28 - Multiple inputfieldshavebeenupdatedsuchthatthey expand when the amount ofcharacters exceeds thedefaultsize.Theseupdateswere doneto catertorgeexpressions.28 +//__Alerting manual pause__// 29 +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. 29 29 30 -//__ UI improvements__//31 - UIimprovementsforstaticputcomponents havebeendone andthe tooltipfor optional/required toggleshas beenimproved.31 +//__Ordering of graphs in Manage__// 32 +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). 32 32 33 -//__ Q&Aforumsearch__//34 - Theoptionto searchby pressingtheEnterkeyhasbeen addedto theQ&Aforum.34 +//__UTC times in Grafana panels__// 35 +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. 35 35 36 -== **Feedback Items** == 37 +//__Update flow designer version__// 38 +The framework used in the flow designer has been updated to the latest version. 37 37 38 -//__Memory settings__// 39 -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. 40 40 41 -//__Runtime validation__// 42 -Validation for runtimes that are moved from on premises to the cloud or vice versa has been improved. 43 - 44 -//__Runtime overview image versions__// 45 -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. 46 - 41 + 47 47 == **Bug Fixes** == 48 48 49 -//__Removal of onramp__// 50 -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). 51 51 52 -//__Component changes reversion__// 53 -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. 54 - 55 -//__State generation statistics__// 56 -The state generation graphs will now show the correct number of cache hits and misses. 57 - 58 -//__Runtime statistics details__// 59 -We fixed an issue where heap memory usage data was accumulating when zooming out in the runtime statistics details dashboards. 60 - 61 -//__Queue browser timestamps__// 62 -All timestamp formatting in the queue browser is now aligned to yyyy-MM-dd HH:mm:ss.SSS. 63 - 64 -//__Deployment prechecks__// 65 -During deployments prechecks will be done on runtimes that still have to be deployed from deploy architecture. 66 - 67 -//__Addition and deletion of internal recipients__// 68 -Internal recipients are now added and deleted correctly. Before, an internal recipient could be added and thereafter deleted automatically when refreshing the page. 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 -* [[What is the eMagiz control tower?>>https://my.emagiz.com/p/question/172825635703696612||target="blank"]] 75 -* [[Deleting connector without flows gives error>>https://my.emagiz.com/p/question/172825635703696657]] 76 -* [[How to use a flowtest with path properties>>https://my.emagiz.com/p/question/172825635703696835||target="blank"]] 49 +* [[Getting files from subfolders (FTP)>>https://my.emagiz.com/p/question/172825635703568575||target="blank"]] 77 77 78 -== **Key Takeaways** ==51 +== **Key takeaways** == 79 79 80 80 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: 81 81 ... ... @@ -86,6 +86,7 @@ 86 86 * Check out the release notes [here] 87 87 * Start thinking about how the license tracker can aid your development 88 88 * Start thinking about major, minor, and patch 62 +* Upgrade to the latest build number 89 89 * Keep making great integrations 90 90 91 91 Let's stay in touch and till next time! ... ... @@ -93,11 +93,6 @@ 93 93 {{info}} 94 94 ~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]] 95 95 96 -{{/info}} 97 -))) 98 - 99 -((( 100 -{{toc/}} 101 -))) 70 +~*~* Indicates a next-generation-architecture only feature. 71 +{{/info}})))((({{toc/}}))){{/container}} 102 102 {{/container}} 103 -{{/container}}