Changes for page 207 - Aligned State

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

From 148.1 to 147.1 From 178.1 to 177.1

From version 177.1

edited by Carlijn Kokkeler
on 2023/10/12 12:58

Change comment: There is no comment for this version

To version 148.1

edited by Erik Bakker
on 2023/08/15 13:54

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 @@
--206 - Situational Deployment
++203 - Fast Paced

Author

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

Content

@@ -2,118 +2,43 @@
  {{container layoutStyle="columns"}}(((
  [[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]]
--**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.
++**Hi there, eMagiz developers!** We have processed some early feedback on the release properties in the last few weeks. On top of that, we have improved the scalability of our complete solution and solved various smaller feedback items.
--== **Release Date Change** ==
--As of release 208, released on November 9th, 2023, we will change our release date to Thursday morning starting at 05:00 AM. 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]].
++== **Release Properties - Early Feedback** ==
++The community well received the release property functionality. However, there was still room for improvement based on some of the early feedback from the community. Some of these early feedback items have been addressed in this release. As a result, we have updated the layout of a property's edit screen and our checks on nested properties to avoid missing properties.
--== **Deployment Plan** ==
--
--//__Improved deployment plan to make the process better and more predictable__//
--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.
--
--//__Editing release properties__//
--With this release, it will be possible to change the description of a property by editing the property.
--
--//__Container memory settings__//
--A change in memory settings triggers redeployment of the container now.
--
--//__Properties tab__//
--We have removed the deprecated tab Properties in the Deploy phase.
--
--//__Cleanup old images__//
--When a release is removed, the related unused images in the on-premises machines will be removed as well.
--
--//__Performance improvements for loading releases__//
--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.
--
--== **Store Improvements** ==
--
--//__Message definition elements order__//
--We fixed an issue that the order of message definition elements was changed after being imported.
--
--//__Importing a store item with synchronous message definitions__//
--We fixed an issue that importing a store item with synchronous message definitions went wrong. Now, the imported message definitions should correspond with the exported message definitions.
--
--//__Importing store items containing static copies__//
--We fixed an issue that store items were missing static copies. Now, store items with static copies are imported correctly.
--
--//__Importing Store content__//
--We fixed an issue that blocked you from importing Store content in the Design phase. The message definitions and message mappings are now imported correctly as the original content in the item of the Store.
--
--//__Store disclaimer__//
--Users who are not the model owner no longer see the eMagiz Store disclaimer popup, instead they see a popup containing a message that states that the model owner should accept the disclaimer.
--
  == **Feedback Items** ==
--//__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.
++//__"All entries" are now cleaned up as part of the migration__//
++To avoid problems when removing integrations after migrating toward the next-generation architecture, we now clean up the "all-entries" as part of the migration towards the next-generation architecture.
--//__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).
++//__Trigger ID added to our alerting on the next-generation architecture__//
++We added a unique trigger ID to each alert configuration to make the interpretation for our support desk much easier and more manageable.
--//__UTC times in Grafana panels__//
--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.
++//__Improved performance Manage Dashboards__//
++We have improved the efficiency with which we retrieve the data that is shown in the Manage Dashboards for the next-generation architecture.
--//__Update flow designer version__//
--The framework used in the flow designer has been updated to the latest version.
--
--//__Carwash track TLS versions in logging__//
--A new logging feature will be released, enabling us to make better choices in deprecating old encryption standards.
--
--//__Moving channels in the flow designer__//
--Moving already attached channels in the flow designer has been made sligthly easier.
--
--//__Topic sizes description change__//
--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.
--
--//__Password change notification__//
--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.
--
--//__Password comparison__//
--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.
--
--//__Inactive user alerting__//
--Inactivated users are now removed from all alert settings (included “disabled“ settings) to avoid undesirable notifications.
--
--//__Alphabetical sorting on user level in HTTP statistics__//
--Variables in the 3rd generation runtimes HTTP statistics detail pages are now sorted case insensitive.
--
--//__SOAP Web services path__//
--Developers with Admin rights are now able to edit the 'SOAP Web services path' in the SSL settings.
--
  == **Bug Fixes** ==
--//__Flow designer styling__//
--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.
++//__Ensure no flow can be in a release twice__//
++We have fixed a bug that could cause one flow to end up in the same release with two different flow versions. As this will break your solution on various occasions, we fixed this.
--//__Partial search for messages__//
--It is now possible to search on messages partially in Manage Monitoring. For example, a search for Uptime can be done by searching for "up" "time" "ptim".
++//__Sped up adding a new operation to the API Gateway solution__//
++We have fixed a bug that slowed down the addition of new operations to the API Gateway solution.
--//__Disk usage after cloud template update__//
--In the last cloud template update there was an issue with disk performance. This has been resolved in this release. You can manually upgrade your cloud template, or rely on automatic updates.
--
--//__Error handling migration__//
--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.
--
  == **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:
--* [[JSON Web Tokens (JWT authentication)>>https://my.emagiz.com/p/question/172825635703606919||target="blank"]]
--* [[Determining container sizes & reading architecture pages>>https://my.emagiz.com/p/question/172825635703594204||target="blank"]]
--* [[SFTP connectivity - supported algorithms>>https://my.emagiz.com/p/question/172825635703607141||target="blank"]]
--* [[Deploy property release results in missing flows in runtime>>https://my.emagiz.com/p/question/172825635703607354||target="blank"]]
--* [[MessageDeliveryException: Dispatcher has no subscribers>>https://my.emagiz.com/p/question/172825635703619797||target="blank"]]
++* [[Issue with mail server dropping messages>>https://my.emagiz.com/p/question/172825635703530232||target="blank"]]
--
  == **Key takeaways** ==
--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:
++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:
  * 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

Changes for page 207 - Aligned State

Summary

Details

Navigation