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,
Post an idea
Upvote ideas that matter most to you
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.
Set Capability in Teamcontent and on Datasources/Dataservers
In Cognos, I want to set role/group base capability on items in Team Content and on datasources/dataservers. Users have permissions on lots of sources, like datasources/dataservers, datamodules and packages, because users run Cognos reports and dashboards on it.
Some users have the capability to build reports, dashboards, explorations and also datamodules. But they are not allowed to build against all sources they have access too. You want to deny build capability in combination on some sources. Like deny using Reporting on package HR. Group/role based.
The last example is possible to arrange. In Teamcontent, properties of the package, tab capalilities, link Set... This takes me to a screen where I can grant or deny capabilties per group or role on this item, the package. I can deny permissons of Report Studio (Reporting). This is a Cognos 10 screen in Cognos Analytics and is build in Cognos 10 for a reason.
My wish is to extend this screen, with the new Cognos Analytics capabilities. So you can also grant/deny on Dashboarding, Exploration, Web moddeling, Story, etc.
My wish is also to be able to set this capabilities on Dataservers, so you can deny web moddeling on a Dataserver, also group/role based.
My company had hundreds of customers that use Cognos. And using it more intensive lately. Meaning I got this question from a few of them lately.
The work around is to set deny permissions on Read, Write and Set policy. And access permissions on Execute and Traverse. But this is not full proof, this prohibits building new stuff on it, but when opening an exisiting datamodule a user still can search, find and use tables from the connected database. Witch allowes a user to search tables and content in it, in a database he does not belong in. And finding for example Salary of financial information he is not allowed to see or query.
It is a logical extent of functionalliy that was there in Cognos 10. I think is is a must have. Hoping it will be there soon in Cognos Analytics.
Do not place IBM confidential, company confidential, or personal information into any field.