Changes for page 212 - Failover Fiesta

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

From 167.1 to 168.1

From version 1.1

edited by eMagiz
on 2022/10/12 10:29

Change comment: There is no comment for this version

To version 167.1

edited by Carlijn Kokkeler
on 2023/10/11 13:32

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 @@
--185 - To determine
++206 - Situational Deployment

Author

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

Content

@@ -2,64 +2,107 @@
  {{container layoutStyle="columns"}}(((
  [[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]]
--**Hi there, eMagiz developers!** We have been hard at work bolstering our offering concerning the upcoming rollout of our new architecture stack. Next to that big development, we have finished our work on the Flow Designer which is the major part of this release. Please take a moment to read the below carefully and work with the new flow designer as soon as possible to familiarize yourself with this one.
++**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.
--==**Flow Designer V3**==
++== **Deployment Plan** ==
--The new Flow Designer used in Create is released! This is a significant improvement in our iPaaS Portal that implements feedback of our users and helps to improve the overall experience. After several iterations of internal validations and testing sessions with end-users, we are releasing this feature to all users. Below are some key notes that are important to know and to consider.
--
--=== **Improvements** ===
--The new Flow Designer implements an approach whereby components can be dragged into the canvas without any configuration setting changed. The right hand panel contains a new section called Alerts that helps users to remove all alerts from the flow created. Such as missing configurations, channels or mismatches. All of these alerts need to be resolved so that a valid flow can be pushed to Deploy.
++//__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.
--[[image:Main.Images.Release Blog.WebHome@184 - FlowDesigner releaseblog 1.png]]
++//__Editing release properties__//
++With this release, it will be possible to change the description of a property by editing the property.
--Furthermore, there is now a right hand panel to brings a few configuration more forward for users. In that panel you will find the following 4 tabs as described below. Furthermore, you can collapse the right hand panel to have more space to view/edit your flow.
--
--[[image:Main.Images.Release Blog.WebHome@184 - FlowDesigner releaseblog 2.png]]
--
--* **Alerts**
--In this section, all alerts are displayed organized by component. Alert text should be clear to understand the issue and the component can be opened from that same location.
++//__JMS memory setting check__//
++A change in memory settings triggers redeployment of the container now.
--* **Resources**
--In this section, all resources are displayed used by the flow. Resources can be added and deleted from this section, as well as download and viewed. Generated resources such as transformations and definition are also vieweable from here. Use the option Show generated resources to explore these.
--
--* **Support objects**
--The support objects are no longer stored on the canvas, but displayed as a list in this tab. The interaction to add new support objects is also moved to this tab. Support objects can be edited from this tab as well. Please note that the interaction with the main canvas remains - selecting a support object will highlight the components in the canvas to illustrate where that support object is used.
++//__Properties tab__//
++We have removed the deprecated tab Properties in the Deploy phase.
--* **Properties**
--The properties tab is also visible now and has been improved so that the values in Deploy can also be viewed. All values of all environments can be viewed - container level properties replicated are condensed into a single entry.
--
--=== **User interaction changes** ===
--There are some small changes to consider compared to the old flow designer. Please take a moment to read these:
--
--* Multiple select. This option is still available, but you have to click the shift button while drawing the rectangle that holds the objects to select
--* Live preview. When moving components around, a live preview of the flow is displayed so that alignment becomes easier
++//__Cleanup old images__//
++When a release is removed, the related unused images in the on-premises machines will be removed as well.
--
--== **Feedback items ** ==
++//__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.
--We have also solved other feedback items besides the key updates around functionality.
++== **Store Improvements** ==
--//__Set runtime field as first selected field on property level__//
--With this change, the runtime is the first field selected when copying a property. This way it is easier to select another runtime and propagate that property to that runtime as well.
++//__Message definition elements order__//
++We fixed an issue that the order of message definition elements was changed after being imported.
--[[image:Main.Images.Release Blog.WebHome@184 - FlowDesigner releaseblog 3.png]]
--
++//__Improting 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.
++
++== **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.
++
++//__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).
++
++//__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.
++
++//__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.
++
++//__Partial search for messages__//
++It is now possible to search on messages partially in Manage Monitoring. For example, search for Uptime can be done by searching for "up" "time" "ptim".
++
++//__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.
++
++//__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.
++
  == **Fancy Forum Answers** ==
--As always, a gentle reminder to all 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:
++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:
--* [[Excel Attachment in Mail to File>>https://my.emagiz.com/p/question/172825635703120756||target="blank"]]
--* [[Importing datapipeline store component Mendix to AWS Redshift failed>>https://my.emagiz.com/p/question/172825635703120551||target="blank"]]
++* [[JSON Web Tokens (JWT authentication)>>https://my.emagiz.com/p/question/172825635703606919||target="blank"]]
  == **Key takeaways** ==
--Thanks to all that help build, 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
@@ -66,13 +66,12 @@
  * Start thinking about major, minor, and patch
  * Upgrade to the latest build number
  * Keep making great integrations
--* Check out the new documentation portal.
  Let's stay in touch and till next time!
  {{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 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 212 - Failover Fiesta

Summary

Details

Navigation