This portal is to open public enhancement requests for IBM Sterling products and services. 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).
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:
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 an idea.
Get feedback from the IBM team and other customers to refine your idea.
Follow the idea through the IBM Ideas process.
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.
Dear Vikram,
Thank you for submitting this RFE and clearly articulating the onboarding challenge when creating SFTP connections on CH using AI and JSON upload. We appreciate you highlighting this from a practical automation and user‑experience perspective.
This request identifies a usability gap in the current bulk JSON upload capability, where users can create either inbound or outbound SFTP connections, but not both together in a single operation. In real‑world scenarios, SFTP integrations are typically bi‑directional, and requiring separate JSON uploads for inbound and outbound increases setup time, introduces duplication, and raises the risk of configuration inconsistencies.
Enabling bulk JSON upload to create both inbound and outbound directions in one request would streamline connection creation, improve automation workflows, and align better with how customers provision SFTP connections at scale using APIs and AI‑driven setup.
Questions
To properly evaluate scope and design implications, the PM should clarify:
JSON structure expectation
Should inbound and outbound definitions be part of a single combined JSON payload, or separate sections within the same upload?
Dependency handling
If one direction (inbound or outbound) fails validation, should the entire connection creation fail, or should partial creation be allowed?
Use‑case priority
Is the primary need initial connection creation, or also bulk updates to existing inbound/outbound connections?
Consistency and defaults
Are inbound and outbound expected to share common attributes (partner, authentication, certificates), or are there frequent cases where they differ?
Backward compatibility
Should the existing single‑direction JSON upload continue to work unchanged, with bi‑directional upload as an optional enhancement?
Scale
Approximately how many connections are typically created using this bulk upload approach?
These details will help ensure the enhancement is intuitive, safe, and compatible with existing automation patterns while reducing overall setup effort.
Thanks again for sharing this enhancement idea. Feedback like this helps us improve automation, reduce customer effort, and make configuration workflows more efficient at scale.
—
Manoj Panda
Senior Product Manager
IBM Sterling