Changes for page 207 - Aligned State

Last modified by Carlijn Kokkeler on 2024/04/18 13:10

From 135.1 to 136.1 From 154.1 to 155.1

From version 136.1

edited by Erik Bakker
on 2023/08/01 14:12

Change comment: There is no comment for this version

To version 154.1

edited by Carlijn Kokkeler
on 2023/10/10 13:41

Change comment: There is no comment for this version

Raw
Rendered

Summary

Page properties (3 modified, 0 added, 0 removed)

Details

Page properties

Title

@@ -1,1 +1,1 @@
--202 - New Equilibrium
++206 - Situational Deployment

Author

@@ -1,1 +1,1 @@
--XWiki.ebakker
++XWiki.CarlijnKokkeler

Content

@@ -2,78 +2,55 @@
  {{container layoutStyle="columns"}}(((
  [[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]]
--**Hi there, eMagiz developers!** In the last few weeks, we have crossed our t's and dotted our i's on the release properties functionality that will impact the day to day life of every user working within the platform. The focus of the release blog will consequently also be on this subject. On top of that we have several additional smaller feedback item coming from our hackathon efforts that are now released to you.
++**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.
--== **Release Properties** ==
--As of this release, we will introduce a new way of handling properties for all our clients. This change intends to solidify the relationship between a release and a property value. Before, in the current generation architecture, timing of changing properties was crucial to avoid costly mistakes on Production. On top of that it was not always clear whether a property value was indeed updated as it was not linked to something that was deployed. These considerations let us to change the property management behavior not only on our next-generation architecture but also on our current generation architecture. Having said that, there are several key changes compared to the current way of managing your properties. Most notably among these are:
++== **Deployment Plan** ==
--* The current properties tab in Deploy will disappear. The new overview of the properties (and their values) can be found under the "Create phase release" in Deploy -> Releases
--* Property placeholders (i.e. the names of properties as given in Create) are now automatically created for you. This to avoid mistakes when filling them in.
--* When adding or editing a property you can *now* select multiple runtimes for which the property applies. This is mainly beneficial for those running in a double lane setup or having a distributed landscape of containers.
--* A, for most, new concept of a "property release" is introduced. With the help of this functionality you can easily change a property on Production without having to create a completely new release in Test and promote it to the Production environment.
++//__Improved deployment plan to make the process better and more predictable__//
++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.
--{{info}}For more information please check out the following microlearnings:
++//__Editing release properties__//
++With this release, it will be possible to change the description of a property by editing the property.
--* [[Property Management>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.crashcourse-platform-deploy-property-management-new.WebHome||target="blank"]]
--* [[Actualize properties - current generation architecture>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.crashcourse-platform-deploy-actualize-properties-new.WebHome||target="blank"]]
--* [[Actualize properties - next generation architecture>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.crashcourse-platform-deploy-actualize-properties-gen3-new.WebHome||target="blank"]]
--Should you have any questions in advance, please get in touch with us at [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]].
--{{/info}}
++
++
++== **Store Improvements** ==
++
--== ** Manage - Next generation graphs improvements ** ==
--As of this release, we will create a condensed view of your metrics when zooming out in the Manage phase graphs. This will significantly improve the performance of the manage graphs as we retrieve and show less fine-grained information when zooming out.
--
--[[image:Main.Images.Release Blog.WebHome@202-release-blog--manage-graphs-zoomed-out.png]]
--
  == **Feedback Items** ==
--//__Improved editability when testing in eMagiz wihout Edit rights in Create__//
--Without having edit rights in the Create phase you could already do a lot on the level of flow tests in eMagiz. However, there were some oversights we missed during the implementation. These have been fixed allowing those without edit rights to now also change the name and description of the test case.
++//__Alerting manual pause__//
++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.
--//__Improved auditability on Deploy Architecture__//
--To improve the audtiability on Deploy Architecture we now also log when someone with Admin rights changes specific functions on this level (i.e. Fixed IP).
++//__Ordering of graphs in Manage__//
++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).
--//__Test your own exported work__//
--We have now made it possible to test your own exported work to the Store before it gets approved. This will increase the quality of store items we have, and our partners, have on offer within the store.
--{{info}}In case the concept of the store is new for you please check out this [[Fundamental>>doc:Main.eMagiz Academy.Fundamentals.fundamental-emagiz-store.WebHome||target="blank"]]{{/info}}
--
--//__Improved Audit Trail on several places__//
--In several places in the portal, we have improved the audit trail to specify better who changed what at which point in time.
--
--//__Removed the erroneous alert on message mapping when having a passthrough API__//
--This release removes the erroneous alert people reported on "errors in message mapping" for a passthrough API.
--
  == **Bug Fixes** ==
--//__Avoid clicking on other components while deleting another__//
--To avoid unexpected behavior, we now ensure that nothing can be selected once you see the "deletion" pop-up when you want to remove something in the flow designer.
++//__Gain the ability again to configure certificates in Deploy Architecture again__//
++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.
--//__Improved validation feedback in migrating to the next-generation architecture__//
--We have improved the validation feedback when migrating to the next-generation architecture.
++//__Ensure that differing container configurations deploy the correct configuration__//
++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.
--//__Make sure that user credentials can be viewed with view rights__//
--This release makes sure that the user credentials in Deploy can be considered with view rights and not only when having edit rights.
++//__Remove queurying options in Manage__//
++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.
--//__Refresh behavior within the deployment plan is fixed__//
--This release changes the refresh behavior within the deployment plan to show, once more, the "to be installed" flows before the user presses Execute.
--
  == **Fancy Forum Answers** ==
  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:
--* [[Replacing Legacy eMagiz-Mendix Connector: Migration Plan>>https://my.emagiz.com/p/question/172825635703517317||target="blank"]]
--* [[Unknown character(s) does not create error message.>>https://my.emagiz.com/p/question/172825635703517488||target="blank"]]
--* [[Split gateway configuration for local GEN3 gateway>>https://my.emagiz.com/p/question/172825635703517580||target="blank"]]
++* [[Getting files from subfolders (FTP)>>https://my.emagiz.com/p/question/172825635703568575||target="blank"]]
  == **Key takeaways** ==
--Thanks to all that helped build and those who tested and gave feedback to improve the product. To end this post, here are some key takeaways for you:
++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:
  * If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
  * If you have feedback or ideas for us, talk to the Platypus
--* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
++* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
  * Clear your browser cache (Ctrl + Shift + Del)
  * Check out the release notes [here]
  * Start thinking about how the license tracker can aid your development
@@ -86,6 +86,6 @@
  {{info}}
  ~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
--~*~* Indicates a GEN3-only feature.
++~*~* Indicates a next-generation-architecture only feature.
  {{/info}})))((({{toc/}}))){{/container}}
  {{/container}}

Changes for page 207 - Aligned State

Summary

Details

Navigation