[Solved] Hiding folders in the reportnet

[JO]

hi,

My requirement is to hide the Folder in the report net.

i have some reports which are in the folders. these reports cant use directly. these are drill thru reports. so i dont want to show this folder which contain reports to the user. In reports net we have a disable entry option, but it does satisfy my requirements.

can anybody plz help me?


Cheers
JO

[JO]

Sry in the above mail i have wrongly mentioned.

The disable entry option in the reportnet doesnot satisfy  my requirement.

suggentions are highly appreciable.

[Darek]

You can't hide it without disabling access to it. We all miss this type of functionality from the Upfront world. Cognos' intention was to have TRAVERSE not display a folder, which would accomplish exactly what you need, but something happened and it does not work as intended.

But there is a workaround. What you could do is change the root of Cognos Connection Public tab to a subfolder within Public Folders for non-admin users. This way they will never see any packages or drill-through folders.

[JO]

Hi Darek,

Thanks for ur reply.

but my intention is to hide the folder in the same package without moving in to anyother location.

suppose i am having a one report say "X" the drill down report say 'Detailed X'  is in same package with in the folder say "Detail".

i want to hide this folder showing only X report to the User not the folder.

Is there any other way of doing it?

Jo

[Darek]

My suggestion was a workaround, in my opinion the only viable option given your needs and current state of the product.

[cognosfreelancer]

Darek

You piqued my interest. Could you explain your workaround further. I could not quite understand it.

Thanks
NKT

[josephalapatt]

Darek

You piqued my interest. Could you explain your workaround further. I could not quite understand it.

Thanks
NKT

[Darek]

Take a look at templates\ps\system.xml ...

   <!-- Specify the base navigation root for consumers. -->
   <param name="consumer-root">/content</param>   
   
Enjoy tweaking ...

[JO]

Hi Darek,

Can u explain me  how to imply workaround in detail...

Jo

[Darek]

1. Create a new folder under Public Folder
2. Go to its properties and view search path
3. Copy search path to your clipboard
4. Paste it in place of /content for parameter consumer-root in ps\system.xml template
5. Save the file
6. Restart ReportNet

[JO]

Hi

Thanks for ur reply.  it workedout well.


JO

[Darek]

I love to correct myself once in a while. By accident I've figured out how to bring back the old Upfront "hidden folders" or how to hide folders to which users have only traverse right.

In Templates\ps\portal.xml you can find this parameter:

   <param name="visible">[permission(&quot;read&quot;) or permission(&quot;write&quot;) or permission(&quot;execute&quot;) or permission(&quot;traverse&quot;) or permission(&quot;setPolicy&quot;)]</param>

If you remove "or permission(&quot;traverse&quot;) " it effectively hides the folder when only traverse right has been granted.

You have to restart ReportNet after making the change.

[JO]

Hi Darek,

i am not able to find the Portal.xml in "Templates\ps" location. This portal .xml is in "\templates\ps\messages" location. Within this xml i didnt find <Param name = "Visible">.

Can u please tell me where it is exactly locatetd and where do i need to make changes?

JO

[Darek]

Sorry for the typo. I've meant system.xml.

[JO]

hi Darek

i made the changes whatever u mentioned, but i am able to traverse, and i am able to view the folder.

do i need to set any thing other than this.

JO

[Darek]

Do you have ONLY Traverse? Are you an Admin ?

If any of the above is true, you will be able to see it.

[JO]

Hi Darek,

Thank U very much.

Actually i did a small mistake, i had give exceute , read and traverse right permission to the folder. becoz of this i was able to see the folder. Now i changed only to traverse right. i am able to HIDE THE FOLDER  :D.

Once again, Thanks a lot.

Cheers
JO

[JoeBass]

This has been a pet peeve of ours for a long time.  Your solution works very well.  Thank you!

[davidsoc]

I've tried editing the system.xml (removed traverse from the visible field).

For me, it works as in it effectively hides the folder but i cannot drill through to any report placed within the 'hidden' folder. I require the execute permission for the target reports.

I also tried inserting traverse back into the system.xml and removed execute. I thought this would have a similar effect... if the folder only has execute permission then it will be hidden from the user. However, when i tried to drill through to a target report the error message returns that it cannot find the target report (no traverse rights). The same drill through works for myself (admin rights).

Anybody got any thoughts?

[donb410]

Normally, I would not have read or responded to a [Solved] topic, please consider starting a new topic if you encounter a similar situation again.Ã, 

On our project, I removed traverse as was suggested, then I overrode the access permissions from the parent entry and set just traverse on the folder for Query Users (Role) and Report Users (I made the last group) and verifying that admin had all permissions for the folder.Ã,  I too had the problem of then not being able to execute the drill through reports.Ã,  I noticed two things - first the drill throughs were going to the wrong place, this gave me the "not able to find the target report" message.Ã,  After I reset the drill through references (6 drill through reports total from 8 different reports) to the correct reports - I received the "unable to execute report" message.Ã,  Again I overrode the access permissions from the parent entry for each drill through report and I explicitly set execute and traverse on each drill through report for the Report Users group and it works perfect.Ã,  This really helped us out, because we had over zealous users trying to execute the drill through reports directly!Ã,  Now they can run the drill throughs in the proper manner from a parent report.

Don

[davidsoc]

Sorry for positing in a [Solved] topic but i thought it'd be better here than starting another topic on exactly the same problem.

You suggestion sounds good and i'll look into it. Thanks