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.
Thank you for your input and for raising this request on behalf of Hanon, a valued client whose feedback we greatly appreciate.
After careful evaluation, we have decided not to move forward with this request at this time, based on the following considerations:
1. Technical and architectural limitations
The SAT code list resides in the legacy Inflight system and was designed strictly for internal flow routing. Unlike other configuration elements exposed in Config Hub, the SAT code list was not built for external consumption, and enabling access would require significant architectural changes to legacy systems.
2. Security and governance concerns
Exposing internal flow-routing logic introduces potential security and governance risks. A detailed risk review and cross-team coordination would be necessary before any such exposure, which is not justified at this point given the nature of the request.
3. Limited value across the broader user base
While we recognize the onboarding delays reported by Hanon, the usage of SAT code lists is typically static after initial setup and does not represent a frequent operational need. As such, the impact of enabling view access appears limited beyond this specific use case.
4. Risk of user confusion
We are currently consolidating client-facing configurations within Config Hub to simplify the user experience. Introducing SAT code list access through a different path could introduce confusion about where configurations should be created and maintained.
5. Current delivery priorities
At this stage, our engineering capacity is fully committed to delivering other high-priority, roadmap-aligned features that serve a broader client base. As such, this request cannot be accommodated without impacting those committed deliverables.
We remain committed to supporting Hanon and continuously improving the onboarding experience. Should similar requests surface from other clients, we will be open to revisiting this position in the future.
Thank you for your request for enhancement that you submitted. We appreciate your feedback and the opportunity to improve our product/service.
Currently RFE is under review. Could you please add the use cases and support tickets which will help us to take forward.
please don’t hesitate to reach out to us. We are committed to providing the best possible experience for our customers, and we value your feedback.
Thank you again for your request, and we look forward to continuing to serve you.”