Following changes to CA DataMinder database security models, some custom reports may no longer run correctly for certain users. Specifically, this issue affects users assigned to a policy-based security model and who are trying to run any custom report (r12.0 or earlier) that directly accesses the Wgn3Trigger database table.
To avoid this problem, we now recommend that all reports accessing the Wgn3Trigger table do so indirectly through a new database view, WGN_V_TRIGGER_1. If you have custom reports that access this table directly, amend these reports to reference the new database view.
Although this issue does not currently affect users assigned to a management group-based security model, we recommend that you make this change anyway to fully safeguard these reports against possible future database changes,
|
Copyright © 2012 CA.
All rights reserved.
|
|