Integration


This is an IBM Automation portal for Integration products. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (https://ideas.ibm.com).


Shape the future of IBM!

We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:

Search existing ideas

Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updates on them if they matter to you. If you can't find what you are looking for,

Post your ideas

  1. Post an idea.

  2. Get feedback from the IBM team and other customers to refine your idea.

  3. Follow the idea through the IBM Ideas process.


Specific links you will want to bookmark for future use

Welcome to the IBM Ideas Portal (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.

ideasibm@us.ibm.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.


Add a new idea Subscribe
Status Submitted
Workspace webMethods Managed File Transfer
Categories On-Prem
Created by Guest
Created on Sep 18, 2026

RELATED IDEAS

Additional options for an MFT build

1. Allow declaring variables in WmMFT/config/properties.cnf and to be referenced in MFT assets and Scheduled Actions for environment-specific configuration. This helps to keep the code generic and avoid editing the configuration in multi-node higher environments like UAT and specifically PROD.

2. Allow more tasks to be added under Error task configuration, to create a series of tasks to be executed like a catch block, when the flow faces a fatal failure and the flow reaches the error task.

3. Allow jump condition to be used for fatal errors also. Eg. In case node 1 is unavailable or path is invalid, the flow shouldn't default to the error task. Instead, we should be able to use a jump task, in case of mentioned errors, to check for similar files in node 2. If a jump step is present with condition checking for a fatal error, then the jump task should be executed and let the flow continue. If no jump task is found to be configured for a fatal error, then the flow can proceed to execute the error task(s). 

Idea priority Low

By clicking the "Post Comment" or "Submit Idea" button, you are agreeing to the IBM Ideas Portal Terms of Use.
Do not place IBM confidential, company confidential, or personal information into any field.