UAT - Prevent Inactive patrons from Requesting
Brief description
FOLIO now prevents Inactive patrons from submitting requests if a patron's User account is Inactive. This new functionality includes the ability to prevent both regular Patrons from submitting requests and Congressional patrons from submitting Mediated requests in the Secure tenant, if they have been marked as Inactive.
Actions included as a part of this UAT as are follows:
Attempt to create a Request for an Inactive patron
Changing status of patron from Active to Inactive
Ensure no Request has been created (Central tenant, Data tenant, and for Authorized staff, Secure tenant)
Testing will take place December 17 through 23, 2025. Please submit any feedback by the end of the day on Tuesday, December 23, 2025.
Jira feature: https://folio-org.atlassian.net/browse/UXPROD-5499
Relevant testing information
Test environment: https://folio-edev-vega-2nd-consortium.ci.folio.org/ Please note that the testing environment is available between 3 a.m. and 5 p.m. ET and testing will need to be planned accordingly.
Test affiliations: Consortium (non-Congressional patrons) or University (Congressional patrons), depending (Instructions on checking & changing affiliation)
Feedback form: Prevent Inactive patrons from requesting
Test credentials: (username/password)
m1/Test1313# - select “Consortium” tenant for login
m2/Test1313#- select “Consortium” tenant for login
m3/Test1313#- select “Consortium” tenant for login
m4/Test1313#- select “University” tenant for login
m5/Test1313#- select “University” tenant for login
Home tenant | Username | Password | First name, Last name | Barcode | Affiliation | Authorization role | Capability set(s) |
Consortium (Central) Unauthorized staff members testing | m1 | Test1313# | Test, User1 | m1 | Central | m1 | UI-Requests - manage UI-Users - edit, create |
College (Data) | m2 | UI-Requests - manage | |||||
Consortium (Central) Unauthorized staff members testing | m2 | Test1313# | Test, User2 | m2 | Central | m1 | UI-Requests - manage UI-Users - edit, create |
College (Data) | m2 | UI-Requests - manage | |||||
Consortium (Central) Unauthorized staff members testing | m3 | Test1313# | Test, User3 | m3 | Central | m1 | UI-Requests - manage UI-Users - edit, create |
College (Data) | m2 | UI-Requests - manage | |||||
University (Secure) Authorized staff members testing | m4 | Test1313# | Test, User4 | m4 | Central | m2 | UI-Requests - manage |
College (Data) | m2 | UI-Requests - manage | |||||
University (Secure) (home tenant) | m3 | UI-Requests - manage UI-Users - edit, create | |||||
University (Secure) Authorized staff members testing | m5 | Test1313# | Test, User5 | m5 | Central | m2 | UI-Requests - manage |
College (Data) | m2 | UI-Requests - manage | |||||
University (Secure) (home tenant) | m3 | UI-Requests - manage UI-Users - edit, create |
Test Patrons:
Tenant | Patron | Status | Barcode |
Consortium (Central) | User, Patron1 | Active | 1111 |
Consortium (Central) | User, Patron2 | Active | 2222 |
Consortium (Central) | User, Patron3 | Active | 3333 |
Consortium (Central) | User, Patron4 | Inactive | 4444 |
Consortium (Central) | User, Patron5 | Inactive | 5555 |
Consortium (Central) | User, Patron6 | Inactive | 6666 |
University (Secure) | User, Patron7 | Active | 7777 |
University (Secure) | User, Patron8 | Active | 8888 |
University (Secure) | User, Patron9 | Active | 9999 |
University (Secure) | User, Patron10 | Inactive | 1010 |
University (Secure) | User, Patron11 | Inactive | 11 |
University (Secure) | User, Patron12 | Inactive | 1212 |
Shared instances created:
How to test an Inactive patron (cenin00000000002) - Shared instance in Central; One holding in College (LB 2395 .E65 2010); Three items in College:
1238579634554435812875946528714
How to test an Inactive patron 2 (cenin00000000003) - Shared instance in Central; One holding in College (LB 2395 .E67 2010); Three items in College:
1235946879225976424195798546
How to test an Inactive patron 3 (cenin00000000005) - Shared instance in Central; One holding in secure University (LB 2395 .E69 2010); Three oLoan items in University:
1235946879325976424185798545
How to test an Inactive patron 4 (cenin00000000004) - Shared instance in Central; currently no Holdings or Items
Related videos and information
Prevent requests (Inactive) - non-Congressional patrons
Prevent requests (Inactive) - Congressional patrons
Instructions
Try to create a Request / Mediated request for an Inactive patron
Log in to UAT environment
Open the Requests application in the Central tenant, or Mediated requests application in the University tenant for staff members authorized to work with Secure patrons
Select an Inactive patron from the “Test patron” list above
Click “Actions” button
Select “New” option
Uncheck “Create title level request” checkbox (if checked)
Enter item barcode from Preconditions in “Item barcode” field
Press or click on “Enter” keyboard button
Enter patron user barcode from Preconditions in “Requester barcode” field
Press or click on “Enter” keyboard button
Select “Page” request type from “Request type” dropdown
Select any service point from “Pickup service point” dropdown
Click “Save & close” button
Note Error toast that appears
Expected result is “This request was not placed successfully”
Note if the “New request” form is displaying
Click “Cancel”
Expected result is “New request” form is closed
Ensure no Request has been created in the Requests app of the Consortium or College tenant
For staff members working in the University tenant, related to non-OLOAN material requests, ensure no Mediated request has been created, ensure no Request has been created in the Requests app of the University, Consortium, College tenant
For staff members working in the University tenant, related to OLOAN material requests, ensure no Mediated request has been created, ensure no Request has been created in the Requests app of the University tenant
*For Staff members authorized to work with Congressional patron data, please convert steps 3-17 to use the Mediated requests workflow, beginning the process with the Mediated requests app. vs. using FOLIO’s Requests app.
Edit an Active patron to be Inactive and attempt to create a Request / Mediated request
Log in to UAT environment
Open the Users app in the Central tenant, or University tenant for staff members working with Secure patrons
Select an Active patron from the “Test patrons” list above
Click “Actions” button, “Edit”, and change the “Status” of the Patron to “Inactive”
“Save & Close” button should be active, Click it
Transition to the Requests app and click “Actions” button
Select “New” option
Uncheck “Create title level request” checkbox (if checked)
Enter item barcode in “Item barcode” field
Press or click on “Enter” keyboard button
Enter patron user barcode in the “Requester barcode” field
Press or click on “Enter” keyboard button
Select “Page” request type from “Request type” dropdown
Select any service point from “Pickup service point” dropdown
Click “Save & close” button
Note Error toast that appears
Expected result is “This request was not placed successfully”
Note if the “New request” form is displaying
Click “Cancel”
Expected result is “New request” form is closed
Ensure no Request has been created in the Requests app of the Consortium or College tenant
For staff members working in the University tenant, related to non-OLOAN material requests, ensure no Mediated request has been created, ensure no Request has been created in the Requests app of the University, Consortium, College tenant
For staff members working in the University tenant, related to OLOAN material requests, ensure no Mediated request has been created, ensure no Request has been created in the Requests app of the University tenant
*For Staff members authorized to work with Congressional patron data, please convert steps 3-19 to use the Mediated requests workflow, beginning the process with the Mediated requests app. vs. using FOLIO’s Requests app.