0018978: Audit Trail screen Old Value / New Value fields should have real values, not IDs

Openbravo Issue Tracking System - Openbravo ERP
View Issue Details

ID	Project	Category	View Status	Date Submitted	Last Update
0018978	Openbravo ERP	A. Platform	public	2011-11-05 02:58	2022-02-01 08:08

Reporter	johnfandl
Assigned To	Triage Platform Base
Priority	normal	Severity	minor	Reproducibility	have not tried
Status	acknowledged	Resolution	open
Platform		OS	5	OS Version
Product Version
Target Version		Fixed in Version
Merge Request Status
Review Assigned To
OBNetwork customer
Web browser
Modules	Core
Support ticket
Regression level
Regression date
Regression introduced in release
Regression introduced by commit
Triggers an Emergency Pack	No

Summary	0018978: Audit Trail screen Old Value / New Value fields should have real values, not IDs
Description	The Audit Trail screen (which shows ALL audit records) is not consistent with the window-specific audit screen, in terms of the values in the Old / New Value fields. The window-specific audit screens have foreign key values properly resolved, while the Audit Trail screen itself shows only the unresolved record id, which is useless to the user.
Steps To Reproduce	For example: 1. Go to a sales order line, and change the tac from Arrendamiento 18% (cobros) to Arrendamiento 16% (cobros) - IVA Normal 2. On the Sales Order Audit Trail screen, the old and new values match what the user selected on the screen 3. But, go to the Master Audit Trail screen and see that the old value is 4DB3919EB42E485FBFB6EA1342C07C04 and the new value is 8AA93DB8D416480E9A54D79A25403E7F. These are not useful values. If the foreign key IDs were properly resolved to real values (like on the table-specific audit screens), it would be very, very useful for searching. For example, consider this common scenario: - employee maintains an order line, to change the tax (for example). It is actually the WRONG order line, a simple mistake. - supervisor looks at the intended order line, sees that it has not been changed. - Asks employee about it. Employee says "yes, I changed an order line to 18%". - They look at the record and employee realizes he changed the wrong order - If the real values were properly shown on the Audit Trail screen, it would be a very simple matter to FIND the order line that was incorrectly changed (so it could be changed back)--just filter on the New Value. As the screen is now, it is useless for this type of research - Additionally, the Audit Trail screen must include a link to open the maintenance screen up on a new application tab (I will enter a feature request for that as well).
Proposed Solution	Resolve the foreign key values on the Master Audit Trail screen, to be consistent with the table-specific audit screens. The real point in time values should be captured in the audit tables, not just the IDs. This would make the Audit Trail much more useful for easily finding any information that was changed (not just literal values).
Additional Information
Tags	No tags attached.
Relationships
Attached Files

Issue History
Date Modified	Username	Field	Change
2011-11-05 02:58	johnfandl	New Issue
2011-11-05 02:58	johnfandl	Assigned To	=> alostale
2011-11-05 02:58	johnfandl	Modules	=> Core
2011-11-16 16:38	alostale	Note Added: 0042882
2011-11-16 16:38	alostale	Status	new => acknowledged
2011-11-16 16:38	alostale	Type	defect => design defect
2011-11-16 16:38	alostale	Steps to Reproduce Updated	bug_revision_view_page.php?rev_id=2911#r2911
2011-11-16 16:38	alostale	Proposed Solution updated
2012-09-24 21:03	AugustoMauch	Note Added: 0052416
2012-09-24 21:03	AugustoMauch	Status	acknowledged => scheduled
2012-09-24 21:03	AugustoMauch	Steps to Reproduce Updated	bug_revision_view_page.php?rev_id=3891#r3891
2017-03-31 14:36	alostale	Status	scheduled => acknowledged
2017-04-10 14:33	alostale	Assigned To	alostale => platform
2022-02-01 08:08	alostale	Assigned To	platform => Triage Platform Base

Notes