Skip to Content

Changes for page 237 - Fabulous Flow

Last modified by Erik Bakker on 2025/01/31 11:52
From version 71.1
edited by Erik Bakker
on 2023/04/25 16:36
Change comment: There is no comment for this version
To version 123.1
edited by Carlijn Kokkeler
on 2023/10/12 12:26
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -196 - Last Post
1 +206 - Situational Deployment
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.ebakker
1 +XWiki.CarlijnKokkeler
Content
... ... @@ -1,38 +1,45 @@
1 -Here's our first release of this quarter. We have delivered additional small (bug) fixes in this release and released the Live Flow testing feature. The last is a real improvement during the development process of a flow. Furthermore, you will find several improvements in the way of work for nextGen environments.
1 +In the last sprint cycle, we focused on improving our deployment plan. On top of that, we made several improvements to the store.
2 2  
3 -Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.196 - The Last Post.WebHome||target= "blank"]].
3 +Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.206 - Situational Deployment.WebHome||target="blank"]].
4 4  
5 -=====New features=====
6 6  
7 -* Create - Flow Testing: so far, the Flow Testing allows test eMagiz flows by defining the testing point on the starts and the end points and comparing the actual and expected messages. In this release, “Live Mode Testing” is introduced, making it possible to test communication with real endpoint. That means that an “http output gateway” can be marked in “Live Mode”, if so, the http output gateway will send its http request to the real endpoint and received the result so we can go further with testing.
8 -
9 9  =====Minor changes=====
10 10  
11 -* Deploy - Architecture: The topics are now ordered alphabetically and the runtimes will now get the same order as design architecture (after ‘apply to environment’)
12 -* Create - Flow designer: CDM edit right is applied to the message definition in Create phase. You can not change CDM message definition, Gateway message definition, even Event streaming message definition without the proper right.
13 -* Deploy - Architecture: We improved the auto-healing feature of AWS machines. The new generation JMS server runtimes always start before other runtimes are ran.
14 -* Administration-User management: Company contact can edit permissions of models that fall under child companies
15 -* Administration: Contracts page removed
16 -* Create-Flow designer: Model resources tab removed on resources page when adding an resource to a validating filter.
17 -* Deploy - Releases: We reduced the time it takes to prepare a release, before it can be deployed. The process of building runtime images has been optimized.
18 -* Deploy - Releases: We have improved editing properties in releases for runtimes that are 3rd generation compatible.
19 -* Design - Store: You are able to see some warning messages when you import a transformation from store. Because your imported transformation is required some information from the related store fragment. You should include that store fragment to avoid a breaking transformation in Create phase after importing. Afterward, we will update your existing flow component transformer to make it work correctly.
20 -* Design - Store: We updated importing to help you avoiding an error during importing store item that will break your message definition in some special cases.
21 -* Create - Store: We excluded automatically resources that are not good enough from the exporting wizard. Then you will easy to recognize a problem and avoid creating unusable store item.
22 -* Flow Designer: Resources in "Unused resources" section can be marked as used for the case that the resources are referred by components through property placeholders or in custom spel expressions.
23 -* Create - API Gateway: We fixed an issue where an optional query parameter would cause failed requests, if that parameter was not supplied. Please reset your entry flow to apply the fix.
24 -* Create - API Gateway: We fixed an issue where API-Key secured requests would fail with error code 500 instead of code 401, if no API-Key was supplied. Please reset your entry flow to apply the fix.
25 -* Design - Store: We fixed an issue that you import the message definition(s) and a specialized DataType of imported message definition(s) are not matched with the exported message definition(s). Now, they are matched and your transformation won't get issues.
26 -* Create-Resources: When viewing a resource, its full name will be shown, removing the need to download the resource in order to obtain its name
27 -* Create - Flow designer: Improve responsiveness of resources tab at right panel
28 -* Manage - Explore: New button to delete queue is added and only visible for Expert Service (Admin)
8 +* Design - Channels: Moving already attached channels in the flow designer has been made sligthly easier. (#845)
9 +* Create - SSL: Developers with Admin rights are now able to edit the 'SOAP Web services path' in the SSL settings.
10 +* Create - Framework: The framework used in the flow designer has been updated to the latest version.
11 +* Deploy - Architecture: The description users see when alerting the topic retention size has been changed to be less confusing.
12 +* Deploy - Deployment plan: The algorithm for genarating a default deployment plan is improved to keep jms downtime and alerting to a minimum. (#1009)
13 +* Deploy - Deployment plan: A change in the memory settings of a container triggers a redeployment of the container. (#993)
14 +* Deploy - Properties: We removed the deprecated tab Properties in the Deploy phase.
15 +* Deploy - Release properties: The description of a property can be changed by editing the property. (#1064)
16 +* Deploy - Release: The start/stop/restart machine deployment steps are now also executed correctly for AWS and on-premises machines.
17 +* Deploy - Release: When a release is removed, the related unused images in the on-premises machines will be removed as well.
18 +* Deploy - Release: Performance improvements have been implemented for loading releases in Deploy.
19 +* Manage - Alerting: If alerting has been paused manually, it will not be activated automatically after a release deployment. (#1024)
20 +* Manage - Alerting: Inactivated users should be removed from all alert settings (included “disabled“ settings) to avoid undesirable notifications.
21 +* Manage - Monitoring: Graphs showing problematic runtimes, queues and requests have been updated to be sorted by “Process CPU usage”, “Messages in queue” and “Unsuccessful requests” by default respectively for 3rd generation runtimes. (#1069)
22 +* Manage - Monitoring: The 3rd generation runtime dashboards have been changed to show data on UTC time zone by default. (#1070)
23 +* Manage - Monitoring: Variables in the 3rd generation runtimes HTTP statistics detail pages are now sorted case insensitive. (#1063)
24 +* Administration - My account: When an account password change request is made, even when this fails, a mail is sent to the account owner to inform on the action.
25 +* Administration - My account: When changing a password, it is compared to a list of known database breaches for security. A warning is shown when the password is found in a database.
29 29  
27 +
28 +
30 30  ====Bug fixes====
31 31  
32 -* Create - Flow designer: Improved help texts of various flow components related to key-/truststores and their usage. They now better explain what you need them for and mention important security considerations.
33 -* Create - Flow designer: Various small (cosmetic) fixes and changes in the edit pages of some flow components to make them more consistent with similar pages.
34 -* Manage/Event streaming statistics. For some models, (some) topic data did not show in the graphs.
35 -* Deploy - Releases: We fixed an issue, where after removing containers from a machine, during execution of the deployment plan, the removed containers are not recognized as change, causing the ‘Deploy machine’ step to be skipped.
31 +* Design - Store: 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.
32 +* Design - Store: We fixed an issue that the orders of message definition elements were changed after being imported.
33 +* Design - Store: We fixed an issue that importing a store item with synchronous message definitions went wrong. Now, the imported message definitions should be the same with the exported message definitions.
34 +* Design - Store: We fixed an issue that static copies were missing when importing store items. (#888)
35 +* Design - Store: Users who are not the model owner no longer see the eMagiz Store disclaimer popup, instead they see a popup containing a message. (#1027)
36 +* Create - Errors - We fixed an issue that, when migrating to Gen3, the error channel to “errorChannel” is only created for the first inbound in an entry flow.
37 +* Create - Styling: The styling of the left component panel has been restructured, solving a rare bug which would break the styling of certain functionalities.
38 +* Deploy - Cloud Template: An issue with disk performance in the last cloud template update has been resolved in this release. Please check out the cloud template [[release notes>>Main.Release Information.Cloud Templates||target="blank"]] for more information.
39 +* Manage - Monitoring: It is now possible to search on messages using partial search words in Manage Monitoring. For example, a search for Uptime can be done by searching for "up" "time" "ptim".
36 36  
37 -====Remarks====
38 38  
42 +
43 +=====Infra and image changes=====
44 +
45 +* Infra: New logging feature enabling us to make better choices in deprecating old encryption standards.