[MODUSERS-415] Restrict ability to change virtual patron data via APIs Created: 26/Dec/23  Updated: 05/Feb/24

Status: Open
Project: mod-users
Components: None
Affects versions: None
Fix versions: None

Type: Story Priority: P3
Reporter: Irina Pokhylets Assignee: Gurleen Kaur1
Resolution: Unresolved Votes: 0
Labels: back-end, dcb-phase2
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Attachments: Microsoft Word API_to_be_restricted.xlsx    
Issue links:
Relates
relates to UIREQ-1053 [Request] Get UI scenarios where PUT ... Closed
relates to UIU-3015 [Users] Get UI scenarios where PUT AP... Closed
relates to UXPROD-4578 DCB FOLIO circulation phase 2 Open
Sprint: Volaris Sprint 184
Story Points: 3
Development Team: Volaris
Release: Ramsons (R2 2024)

 Description   

Purpose/Overview:
The DCB (virtual) patrons are created as part of DCB FOLIO integration. The change of virtual parton data should not be allowed from front-end and back-end. The UI changes for preventing data changes are implemented (DCB phase1). This story is for implementing restrictions on changing virtual patron data via APIs.

Requirements/Scope:
1. The system should respond with an error on an attempt to change virtual parton data through APIs, listed in the attachment.

Acceptance criteria:
1. The system throws an exception on the change of virtual patron data via APIs listed in attachment.

 


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