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.

Created by Guest
Created on Dec 19, 2023

Hiding of unnecessary ROP/ROQ Methods

MRO provides a number of ROP/ROQ Methods that may not be applicable for a given client's environment.   These methods are usually included by default in their drop-down list for selection by users.  I'd like a method to either hide or remove methods that are either incompatible with the client set up or methods the client specifically would like not to be used.  Perhaps a setting that says which ROM's the client system is enabled for and based on that setting, a pre-defined list of methods can be used - then consultant can review the methods with client during implementation and either hide certain methods that the client does not want, but to begin with the list only contains "acceptable" methods for the ROM(s) used within the client system.

Idea priority Low
Needed By Not sure -- Just thought it was cool
  • Admin
    Dylan Jones
    Jan 24, 2024

    This can possibly be achieved by deleting out of the codes list/ autotask. We will look at creating a checkbox to hide or display the appropriate ROP/ROQ methods associated with customer ROM type

  • Admin
    Dylan Jones
    Jan 15, 2024

    This idea certainly makes sense and completing the work will allow simplification of the use of MRO IO. Will review with the team