Skip to Main Content
IBM Data and AI Ideas Portal for Customers

This portal is to open public enhancement requests against products and services offered by the IBM Data & AI organization. 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

Post 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

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.

IBM Employees should enter Ideas at

Status Not under consideration
Workspace IBM Safer Payments
Components Business
Created by Guest
Created on Oct 10, 2022

In Case Management, allow visibility of fired rules for only the mandator level they fired in.

Currently, in a Case all rules that fired will be shown in that case, even if another case class was raised by the same or other rules firing at the same time. Therefore, if there are sensitive rules from 1 department firing, these would be visible to another team in another department, even if they are in another workgroup, where another case class was raised. For example, fraud, compliance, and internal audit teams may all want their own separate rules, but do not want other teams to see when these rules fire. This applies in a vertical mandator structure, where it is possible to separate teams and visibility of cases and rules using standard mandator accesses and inheritance, separate working queues, case classes, etc. The data is shared, and passes through all mandator levels, allowing rules from different levels to fire. No issue if only 1 ruleset fires at 1 mandator level, and only 1 case class is raised. However, if rules from more than 1 mandator level fires (=more than 1 team's rules) causing more than 1 case class to be raised, then all fired rules appear in all raised cases for that incoming message. Of course, a branched mandator structure would solve this, but then requires non-shared data, so data duplication, not affordable in large systems of > 512GB RAM.
Needed By Quarter
  • Guest
    Oct 10, 2022

    One possible way to achieve the same thing might be to simply filter which rules are visible in the case using some kind of enforceable filter in the case view, that is set by an administrator, and cannot be change by a user.