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 Submitted
Workspace Cognos Analytics
Components Administration
Created by Guest
Created on Jan 15, 2024

Remove admin vulnerability on routing sets when non admin users copy data modules / packages / files

Only cognos administrators can create and edit routing sets. This allows administrators to specify that certain cognos dispatchers should only be used for certain bits of data. For example all the Finance data modules / packages should be sent to dispatcher 1, whilst all the Sales reports should be sent to dispatcher 2. This allows you to reserve cognos dispatchers for certain types of reports.

When a package / data module is copied, that copy is included in any existing routing sets. With FM packages this wasn't such a big deal as users could not change the content of an FM package. With data modules this becomes an issue.

Using the initial scenario above, that dispatcher 1  should only be used for finance reports. An unprivileged user can copy the finance data module, edit it, remove all the finance content and add in their own content. When anyone uses this data module it will be sent to dispatcher 1. We now have dispatcher 1 being used for any kind of data.

Or, the user could copy the finance data module, link in the sales data module, repoint a sales report to the fudged data module. We now have a user able to send a sales report to the finance dispatcher.

Within current CA functionality there is no way to preserve the functionality of routing sets - that certain dispatchers should be reserved for certain content. Even without admin privileges, any user can send any report to any 

If this is the case - why is routing set maintenance  only available to administrators, when anyone can simply bypass it.

There should be a system flag so that admin users can decide the behaviour of copied data, this flag will either keep the existing behaviour, or not include copied data sources within routing sets.




Needed By Quarter