Changes for page 206 - Situational Deployment

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

From 29.1 to 28.1 From 173.1 to 172.1

From version 172.1

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

Change comment: There is no comment for this version

To version 29.1

edited by Erik Bakker
on 2022/10/24 09:03

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
++186 - Daemon Switch

Author

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

Content

@@ -2,113 +2,137 @@
  {{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 hit the ground running in this quarter by not only focusing on larger features but also spend a substantial chunk of time on focusing with us all on a lot of smaller feedback items and bugs. All these items will be provided to you with this release. Among these are flow designer improvements, navigation improvements, and consistency improvements. On top of that, we have made our new monitoring stack available to a first set of models. So let us dive into all we have to offer this time!
--== **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]]
++== **New monitoring stack** ==
--== **Deployment Plan** ==
++This release will introduce a new monitoring stack that is available for models that run in the new runtime architecture of eMagiz. With the help of this monitoring stack we have redesigned various screens in Manage and restructured our alerting approach. For a sneak preview of what these changes entail please check out the following microlearnings.
--//__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.
++* [[Runtime Statistics>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.crashcourse-platform-manage-interpreting-runtime-statistics-gen3.WebHome||target="blank"]]
++* [[Alerting in eMagiz>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.crashcourse-platform-manage-alerting-gen3.WebHome||target="blank"]]
++* [[Queue Statistics>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Messaging.crashcourse-messaging-interpreting-queue-statistics-gen3.WebHome||target="blank"]]
++* [[HTTP Statistics>>doc:Main.eMagiz Academy.Microlearnings.Advanced Level.Advanced monitoring.HTTP Statistics.WebHome||target="blank"]]
--//__Editing release properties__//
--With this release, it will be possible to change the description of a property by editing the property.
++{{info}}Note that the new monitoring stack is only available for models that run the new runtime architecture. Should you wish to become an early adopter please contact us at productmanagement@emagiz.com to discuss the possibilities{{/info}}
--//__JMS memory setting check__//
--A change in memory settings triggers redeployment of the container now.
++== **Transformation Improvements** ==
--//__Properties tab__//
--We have removed the deprecated tab Properties in the Deploy phase.
++//__Toggle between Design and Create__//
++This release will introduce a toggle that allows you to quickly navigate between the Create Transformation and the Design Message Mapping. In both Create as Design, a new button is added on the transformation level that allows you to open the transformation in Design (or Create) depending on where you are currently. This should make navigating easier when you make a mistake or forget something in Design.
--//__Cleanup old images__//
--When a release is removed, the related unused images in the on-premises machines will be removed as well.
++//__Improved Transformation options for booleans__//
++On top of that, we will introduce additional functionality to transform "Boolean to enumeration," "enumeration to Boolean," and" Boolean to Boolean." Just as you are used to for the "enumeration to enumeration" transformation, you can now define a value mapping for each combination mentioned above. See below for an example of how this looks.
--//__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.
++[[image:Main.Images.Release Blog.WebHome@179-release-blog--transformation-options-boolean.png]]
--== **Store Improvements** ==
++== **Feedback items ** ==
--//__Message definition elements order__//
--We fixed an issue that the order of message definition elements was changed after being imported.
++Apart from the key updates around functionality, we have also solved other feedback items.
--//__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.
++//__Correctly define the size of a cloud slot when creating it for the first time__//
++Currently, eMagiz will look to Design when creating the cloud slot for the first time. This is to avoid you having to “create” your solution twice, as there were instances where eMagiz would always create the cloud slot with the smallest size available first, even if this were not what you wanted.
--//__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.
++//__Updated infographic Capture__//
++As of now, we have updated the infographic on the Capture phase to incorporate the new look and feel and explain the updated functionality in Capture.
--//__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.
++//__Updated error feedback in Design__//
++Before, you could see a transformation error in Design even though the transformation was not used in your solution (i.e., “data pipeline” functionality). However, when you now define a specific integration as a data pipeline solution, the error will not be shown.
--//__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.
++//__Improved styling of Topic Storage in Design Architecture__//
++When having a large number of topics in your environment, the topic storage overview in Design Architecture will now be improved as the horizontal scrollbar is gone.
--== **Feedback Items** ==
++//__Improved styling of error feedback on User Management in Deploy__//
++With this release we have improved the styling of the feedback pop-up you get in User management after pressing “Apply to environment” and several updates could not be executed.
--//__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.
++//__Show only the ten latest flow versions when selecting a flow version in a Release__//
++To improve the quality and speed of defining a release, we will show only the latest ten versions of a flow in the release widget, as these ten are most likely to be selected by a user. If you need an older version, you can add it via the “Details” option on the release.
--//__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).
++[[image:Main.Images.Release Blog.WebHome@179-release-blog--ten-latest-flow-versions-release.png]]
--//__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.
++//__Optional Client Secret when using the grant_type Password when calling an OAuth2.0 IDP__//
++Before, you needed to define the Client Secret even for the grant_type Password, where it is not always required. We have corrected this behavior to ensure that this is in line with the OAuth 2.0 specification.
--//__Update flow designer version__//
--The framework used in the flow designer has been updated to the latest version.
++//__Clear API Gateway System message__//
++With this release, we have added the Clear button that you already know from the messaging pattern to the API Gateway system message. This unifies the options between the two patterns in Design on the system message level.
--//__Carwash track TLS versions in logging__//
--A new logging feature will be released, enabling us to make better choices in deprecating old encryption standards.
++//__Additional information in Property History__//
++To improve the usability of the property history page in Deploy, we now also show the runtime on which a particular property is changed. This is particularly useful when changing the same property used on different runtimes.
--//__Moving channels in the flow designer__//
--Moving already attached channels in the flow designer has been made sligthly easier.
++//__Save Tag when ready__//
++With this release, we have made it explicit that when you want to change the name of a tag, you first need to press the “Save” button before the change is actualized within your model.
--//__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.
++//__View deployment step information when having view rights__//
++With this release, we have made it possible to view not only the deployment steps but also the detailed information of each deployment step when you only have view rights on a specific environment.
--//__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.
++//__Validating external recipients in notification settings__//
++Before pressing save, we will now validate what you entered in the external recipients setting to ensure that what is entered there are valid values.
--//__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.
++//__Automatically link enumeration list to attribute__//
++When you create an enumeration list relevant to a particular attribute, eMagiz will now automatically link the two together without you having to do this manually.
--//__Inactive user alerting__//
--Inactivated users are now removed from all alert settings (included “disabled“ settings) to avoid undesirable notifications.
++//__Approve and go to environment__//
++With this release, we will provide you with the option to approve a release to a specific environment and let eMagiz directly take you to that environment.
--//__Alphabetical sorting on user level in HTTP statistics__//
--Variables in the 3rd generation runtimes HTTP statistics detail pages are now sorted case insensitive.
++[[image:Main.Images.Release Blog.WebHome@179-release-blog--approve-and-go-to-environment.png]]
--//__SOAP Web services path__//
--Developers with Admin rights are now able to edit the 'SOAP Web services path' in the SSL settings.
++//__Remove irrelevant information on a runtime in Design Architecture__//
++We have removed all irrelevant information for a user when you enter the details view of a runtime in Design Architecture. The information that is still shown is visualized below.
++[[image:Main.Images.Release Blog.WebHome@179-release-blog--container-view.png]]
++
++//__Add question about message redelivery in Capture__//
++When you use the message redelivery functionality, and it is relevant to consider whether it will be helpful when sending data to the system, you will now see an additional question in Capture. This question should trigger a thinking process on handling message redelivery for that specific solution.
++
++//__Prevent pressing “Apply to environment” multiple times leading to conflicts__//
++With this release, we have improved this functionality to verify whether an update is currently being executed. If this is true, all other times, you push the button; you will be notified that the process is still running. This is done to avoid potential conflicts if a user presses the "Apply to environment" button more than once in a short period.
++
++//__Add “State” to the topic details in Deploy Architecture__//
++Based on your feedback, we have improved the topic details overview to include the “State” of a topic. Each topic can be “Unchanged,” “Changed,” “Deleted,” or “New.” Based on this state, you can determine which topics will be added, changed, deleted, or remain untouched.
++
++//__Improved stability of logging on the Gen3 Architecture__//
++With this release, we have improved the stability of the logging and made sure that the logging is correctly compacted internally.
++
  == **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.
