Kbase P116776: Audit records are created when updating the fields that should not be audited
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
07/08/2006 |
|
Status: Unverified
FACT(s) (Environment):
OpenEdge 10.1A
SYMPTOM(s):
OpenEdge 10.1A01
Audit records are created when updating the fields that should not be audited
Only specific fields in a table are audited
An audit record is created with no event detail
CAUSE:
This is a known issue being investigated by Development
CAUSE:
This issue occurs when using OpenEdge 10.1A and OpenEdge 10.1A01.
When auditing database record UPDATE operations, additional audit-data records are created when the application updates a field that the auditing policy indicates should not be audited.
This is an example that illustrates the improper behavior:
Table ?Customer? has the fields ?Code?, ?Name? and ?Phone?.
Auditing is enabled for the field ?Name?.
When a user changes the fields ?Code? or ?Phone? but not "Name", an auditing record will be created. This should not happen because the fields ?Code? and ?Phone? are not enabled for auditing therefore no auditing record should be created (unless the field "Name" is also modified).
FIX:
A T-Fix has been created for 10.1A02 which addresses this problem. Later versions will incorporate the fix into the shipped product.
Contact Progress Software Technical Support to request the T-Fix.