IBM Data and AI Ideas Portal for Customers

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

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

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 product management 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 notification 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.

Additional Information

To view our roadmaps:

Reminder: This is not the place to submit defects or support needs, please use normal support channel for these cases

IBM Employees:

The correct URL for entering your ideas is:

Status Future consideration
Workspace Cognos Analytics
Components Administration
Created by Guest
Created on Oct 9, 2021

Remove the need for NC Drop, handle dead processes / schedules better

Currently, if a bad report is scheduled or something happens to the environment, the NC table can build up as explained by this technote and make schedules slow or send them into pending. To resolve this requires a lengthy process of a) backing up the content store (requires DBA, takes hours) and b) running the NC drop script. Please build this into the system and prevent this table from building up. It's going to happen, and shouldn't be something you require customers to do. The system should be handling cleanup on it's own and not require your customers to overengineer their own processes to make up for the system not being resilient.

Cognos is a product that has been around a long time and is likely in a fairly mature state at most enterprises. Given this, it is likely a lot of projects have been created over time that aren't what we would call "perfect" -- that means things like using old features, using CQM, multiple versions of the same report copied by users over time, i.e. not best practices, using messy direct SQL. It is one thing to have to treat your Cognos environment very militantly to prevent this from happening, i.e. restrict access, increase testing costs, overtune the environment, spend large on training, etc. This is fantasy though and is probably unachievable in some of these legacy environments where the Cognos expertise is low.

Needed By Yesterday (Let's go already!)