If you are unable to create a new account, please email support@bspsoftware.com

 

News:

MetaManager - Administrative Tools for IBM Cognos
Pricing starting at $2,100
Download Now    Learn More

Main Menu

[solved] disable entry, bug or feature?

Started by Wizard of Mig, 01 Oct 2014 03:24:21 AM

Previous topic - Next topic

Wizard of Mig

Hi,
potentially you know the "disable entry" setting for objects in Cognos Connection.
I wanted to use this feature to disable packages (= report execution) while updating our data warehouse. The expected behaviour was that users can access saved report output but cannot run a query or execute a report.
Well, it turns out that this feature has NO effect! I can execute reports or start Cognos Workspace advanced and run new reports/analysis.
Bug or feature?
Is there any other good strategy for scenario?

Thx in advance
Matthias

MFGF

Quote from: Wizard of Mig on 01 Oct 2014 03:24:21 AM
Hi,
potentially you know the "disable entry" setting for objects in Cognos Connection.
I wanted to use this feature to disable packages (= report execution) while updating our data warehouse. The expected behaviour was that users can access saved report output but cannot run a query or execute a report.
Well, it turns out that this feature has NO effect! I can execute reports or start Cognos Workspace advanced and run new reports/analysis.
Bug or feature?
Is there any other good strategy for scenario?

Thx in advance
Matthias

Are you by any chance a member of the System Administrator's role? If so, you can see and do everything, regardless of restrictions or security or any other limitation that may be applied. That's not the case for "normal" users though.

MF.
Meep!

Wizard of Mig

No,
I'm not a member of our "glorious" systemadmin group  ;)
At least not that I'm aware of ... I have no access to the admin console so I guess it means "no"

Cheers,
M.

MFGF

Quote from: Wizard of Mig on 01 Oct 2014 03:38:44 AM
No,
I'm not a member of our "glorious" systemadmin group  ;)
At least not that I'm aware of ... I have no access to the admin console so I guess it means "no"

Cheers,
M.

Ah. Ok. That was only the first thing to check, though :)

Are you the owner of the folders/reports in question? Do you have "Set policy" privileges to the content? I suspect both of these would also mean you can use them while they are disabled...

Cheers!

MF.
Meep!

Wizard of Mig

"Are you the owner of the folders/reports in question?"
Nope

"Do you have "Set policy" privileges to the content? I suspect both of these would also mean you can use them while they are disabled..."
I guess yes since at least in our development environment I can change the status to disabled. Good hint, let me check :)

Wizard of Mig

BTW, at least in CRN (long time ago, different galaxy ... 8) ) the effect was that a admin could give himself the right if necessary. But he/she couldn't execute the report / package ...

Wizard of Mig

The "Do you have "Set policy" privileges to the content?" led to the solution. You need to make sure that you don't have the right to set policies. The feature "disable entry"doesn't have an effect when you can set the policy on the disabled object ...
However, we are experiencing another little issue: you need to log off an log on again so that a changed status of the enabled object can experienced by a user. I guess it's a local caching issue, our sysadmin need to take care for ;)

Cheers and thx for the help!
M.