Oracle Fusion Technical: Reports, Data, Integrations and Extensions · Module 4 · BI Publisher: data models, templates and bursting
Security in BI Publisher
Lesson 40 of 177 · 2 min
Three questions, and a reviewer will ask all three. WHO CAN RUN IT? A BI Publisher report is protected by the roles granted on its folder and on the report itself. The default in a hurry is to leave it wherever it was built, which is usually a folder half the organisation can reach. WHO CAN EDIT IT? Editing rights are separate from running rights, and they matter more: somebody who can edit the data model can change what the query returns for everybody, including changing a filter that was the only thing restricting the rows. AND DOES THE QUERY RESPECT THE DATA SECURITY THE REST OF FUSION ENFORCES? This is the one people miss, and Module 2 covered it: your own SQL does not necessarily apply the ledger and business unit gates the UI applies. A report can legitimately show everything — a statutory return must — and it…
The full lesson is part of the course
The video, the complete written lesson and the module quiz are included in Oracle Fusion Technical: Reports, Data, Integrations and Extensions, with a certificate on completion and a fourteen-day refund window.
In this module: Module 4 · BI Publisher: data models, templates and bursting
- 1What a data model actually isFree preview
- 2SQL data sets: writing the query
- 3Parameters and lists of values
- 4Bursting: one run, many recipients
- 5RTF templates: the practical subset
- 6Excel and eText templates
- 7Sub-templates and reuse
- 8Layout, pagination and the printed page
- 9Localisation: Arabic, dates and numbers
- 10Performance: making a slow report fast
- 11Security in BI Publisher
- 12Scheduling and delivery
- 13What breaks: five BI Publisher failures
- 14Lab briefing · A supplier statement, end to end