IBM Sterling Ideas

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:

Post your ideas

IBM is transforming its request for enhancement (RFE) process. The purpose of the transformation is to provide a more consistent experience for you to submit requests and to enable IBM product owners to respond to your requests more quickly. For more information click here.

Start by posting ideas and requests to enhance a product or service. Take a look at ideas others have posted and upvote them if they matter to you,
1. Post an idea
2. Upvote ideas that matter most to you
3. Get feedback from the IBM team to refine your idea

Help IBM prioritize your ideas and requests

The IBM team may need your help to refine the ideas so they may ask for more information or feedback. The offering manager team will then decide if they can begin working on your idea. If they can start during the next development cycle, they will put the idea on the priority list. Each team at IBM works on a different schedule, where some ideas can be implemented right away, others may be placed on a different schedule.

Receive notifications on the decision

Some ideas can be implemented at IBM, while others may not fit within the development plans for the product. In either case, the team will let you know as soon as possible. In some cases, we may be able to find alternatives for ideas which cannot be implemented in a reasonable time.

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.

  • Guest
  • Aug 26 2019
  • Future consideration
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

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.