Changes for page 206 - Situational Deployment
Last modified by Carlijn Kokkeler on 2024/04/18 13:11
From 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
To version 154.1
edited by Carlijn Kokkeler
on 2023/10/10 13:41
on 2023/10/10 13:41
Change comment:
There is no comment for this version
Summary
-
Page properties (1 modified, 0 added, 0 removed)
Details
- Page properties
-
- Content
-
... ... @@ -12,23 +12,12 @@ 12 12 //__Editing release properties__// 13 13 With this release, it will be possible to change the description of a property by editing the property. 14 14 15 -//__JMS memory setting check__// 16 -A change in memory settings triggers redeployment of the container now. 17 17 18 -//__Properties tab__// 19 -We have removed the deprecated tab Properties in the Deploy phase. 20 - 21 -//__Cleanup old images__// 22 -When a release is removed, the related unused images in the on-premises machines will be removed as well. 23 - 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. 26 - 16 + 17 + 27 27 == **Store Improvements** == 19 + 28 28 29 -//__Message definition elements order__// 30 -We fixed an issue that the orders of message definition’s elements were changed after imported. 31 - 32 32 == **Feedback Items** == 33 33 34 34 //__Alerting manual pause__// ... ... @@ -37,33 +37,18 @@ 37 37 //__Ordering of graphs in Manage__// 38 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 -//__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 -//__Update flow designer version__// 44 -The framework used in the flow designer has been updated to the latest version. 30 +== **Bug Fixes** == 45 45 46 -//__ Carwash trackTLSversions in logging__//47 - Anewloggingfeaturewillbe released, enablingus tomakebetterchoices indeprecating oldencryptionstandards.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. 48 48 49 -//__ Moving channelsin theflow designer__//50 - Movingalreadyattached channels in the flowdesigner hasbeenmadesligthly easier.35 +//__Ensure that differing container configurations deploy the correct configuration__// 36 +When you run in a multi-runtime configuration and change the actual flows that need to run on container A vs. container B, it happened before that all flows were still being deployed on all runtimes. With this release, we will feed this information correctly to our infrastructure to ensure the correct and configured flows are deployed on the proper containers. 51 51 52 -//__ Topic sizesdescriptionchange__//53 - Inthe changedescription(andHistory)when alteringthetopiczeofatopicthe newandoldvaluewere switchedaroundcreatingconfusion,thishasbeenresolved.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. 54 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 - 67 67 == **Fancy Forum Answers** == 68 68 69 69 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: