Resolution
Directory and Resource Administrator 6.6
symptom
The 'operands' field is not getting populated for any operation.
symptom
History of Usage Reports' are not showing accurate information after upgrading to Directory and Resource Administrator 6.6.
cause
This issue is due to Directory and Resource Administrator 6.6 not writing the 'Operands' information to the application log entry.
Whenever you complete any operation through Directory and Resource Administrator (DRA), an application log entry is generated. One of the fields in the application log entry is 'operands', which specifies what field the AA acted on. In DRA 6.6, the operands field is not populated for any operation.
fix
This issue is resolved in Directory and Resource Administrator (DRA) 7.0 and later. Upgrade to the latest version of DRA to resolve this issue.
Work around for version 6.6:
In DRA 6.6, a pre-task trigger can be utilized that writes the Operands information to the application log. The pre-task trigger should be tied to UserSetInfo operation and any other operation that you wish to report on.
The trigger script is below:
#!vbscript
Function Main
sOps = VarSet.Get("Work.AuditInfo.Operands")
if (IsEmpty(sOps)) then
VarSet.Put "Work.AuditInfo.Operands", ""
end if
Main = True
End Function