I tried your suggestion. It made no difference. The Database View has no fields defined, so it combines the entire Incident and Problem tables into 1 view.
I have 2 Read ACLs defined on the Database View on my Development instance
1: Incident_Problem.--None-- ITIL: that provides ITIL Users with read access to the Database View
2: Incident_Problem.* ITIL: that provides ITIL users with read access to the Records within the Database View
This works. However the same ACLs on Production do not work. This makes me think that there are ACLs on the Production Incident and Problem tables that are preventing this. My understanding is that, post-Fuji, specific ACLs are required on Database Views to prevent unauthorised access to underlying Tables.
Therefore, I would assume that if there are specific ACLs for Columns on the Incident and Problem tables, any ACLs on the Database View would respect these.
Example:
There is a ITIL User, Read ACL on the Incident.Number column. That would mean that anyone with the designated Role would be able to Read the Incident.Number, but, by exclusion, would NOT be able to Read any other Columns.
Adding a Read.* ACL to the Incident_Problem Database View would only provide Read access to Columns on the Incident and Problem tables supported by the ACLs on the underlying tables (in this case ONLY the Incident.Number column). Am I understanding this correctly?
