Skip to Content

Changes for page 237 - Fabulous Flow

Last modified by Erik Bakker on 2025/01/31 11:52
From version 76.2
edited by Erik Bakker
on 2023/05/09 13:47
Change comment: Update document after refactoring.
To version 122.1
edited by Carlijn Kokkeler
on 2023/10/12 12:18
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -197 - Pay Attention
1 +206 - Situational Deployment
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.ebakker
1 +XWiki.CarlijnKokkeler
Content
... ... @@ -1,35 +1,45 @@
1 -Here is our first release of this quarter. We have delivered additional minor (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 enhancements in working in 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: Till now, Flow Testing allowed to test eMagiz flows by defining a testing point on the start (and end) point(s), running them, and comparing the actual and expected messages. In this release, "Live Mode Testing" is introduced, making testing communication with an actual "live" endpoint possible. As a result, an "HTTP outbound gateway" can be set in "Live Mode." When you do this, the HTTP outbound gateway will send its request to the endpoint. Consequently, the response will be handled by the flow in the flow test so you can determine whether the actual endpoint behaves as expected.
8 -
9 9  =====Minor changes=====
10 10  
11 -* Design - Store: You can encounter a warning message when you import a transformation from the store because your imported transformation requires information from the related store fragment. To avoid a non-functional transformation in the Create phase, you should include that store fragment. Afterward, we will update your default flow component transformer to make it work correctly.
12 -* Design - Store: We updated importing to help you avoid an error while importing store items that will break your message definition in some cases.
13 -* Design - Store: We fixed an issue that you import the message definition(s), and a specialized DataType of imported message definition(s) is not matched with the exported message definition(s). Now, they are matched, and your transformation won't get issues.
14 -* Create - Store: We automatically excluded resources that are not good enough from the exporting wizard. Then you will find it easy to recognize a problem and avoid creating unusable store items.
15 -* Create - Flow designer: CDM edit right is applied to the message definition in Create phase. You can only change the CDM message definition, Gateway message definition, or even Event streaming message definition with the proper rights. (#690)
16 -* Create - Flow designer: Model resources tab removed on the resources page when adding a resource to a validating filter. (#921)
17 -* Create - Flow designer: Improve the responsiveness of the resources tab on the right panel.
18 -* Create - Flow Designer: Resources in the "Unused resources" section can be marked as used when components refer to the resources through property placeholders or in custom SPeL expressions.
19 -* Create - API Gateway: We fixed an issue where an optional query parameter would cause failed requests if that parameter was not supplied, so please reset your entry flow to apply the fix.
20 -* 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.
21 -* Create - Resources: When viewing a resource, its full name will be shown, removing the need to download the resource to obtain its name. (#922)
22 -* 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.
23 -* Deploy - Releases: We have improved editing properties in releases for runtimes that are 3rd generation compatible.
24 -* Deploy - Architecture: The topics are now ordered alphabetically, and the runtimes will now get the same order as design architecture (after 'apply to environment') (#543)
25 -* Deploy - Architecture: We improved the auto-healing feature of AWS machines. The new generation JMS server runtimes always start before other runtimes are run.
26 -* Manage - Explore: A new queue delete button is added. This button is only visible to authorized personnel.
27 -* Administration -User management: Company contact can edit permissions of models that fall under child companies. (#895)
28 -* Administration - Overview: Contracts page removed. (#907)
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 title of the 'apply to environment' action for changing 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 better explain what you need them for and mention essential security considerations.
33 -* Create - Flow designer: Various minor (cosmetic) fixes and changes in the edit pages of some flow components to make them more consistent with similar pages.
34 -* Deploy - Releases: We fixed an issue where after removing containers from a machine, during the execution of the deployment plan, the removed containers are not recognized as change, causing the 'Deploy machine' step to be skipped. (#514)
35 -* Manage/Event streaming statistics. For some models, (some) topic data did not show in the graphs. (#940)
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".
40 +
41 +
42 +
43 +=====Infra and image changes=====
44 +
45 +* Infra: New logging feature enabling us to make better choices in deprecating old encryption standards.