++//__Various updates when importing store items in Design including a transformation__//
++With this release, we have made several improvements for importing store items in Design, including a transformation. This will further bolster our offering on 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".
++//__Opening flow testing widget in specific circumstances was not working__//
++With this release, we fixed an issue where you could not open the flow testing functionality in the Create phase when your flow contained a particular construction combined with the “nullChannel.”
--//__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.
++//__Improved styling when adding a large message to a flow test__//
++With this release, the styling of the pop-up will not change when you define a large message as input (or expected output) of your flow test. This will ensure that you can still easily specify the flow test message’s name and description after entering the large message.
--//__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.
++//__Errors on the UI do not keep following me__//
++Before, we had some issues: when you navigated away from the API Gateway statistics page, an error pop-up would keep following you throughout the platform. To resolve this issue, you needed to refresh the browser. We have fixed this issue permanently with this release, making the refresh obsolete.
++//__Navigating back to the transformation in Create works again__//
++With this release, we have squashed a bug that annoyed users. Before, it could happen that when you navigated away from the transformation page in your flow in Create and returned later, the transformation was not shown anymore. With this release, we have made sure that regardless of where you come from, the transformation will be visible for you to see.
++
++//__Remove the qualified name when editing a non-legacy Mendix entry in eMagiz__//
++With this release, we have removed the possibility of changing the obsolete qualified name when editing a non-legacy Mendix entry in eMagiz.
++
++//__Selecting tags when drawing a line in Capture__//
++We have now made this possible (again). This way, you can directly select the tag(s) you want instead of opening the detailed information on the line after it is already added to Capture.
++
++//__Remove invalid selection when configuring a cron trigger via the tooling__//
++With this release, we have removed invalid selection options presented to you when you used the configuration option on a property of type cron to let eMagiz define the cron trigger value. This is to avoid unwanted surprises when deploying your solution.
++
  == **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:
++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:
--* [[JSON Web Tokens (JWT authentication)>>https://my.emagiz.com/p/question/172825635703606919||target="blank"]]
++* [[Header 'X' with value '0' will not be set since it is not a String and no Converter is>>https://my.emagiz.com/p/question/172825635700363586||target="blank"]]
++* [[Kafka Consumer Mendix String Deserializer is not working>>https://my.emagiz.com/p/question/172825635700363585||target="blank"]]
++* [[Namespace prefix 'xs' has not been declared>>https://my.emagiz.com/p/question/172825635700363685||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 help build, 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 questions surrounding our Program Increment Planning, please get in touch with
  * 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
@@ -119,8 +119,8 @@
  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 next-generation-architecture only feature.
++~*~* Indicates a GEN3-only feature.
  {{/info}})))((({{toc/}}))){{/container}}
  {{/container}}

Changes for page 206 - Situational Deployment

Summary

Details

Navigation