AnsweredAssumed Answered

Out-of-the-box reports and public schema

Question asked by Kevin Perkins on Nov 8, 2019
Latest reply on Nov 15, 2019 by Sean Miller

Looking at the out of the box reports, some of them use views that aren't listed in the public database schema reference. For example, when creating a report, if I choose:
Type: Review

Template: Review Delegation History


The FROM clause for the report is auto-populated with V_REVIEW_DELEGATION_HISTORY.


We've gotten numerous warnings from RSA support about staying away from querying things that aren't in the public schema and since last year those warnings have gotten stronger. So I'm confused. On the one hand, it seems like if an out-of-the-box report references some schema object, then it should be fair game for everyone else. On the other hand, the public database schema reference emphasizes that the public schema consists of a specific set of objects visible to the ACMDB user, and this is not one of them.


Who's right? Should I be treating these out-of-the-box report queries as magic or can I add conditions, joins, or whatever else suits my needs?