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 SPSS Modeler
Components SPSS CNDS
Created by Guest
Created on Oct 29, 2015

Variable returning the version of a job step asset

We have a number of jobs defined in C&DS that are all using the same underlying SPSS Modeler stream as a job step to create a report.
All of the jobs use the version of the Modeler stream that is labeled "PROD" indicating that this is the production version of the stream.
However, the underlying stream is updated and enhanced frequently and is used to generate reports for different projects several times each week.
It would be very useful to be able to tell the exact version of the job step was used when generating a given report.
There is currently a variable available with the name "${JobStep.VersionLabel}", but this only return the label (always "PROD" in my case). While this might be useful in some scenarios, it is not useful in mine as the "PROD" label is frequently applied to a new version of the Modeler stream.
This means that I cannot currently look at a 2-week old report and identify the exact version of the Modeler stream that was used by the job that generated the report.