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 Not under consideration
Workspace Planning Analytics
Created by Guest
Created on Oct 21, 2021

Selection capabilities in PAW Modeller

I am finding the object tree in PAW Modeler difficult to use. It seems to have re-implemented some of the issues in Perspectives.

What I would suggest is that instead of one continuous tree showing all types of objects, cubes, dimensions, etc, that we instead have selections at the top to select one type of object, so that the lower pane only shows objects of the selected type, eg cubes, or dimensions, not both. A developer is in general only wanting to find one type of object at a time.

The selection area at the top should include the search box. This needs to be static in the top pane. At present it scrolls with the list of the cubes and soon scrolls off the screen. If you cannot find the search box then you cannot use it to search!

The ability in Perspectives to type the first character to jump to eg the cube that starts with that character has been lost but if the search functionality mentioned above was implemented this would not be necessary as this would give a better way to search than Perspectives.

There should be a sub-search, eg if expanding a cube to show views then the sub search would search the views. If expanding a Dimension then the sub search would be for Subsets. An alternative would be the sub types opening in a different column to the parent object, eg Cubes in the left column, and if they pick a cube and expand views, the views show in the right column with a search option above that. I think most cubes and dimensions that have been around a while tend to have a lot of different views and subsets so some way to search these is needed.

The fact that the list only shows a small number of items and then only shows further items when you scroll down is problematic. If the list was constrained to only show one type of object, it should be possible to show all objects without stretching client memory limitations too much.

The icon for rules is difficult to distinguish from that for a cube and should be changed, eg re-introduce more colour.

Double clicking a cube should show the default view.

The fixed top pane should show the selectors for the main TM1 objects, eg icons for cube, dim, process, and chore. It should also show the search text boxes for major and dependent objects (views and subsets). There should also be a + to open a window to create a new cube, dimension, etc.

Following on from another suggestion the full implementation of application folders as per Perspectives would enable developers to organise cubes, processes, etc, into a logical folder structure of related items. Happy to show IBM our folder structure to illustrate how we use this.

Needed By Quarter
  • Admin
    Stuart King
    Nov 2, 2021

    I've updated the status to Not under consideration. This idea is a mix of different enhancement requests. Some of which are already partially implemented (e.g the search) and some that cannot be implemented without a redesign of the modeling tree, which is not planned. Please describe a single enhancement request per AHA idea being submitted.

  • Guest
    Oct 26, 2021
  • Guest
    Oct 22, 2021

    In addition the current separation of standard and control objects is not one that I find useful. If I select cubes and search for a name then I want that to show up regardless of whether it is a standard or control object. I would suggest that instead that the list of any object type ie cube, dimension, process, chore, includes the control objects. Instead in the top pane we can just have a toggle button to select whether we want to see control objects. The icon could just be a } curly bracket.

    Most developers are going to be working on both Control Objects and Standard Objects.