Skip to Main Content
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 (

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 ( - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal ( - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM. - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.

Status Future consideration
Created by Guest
Created on Aug 26, 2019

Prevent Netmap Node deletion if node is referenced by a Functional Authority

When an admin retires a netmap node that is no longer needed, sometimes we end up with an orphaned Functional Authority (FA) referencing a now non-existent netmap node. To prevent this from occurring, a new functionality could be created where Connect:Direct(C:D)/Control Center checks if there are any FAs referencing the netmap node that is about to be deleted. If there is an FA referencing the netmap node about to be deleted, then a pop-up in Control Center would generate saying the node can't be deleted because it is currently referenced by an FA. If that can't be done, then let the job run and fail with a return code stating the netmap node can't be deleted because it is currently referenced by an FA.

The netmap and FA could be thought of as in a parent/child relationship. The parent can't be removed if there are any dependent children.

This new setup would be useful to prevent residual access definitions (such as FAs with no corresponding netmap entry). This could prevent potential audit findings, and also, it promotes cleaner configurations.

I am unsure if this RFE should be opened under Control Center or C:D.

What is your industry? Banking
How will this idea be used?

As a Connect:Direct admin, i need to retire a netmap node entry.  I need to ensure there are no dependent FAs associated with this node before deleting it and the this RFE would address this situation