Custom BI Webcat Reporting Duty

Sian S

Summary

Trying to hide seeded reporting folders and understand the updated options within 19D

Content

We are keen to have the option to hide seeded folders from users. Changing permissions on seeded report folders comes up with the following error:

"In-place customizations are not allowed on factory delivered content. Save your customizations in /shared/custom"

***

We were really pleased therefore to see the following release notes for 19D:

https://www.oracle.com/webfolder/technetwork/tutorials/tutorial/cloud/r13/wn/common/releases/19D/19D-common-wn.htm#F10098

However, I am trying to understand how it works. Has anyone used these roles yet?

The BI Consumer role still has traverse permissions to these seeded folders, therefore struggling to understand how assigning another role counters this. 

Also - the Custom BI Webcat Reporting Duty, which is the Duty Role that it is advised we edit put into a role and assign, is unable to be copied. Is this what people would expect?

If anyone can give any further detail on how this works, it would be much appreciate. Keen to lock down some of these seeded reporting folders.

Kind regards,

Sian.

 

 

Version

19D

Nathan CCC

Hi, I have set it up. When i logon as administrator I see all the folders. But when I logon as a consumer I only see a subset of folders for the folder duty roles I have assigned to that user. My only confusion was the empty folder for Extensions hence the previous post. But all the other folders seem to work ok. Give it a go. Regards, Nathan

Nathan CCC

BTW I think is is the "Read" privilege on the top folder that makes it happen. "Traverse" is no good if you can not "Read" it?

see

Oracle® Fusion Middleware
User's Guide for Oracle Business Intelligence Enterprise Edition
11g Release 1 (11.1.1) E10544-08 December 2014
https://docs.oracle.com/middleware/11119/biee/BIEUG/mancat.htm#BIEUG10771

 

Nathan CCC

Regards "cannot copy", I do not think you need to copy, I think it is ok to create a new Custom "Custom BI Web Cat Reporting Duty" role, using whatever naming convention you have, then on step 4 on role hiearachy add whatever "BI_XXX_REPORTING_DUTY" roles you need. For example, BI_FIN_REPORTING_DUTY. That way you do not have to repeat anything in 3 months time. Now just grant this new custom role to your authors.

Sian S

Thanks for your responses Nathan.

I have edited the Custom BI Webcat Reporting Duty Role to remove a few catalog duty roles to test and then added this to the a new job role. This looks to have worked, which is great.

I will test creating a new Custom BI Webcat duty role - but given users can see the seeded folders by default with BI Consumer, if I wanted none of the seeded reporting folders to be visible, this means I wouldn't be adding any reporting catalog duties to this newly created role... it would therefore be empty. So I don't know how assigning this would let the system know to hide catalog files. I thought that there must be something embedded in the Custom BI Webcat Duty Role, as well as just the assigned duty roles.... and if so, that I would need to make a copy?

If it isn't possible to copy, then I wondered how people would deal with different combinations of seeded folder access.

Thanks,
Sian.

Christian Berg -Oracle

"BTW I think is is the "Read" privilege on the top folder that makes it happen. "Traverse" is no good if you can not "Read" it?"

Traverse means that you can programmatically go through (traverse) the folder to access objects or sub-folders inside it but you can not navigate through it and open it in the GUI. It won't even show. That means that you can seen and use analysis mapped onto a dashboard if they reside in that folder but you can not use the catalog to click your way through to them and open them.