What’s new in Axway Flow Manager | February 2024

If you are new to Flow Manager, learn Flow Manager basics at Axway University:
university.axway.com/learn/le...
This release does not impact current configurations.
For detailed release notes and installation instructions go to:
docs.axway.com/bundle/FlowMan...
In this video:
0:40 Important fixes and updates
1:20 Filter using tags
1:41 Set common and specific properties for Transfer CFTs in subscriptions
7:36 Set the subscription name to the same name as the flow
Explore Flow Manager:
www.axway.com/en/products/man...
#mft #flowmanager #whatsnew
Hi, my name is Miila. Let's dive into what's new in this release. This version is compatible with earlier releases and can be installed on top of existing flow manager instances. Note that flow manager requires a database to store the flow repository. If you are using MongoDB, check that the version is 4.4 or 5.0, especially before performing an update.
Let's quickly go through the most important fixes and updates in this release. We've added support for Sul SSO IDP OCTA by adding a new parameter FM IDP entity format. The FM core private key parameter now accepts the dot bam format with an encrypted private key, fixing issues with the secure transport plugin in RPM so that it can connect to the bridge even when they are in different networks.
These are the most important fixes addressed in this release. You can find a complete list of fixes and product enhancements in the release notes that can be found in the description below. Search by tags in various flow manager pages. The advanced search has been extended to also include performing searches by tags page, which did not have advanced search before, like applications, application groups, partners, custom attributes, and domains.
They have been improved to also have this functionality. Another new feature delivered this month is common properties for multiple application sources or application targets, and subscriptions created from advanced patterns with this new flow manager version. Subscriptions from advanced patterns now allow you to set common properties for all CFs and only optionally set some specific properties for a given subset of transfer CFs.
In case the sources or targets are CF applications in previous versions, in the flow manager user interface, all properties were specific previously. The user interface aided in copying the previous properties for newly added sources or targets, but you had no way to edit all properties for all sources from one screen.
Creation: Weert and fill in the mandatory fields. And when you reach the last step, enter a name for your template here. You have a new section called "subscription," which has this option for subscription name. You can click on the functions button and select from here flow name with this expression. The subscription name will be calculated to have the same name as the flow name. Browse down a bit and see if you need to enable subscription approval or not. Also, check the flow name expression. For this case, it has the default value so that the flow name will have a calculated name using the subscription participant name. Save your template, publish your template, and now you're ready to subscribe. As you can see now in the subscription form, the name of this subscription has this expression which is not editable. Fill in the mandatory fields, deploy your subscription, and as you can see, the subscription name has the same name as the flow. For the second example, I'm going to use the previous template and only change the expressions used in calculating the flow name and the subscription name. So, for the second example, I will change this expression so that the flow name in this situation will be the subscription name. So, the first option, and also I will change the subscription name to be calculated using the date to save the template, publish the template, and now you're ready to subscribe. As you can see in this case, as well, the subscription name is no longer the flow name; it used the expression I entered earlier. And the flow name has, in this situation, the same name as the subscription. Thanks for watching. Find more information and resources.
Deploy since this subscription is deployed successfully, we can go ahead and check whatever got deployed on the transfer CFTs. For example, we can first check the customized transfer CFT, which was CFT uh 310 Docker. In the flows definition folder monitoring section, with the IDF demo, as well as with the scan new deer that I entered, customized. Now, we can go ahead and check the send templates for IDF demo. And for the processing section, we have the new script. Now, we can go ahead and check one of the CFTs that were not customized.