Report security & Business Views

[pandpp]

Hi there.

I have always only used CR before & never CE. I now find myself in a position of trying to play catchup on CE. As such, I have a couple of questions that hopefully people can help me out with.

We are running CE10 & Oracle 8i.

In the ePortfolio, we can setup every user.
I have a number of reports. Of course, not every one is to have access to ALL reports.
1) Can I restrict access/view to reports, based upon user, or user group?



My reports are used across a number of Business Units, but of course, security needs to be available here as well. Business Views seemed the logical choice.

Currently, my reports have a Parameter of Business Unit, but this needs to be replaced with a more secure form of security, to physically restrict access to the other records.

I need to merely filter on a single field, which resides in a good number of the tables. Perhaps I'm trying to make it overly simplistic.

2) Do the Business Views have to setup for each & every report, or can I set up a Business View on a table?

Thanks for any help,

Peter.

 

[KingfisherINC]

I'm in a rush so brief answers:

1) Yes - It's a filter (Groups would be better).

2) The BV goes against the data source, so it sits between the report(s) and the data source(s). One BV can join many data sources, many reports can access one BV, one report can not access two BV's.

Other reports do not have to access BV (they could go directly to the data source).

Kingfisher [CECP]

 

[synapsevampire]

A shame that you don't have a means to set up security on the database, that resolves these conerns and would allow you to use standard Database Views and Stored Procedures on the database as opposed to proprietary data sources such as Business Views and BO Universes.

We're in the process of rewriting a lot of BO Universes right now based on the erroneous idea that a proprietary layer is good long term.

Any idea how BO will handle licensing in CE 11 and will you ALWAYS use Crystal? Are you sure that it's worth investing the time to construct yet another Crystal proprietary data extraction object which might later be yanked (such as the old Crystal SQL Designer which is now defunct).

-k