Every month or so I will be publishing a list of list of RFEs (Request For Enhancements) that have been submitted to IBM. Some of these are enhancements that I believe should be instituded ASAP, and others just sound interesting.
This is the second month doing this, please take a look at November 2018’s list here.
This time we’ll start with a couple of RFEs relating to data modules. Data modules are a great addition to Cognos. It’s an ETL job, it’s a data source, it’s a modeling tool. I love it to death, but that doesn’t mean it can be improved.
1. Object Level Security at Table and Field Level for Data Modules
Under Consideration with 8 votes.
Data security is possible, to a small degree, but object security still isn’t. There are some columns that I don’t want users to see, ever. If they run a report that uses it, I want it to fail hard with an unfriendly error message. We can do it in FM, but not yet in data modules.
2. Data Module created from Data Server with multiple connections should be able to use any connection
Under Consideration with 3 votes.
With regular data sources it’s possible to create multiple connections to a single database, or even different databases. Reports built on FM models work very gracefully with this. Data modules just aren’t there yet.
3. Data Module – Select Unmatched Column Values
Under Consideration with 5 votes.
For the most part a standard equals join is pretty much all I ever need, except for that one time in a year where I absolutely need to have a non-standard join. I haven’t had that problem yet, but it looks like someone already did.
Now let’s look at a couple others
4. RAVE2 SDK
Under Consideration with 60 votes.
Story time! A few years ago I was giving a lecture, at BACon, on RAVE. How to use it, how to work with it, and most importantly a walkthrough of the grammar. It was a great success and everyone loved it. Then a certain IBMer who will remain anonymous, had his session. Where he said that RAVE 1 was being dropped in favor of RAVE 2. It was like I got punched in the stomach. However RAVE 1 is still going strong. That being said, having a modern kit for customizing or creating our own visualizations would be awesome. It’s interesting to note that the RFE linked here has an update from IBM: While we would like to have an extensible viz API, it is unlikely to be RAVE 2 based.
5. Improve Look, Flexibility and augment the properties on Interactive Dashboard and Visualization (IDnV) Prompts
Submitted with 9 votes.
Recently there’s been an upsurge on people demanding changes to the prompting GUI. The bottom line is the prompt options are aging, and competing tools are much “sexier”.
Did I miss any important RFEs? Got an important idea that you want in Cognos? Drop a note in the comments.
Hello,
when I discuss at analytics university, the answer was no SDK and after Rave1 and Rave 2 there will be D3js.
I also ask on former community forum the answer was not clear but not seems to open a rave2 SDK.
regards,
Really like that you are doing this. I try to share RFE’s that I think are worth voting with our Cognos user group and recently I have seen others doing this more in the IBM Community for Cognos Analytics.
Your fix list also helped a lot.
Thanks.
If you have any that you think are worth voting for, drop me a line with the details and I’ll include them in the January roundup.
This came up about cascading prompts for dashboards. We have a site where it has business unit and position in the All filters but there is not way to cascade the position based on the business unit chose. So it I chose governor’s office, I can get positions like hockey coach. This doesn’t make sense.
https://www.ibm.com/developerworks/rfe/execute?use_case=viewRfe&CR_ID=122149
And that’s on the list!