Oracle Fusion Technical: Reports, Data, Integrations and Extensions · Module 2 · Security, roles and what you are allowed to see
Custom roles: when, and how to survive an update
Lesson 18 of 177 · 2 min
COPYING A SEEDED ROLE FORKS IT PERMANENTLY. Oracle changes theirs quarterly — new privileges for new features, occasionally a privilege split in two — and yours stays exactly as it was on the day you copied it. What that buys is control. Your role is stable, you can explain every privilege in it, and an update cannot silently widen what your users can do. What it costs is maintenance, and the cost is not theoretical: a feature the business asks for six months from now may need a privilege that arrived in Oracle's version and not in yours, and the symptom will be a page that does not open with no obvious cause. The alternative is an INHERITED role with a targeted addition. Rather than copying, create your own role that inherits the seeded one and adds the specific duty you need. Oracle's changes keep flowing through the inherited part,…
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 2 · Security, roles and what you are allowed to see
- 1Roles, privileges and duties
- 2Data security versus function security
- 3Data access sets and business unit security
- 4The security diagnostic sequenceFree preview
- 5Reading the security console
- 6Security for reporting: the part people miss
- 7Custom roles: when, and how to survive an update
- 8Provisioning and role assignment at scale
- 9What breaks: the three security failures you will meet
- 10Lab briefing · Diagnosing three access failures