IBM Sterling
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).
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
Post an idea.
Get feedback from the IBM team and other customers to refine your idea.
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.
Thank you for submitting this idea—this is a valuable enhancement aligned with improving customer self-service, testing agility, and operational efficiency.
Providing customers with the ability to enable or disable outbound Trading Partner (TP) flows directly—especially during CTE/testing phases—would significantly reduce dependency on IBM Support and speed up partner onboarding and validation cycles. Exposing this capability through a Trading Partner Relationship tab is a logical and intuitive placement.
We also appreciate the suggestion to add guardrails, such as warnings or disabled controls when a flow is generic or shared, to prevent unintended impact. This aligns well with our goals around safe self-service and controlled configuration ownership.
We will review this idea in the context of:
Customer-owned vs IBM-managed configurations
Risk of accidental disruption to shared/generic flows
Role-based access control and auditability
Alignment with Doc Tracking / Inflight 2.0 capabilities
Your input helps shape how we evolve toward a more customer-controlled operating model while maintaining platform stability.
Clarifying Questions
Scope of Control: Should customers be able to enable/disable flows only in non-production (CTE/Test) environments, or should this also be allowed in Production?
Granularity: Is the expectation to control flows at the Trading Partner level, document type level, or individual outbound flow level?
User Roles: Which customer roles should have permission to perform enable/disable actions (e.g., Admin only, Ops users)?
Audit & Visibility: Do you need an audit trail (who disabled/enabled, when, and why) visible in the UI?
Recovery Expectations: Should there be safeguards such as confirmation prompts, auto-revert options, or dependency warnings before disabling a flow?