Changes for page 213 - Joyful Journeys
Last modified by Carlijn Kokkeler on 2024/04/18 13:07
From version 180.1
edited by Carlijn Kokkeler
on 2023/10/12 14:08
on 2023/10/12 14:08
Change comment:
There is no comment for this version
To version 362.1
edited by Carlijn Kokkeler
on 2024/01/29 14:49
on 2024/01/29 14:49
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,114 +1,88 @@ 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 th e lastfew weeks, we have done much work for theDeploy phase. On top of that,we have worked onseveralstore functionalities. Next to this, we haveseveral smaller feedback items from ourhackathon effortsthat arenow releasedto you.6 +**Hi there, eMagiz developers!** In this release, several improvements for pop-ups have been achieved. 6 6 7 -== **Release Date Change** == 8 -As of release 208, released on November 9th, 2023, we will change our release date to Thursday morning starting at 05:00 AM CET (3:00 UTC). We opted for this change as it allows us to control better and manage our releases to uphold the quality standards you have gotten used to from us. Should you have any questions, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]. 9 9 10 -== **Deployment Plan** == 9 +== **Pop-up Improvements** == 10 +//__Property releases__// 11 +When a new property release is created, this property release can now be viewed and deleted. 11 11 12 -//__Improved deployment plan to make the process better and more predictable__// 13 -The algorithm for generating a default deployment plan is improved to keep JMS downtime and alerting to a minimum. When stopping a machine, the JMS server is now stopped first, and when executing the deployment plan, the JMS server is deployed first. This way, the JMS server is troubled minimally. Next to this, the start/stop/restart machine deployment steps are now also executed correctly for AWS and on-premises machines. 13 +[[image:Main.Images.Release Blog.WebHome@release-blog-213-joyful-journeys-property-release.png]] 14 14 15 -//__ Editingrelease properties__//16 -With this release,itwillbepossibletochange thedescriptionofapropertybyeditingtheproperty.15 +//__Runtime deletion__// 16 +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. 17 17 18 -//__ Containermemorysettings__//19 - A changein memorysettings triggersredeploymentofthecontainer now.18 +//__Wiretap & debug error messages__// 19 +The error messages that may be displayed when using wiretaps and the debugger have been improved, these are now more user friendly. 20 20 21 -//__ Propertiestab__//22 - Wehave removedthedeprecatedtabProperties in theDeployphase.21 +//__Action messages__// 22 +The formatting of action messages regarding changes in retention bytes/hours has been improved. The action message will now display the correct, actual behaviour. 23 23 24 -//__Cleanup old images__// 25 -When a release is removed, the related unused images in the on-premises machines will be removed as well. 26 26 27 -//__Performance improvements for loading releases__// 28 -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. 25 +== **Formatting & Alignments** == 29 29 30 -== **Store Improvements** == 27 +//__Input fields__// 28 +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. 31 31 32 -//__ Messagedefinitionelementsorder__//33 - Wefixed anissuethat theorder ofmessagedefinition elementswaschangedafterbeingimported.30 +//__UI improvements__// 31 +UI improvements for static input components have been done and the tooltip for optional/required toggles has been improved. 34 34 35 -//__ Importinga storetemwithsynchronousmessagedefinitions__//36 - We fixed anissue that importing a storeitemwith synchronous messagedefinitionswentwrong.Now,theimported messagedefinitions should correspond with theexported messagedefinitions.33 +//__Runtime overview image versions__// 34 +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. 37 37 38 -//__ Importing storeitemscontainingtaticcopies__//39 - We fixedanissue thatstore itemswere missingstaticcopies.Now,store items with staticcopiesare importedcorrectly.36 +//__Component changes reversion__// 37 +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. 40 40 41 -//__ Importingstore content__//42 - Wefixed an issuethatblockedyou from importingStorecontent in the Design phase. The message definitionsand message mappingsarenowimportedcorrectlyas theoriginalcontentin the itemoftheStore.39 +//__State generation statistics__// 40 +The state generation graphs will now show the correct number of cache hits and misses. 43 43 44 -//__ Storedisclaimer__//45 - Users who are not the modelowner nolongerseethe eMagiz Store disclaimer popup, instead they see apopupcontaininga messagethat statesthat themodelowner shouldacceptthedisclaimer.42 +//__Queue browser timestamps__// 43 +All timestamp formatting in the queue browser is now aligned to yyyy-MM-dd HH:mm:ss.SSS. 46 46 47 -== **Feedback Items** == 45 +//__Addition and deletion of internal recipients__// 46 +Internal recipients are now added and deleted correctly. Before, an internal recipient could be added and thereafter deleted automatically when refreshing the page. 48 48 49 -//__Alerting manual pause__// 50 -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. 51 51 52 -//__Ordering of graphs in Manage__// 53 -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). 49 +== **Feedback Items** == 54 54 55 -//__U TCtimesin Grafana panels__//56 - AllGrafana panelsnowshow UTC times,whicharenormallyused ineMagiz, insteadofcal(browser)timezones.This way, itiseasiertomatchgraphs withloggingeventsalerts.51 +//__Update flows__// 52 +In Create > Resources, a button "Update flows" has been added to update versions of all flows in which a resource is used. 57 57 58 -//__ Updateflowdesignerversion__//59 -The framework usedin theflowdesigner has beenupdated to thelatestversion.54 +//__Q&A forum search__// 55 +The option to search by pressing the Enter key has been added to the Q&A forum. 60 60 61 -//__ Carwash track TLS versions in logging__//62 - Anew logging featurewillbereleased,enablingus tomakebetterchoices indeprecating old encryptionstandards.57 +//__Memory settings__// 58 +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. 63 63 64 -//__ Moving channels intheflowdesigner__//65 - Movingalreadyattachedchannelsintheflowdesigner has beenmade sligthly easier.60 +//__Runtime validation__// 61 +Validation for runtimes that are moved from on premises to the cloud or vice versa has been improved. 66 66 67 -//__Topic sizes description change__// 68 -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. 69 69 70 -//__Password change notification__// 71 -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. 72 - 73 -//__Password comparison__// 74 -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. 75 - 76 -//__Inactive user alerting__// 77 -Inactivated users are now removed from all alert settings (included “disabled“ settings) to avoid undesirable notifications. 78 - 79 -//__Alphabetical sorting on user level in HTTP statistics__// 80 -Variables in the 3rd generation runtimes HTTP statistics detail pages are now sorted case insensitive. 81 - 82 -//__SOAP Web services path__// 83 -Developers with Admin rights are now able to edit the 'SOAP Web services path' in the SSL settings. 84 - 85 85 == **Bug Fixes** == 86 86 87 -//__ Flowdesignerstyling__//88 - Thestylingoftheflowdesigner'sleftcomponentpanelhasbeenestructured,solvingararebug which wouldbreakthestylingof certainfunctionalities.66 +//__Removal of onramp__// 67 +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). 89 89 90 -//__ Partialsearchfor messages__//91 - Itisnowpossibleto searchonmessagespartiallyinManageMonitoring.Forexample,a searchforUptimecanbedoneby searchingfor"up" "time" "ptim".69 +//__Runtime statistics details__// 70 +We fixed an issue where heap memory usage data was accumulating when zooming out in the runtime statistics details dashboards. 92 92 93 -//__D isk usageafter cloud templateupdate__//94 - Inthe last cloudtemplateupdate there was anissue with diskperformance.Thishasbeenresolvedin this release.You canmanuallyupgradeyourcloudtemplate,orrelyonautomaticupdates.72 +//__Deployment prechecks__// 73 +During deployments prechecks will be done on runtimes that still have to be deployed from deploy architecture. 95 95 96 -//__Error handling migration__// 97 -If there is no custom error handling, when migrating to Gen3, the error channel to “errorChannel” is only created for the first inbound in an entry flow. This has been fixed by adding a migration step, where we set the error channel of all inbounds in a flow to “errorChannel” if the custom error handling is set to false. 98 98 99 99 == **Fancy Forum Answers** == 100 100 101 101 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: 102 102 103 -* [[JSON Web Tokens (JWT authentication)>>https://my.emagiz.com/p/question/172825635703606919||target="blank"]] 104 -* [[Determining container sizes & reading architecture pages>>https://my.emagiz.com/p/question/172825635703594204||target="blank"]] 105 -* [[SFTP connectivity - supported algorithms>>https://my.emagiz.com/p/question/172825635703607141||target="blank"]] 106 -* [[Deploy property release results in missing flows in runtime>>https://my.emagiz.com/p/question/172825635703607354||target="blank"]] 107 -* [[MessageDeliveryException: Dispatcher has no subscribers>>https://my.emagiz.com/p/question/172825635703619797||target="blank"]] 80 +* [[What is the eMagiz control tower?>>https://my.emagiz.com/p/question/172825635703696612||target="blank"]] 81 +* [[Deleting connector without flows gives error>>https://my.emagiz.com/p/question/172825635703696657]] 82 +* [[How to use a flowtest with path properties>>https://my.emagiz.com/p/question/172825635703696835||target="blank"]] 108 108 84 +== **Key Takeaways** == 109 109 110 -== **Key takeaways** == 111 - 112 112 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: 113 113 114 114 * If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]] ... ... @@ -118,7 +118,6 @@ 118 118 * Check out the release notes [here] 119 119 * Start thinking about how the license tracker can aid your development 120 120 * Start thinking about major, minor, and patch 121 -* Upgrade to the latest build number 122 122 * Keep making great integrations 123 123 124 124 Let's stay in touch and till next time! ... ... @@ -126,6 +126,11 @@ 126 126 {{info}} 127 127 ~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]] 128 128 129 -~*~* Indicates a next-generation-architecture only feature. 130 -{{/info}})))((({{toc/}}))){{/container}} 102 +{{/info}} 103 +))) 104 + 105 +((( 106 +{{toc/}} 107 +))) 131 131 {{/container}} 109 +{{/container}}