Details
-
New Feature
-
Status: Closed (View Workflow)
-
TBD
-
Resolution: Done
-
None
-
None
-
Leipzig
-
-
0
-
R4
-
R3
-
R2
-
R3
Description
Use case: As a library, we receive exmatriculation notifications through our campus ID system. We want to deactivate exmatriculated users in Folio but do not want to delete them immediately (for report reasons and given reactivation period). But we want to make sure the user doesn't have any open transaction in the library when they leave the university. If there are open transactions, we want to notify the user based on some sort of report or logfile for a quick clearing up. For this reason, the transaction check (previously called dependency check) must also be possible independently of the deletion of the user record. Transaction check on user deletion process is part of https://issues.folio.org/browse/UXPROD-2728.
Requirement: As a system administrator with API access, I would like to run a transaction check (previously called dependency check) for a particular user {userId}. The transaction check shall include:
- open loans
- open requests
- unpaid fees/fines
- unexpired proxy
- manual blocks (automated should be covered by open loans or fees/fines)
The user can be active or inactive. I need a report of open transactions for further processing in the service unit. This report is also part of MODUIMP-33.
TestRail: Results
Attachments
Issue Links
- is defined by
-
MODUSERBL-115 Create a list of open transactions whose presence will prevent deletion (UI & API, Single)
-
- Closed
-
-
MODUSERBL-116 Report on open transactions that prevent user deletion (API, Single user)
-
- Closed
-
- relates to
-
UXPROD-2388 Delete user through the UI with check for open transactions (UI, Single user)
-
- Closed
-
-
UXPROD-2728 Delete user through the API with check for open transactions (API, Single user)
-
- Closed
-
- mentioned in
-
Page Loading...