Release Notes Version 2025.1
Version 2025.1 Major Release - March 18, 2025
Enhancements
MFT-2436 — The Trading Partner grid has been improved with the addition of a username column, and it now supports searching by the Server field.
MFT-2628 — Additional debugging options related to MFT server log files has been added to the existing
Settings > MANAGER SERVICE > Logs > Debug
module. This lets Redwood Technical Support enable the creation of log files that are not rotated, ensuring any relevant troubleshooting information is not overwritten.
MFT-2762 — The HTTP Request Trigger Action now supports the OAuth 2.0 authentication type.
MFT-2954 — JSCAPE SaaS default server log file size has been increased from 10MB to 100MB. When the maximum file size is reached, the log files are rotated as usual.
MFT-3265 — When Trigger debugging is enabled, more verbose Trigger information is appended to the MFT Server log file.
MFT-3384 — The ForEach Trigger Action now supports the ability to continue looping when an Action within the loop fails. A new checkbox named
Continue on Error
enables this option.
MFT-3415 — Some examples using the Rename File Trigger Action with the ReplaceFirst function were added to the documentation. The examples demonstrate how to rename files dynamically.
MFT-3485 — You can now bypass bucket name validation when using an S3 Compatible Trading Partner in certain Trigger Actions. A new checkbox named
Ignore Bucket Name Validation
enables this option.
MFT-3809 — Added support for additional SFTP ciphers and MACs.
Ciphers:
aes128-gcm@openssh.com
aes256-gcm@openssh.com
MACS:
hmac-sha2-256-etm@openssh.com
hmac-sha2-512-etm@openssh.com
Corrections
MFT-3269 — Removed
Settings > MISCELLANEOUS > Web > Web > Web Server > HTTPS on host
field in a SaaS environment since enabling it causes unintended behavior.
MFT-3601 — Under certain circumstances, a loss of data can occur in the SECURITY > IP Access list (allow/deny connections based on IP address).
MFT-3379 — Using JSCAPE SaaS, Trading Partner connections intermittently fail when the tenant's DNS Alias resolves to an inactive IP in Amazon's dual availability zones.