Change Tracker (UXPROD-782)

[UXPROD-4040] Capture log of deleted records Created: 07/Feb/23  Updated: 04/Jan/24

Status: Draft
Project: UX Product
Components: None
Affects versions: None
Fix versions: Trillium (R1 2025)
Parent: Change Tracker

Type: New Feature Priority: P2
Reporter: Dennis Bridges Assignee: Dennis Bridges
Resolution: Unresolved Votes: 1
Labels: LC4, acquisitions, loc, volaris-candidate
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Issue links:
Cloners
is cloned by UXPROD-4041 Record deletion workflow management -... Draft
Relates
relates to UXPROD-3215 Display a history of edits for the Or... Closed
relates to UXPROD-3457 Organizations - Display a history of ... Draft
Release: Trillium (R1 2025)
Epic Link: Change Tracker
Front End Estimate: Large < 10 days
Front End Estimator: Khalilah Gambrell
Front-End Confidence factor: 20%
Back End Estimate: XL < 15 days
Back End Estimator: Khalilah Gambrell
Back-End Confidence factor: 20%
Development Team: Thunderjet
PO Rank: 0
Rank: Cornell (Full Sum 2021): R1

 Description   

Current situation or problem: When records are deleted from the system there is no way for the user to know they once existed or who deleted them. This means the library looses information that could be required by auditors

In scope

TBD

Out of scope

TBD

Use case(s)

  • User creates and order and invoice. Invoice is canceled and order line in deleted because it was created in error. Auditors are able to see the invoice but it is not clear whether an order ever existed for that invoice and why it was deleted.
  • Library has a legislated obligation to explain the actions taken on records to the necessary auditors. (Actor, Action, time and purpose)
  • Certain records that are linked to third party system (Eg. momentum) can not just be deleted without cause problems for that third party system.

Proposed solution

TBD - Incorporate the tracking of deleted records into the version history functionality. Provide an exportable list of deleted records with very limited data. Use mod-audit to capture deleted record data.

Links to additional info

Questions



 Comments   
Comment by Erin Nettifee [ 14/Feb/23 ]

Dennis Bridges how does this relate to UXPROD-910 Open ? (Or does it?) It's in the Change Tracker epic, are you thinking that a new app would enable the export of this information when order records are deleted?

Comment by Dennis Bridges [ 19/Feb/23 ]

Erin Nettifee I think it relates to change tracker because the users desire is to be able to understand what has happened to a deleted record. In a way you could consider that part of the record "history". I think what we have implemented for orders could be the ideal mechanism for serving this information to users. Ie. mod-audit is used to track version history "changes" made to orders and order lines. Perhaps it should also note which ones have been deleted so we can serve up that information to users/applications in some way. 

Mainly it is related in that deletion is making a "change" to a record. User want to be able to identify when that has happened and possibly understand a little about why that happened.

Comment by Khalilah Gambrell [ 14/May/23 ]

Unsure what the difference is between UXPROD-4041 Draft and this one. Raman Auramau  what do you think? 

Generated at Fri Feb 09 00:36:47 UTC 2024 using Jira 1001.0.0-SNAPSHOT#100246-sha1:7a5c50119eb0633d306e14180817ddef5e80c75d.