Patron block is not triggered automatically (OKAPI)

Description

Any automated patron block doesn’t appear automatically
The issue exists on the snapshot env and Ramsons bugfest
to reproduce please try to execute TC11020
https://foliotest.testrail.io/index.php?/cases/view/11020


ENV: https://bugfest-ramsons.int.aws.folio.org
diku_login: 'folio'
diku_password: 'folio'

Steps:

  1. Create new patron group in https://bugfest-ramsons.int.aws.folio.org/settings/users/groups

  2. Start creation of new user

  3. Patron group from step 1 should be selected for the new user

  4. Set all another required fields correctly

  5. Save new userCreate a

  6. patron block “condition” at Settings>Users>Conditions, for 'Maximum outstanding fee/fine balance'

  7. Select to block borrowing, renewals and requests, plus enter the message to be displayed

  8. Save new condition

  9. .Create a patron block “limit” at Settings>Users>Limits, for patron group created in step 1

  10. .Enter a limit of 99.99 for 'Maximum outstanding fee/fine balance'

  11. Save new limit

  12. Create new fee/fine owner at Settings>Users>Owners

  13. .Enter owner name and save new ownerCreate

  14. a manual fee/fine type for fee/fine owner created in step 13 at Settings>Users>Manual charges

  15. Enter fee/fine type of “Misc fee/fine” and default amount of 100.00

  16. Save new manual charge

  17. Open user details for user created in step 5

  18. Select “Create fee/fine” from the ACTIONS menu

  19. Select fee/fine owner created in step 13 and tee/fine type created in step 14

  20. Save new fee/fine as "Charge only"

Expected result: User details now displays “Patron has block(s) in place” on top, a red icon next to the patron blocks sub-section and a row in the patron blocks table (as shown in screen print below), see attached to test screenshot

Actual result: Automated patron block doesn’t appear automatically

CSP Request Details

1. Describe issue impact on business - Without this work automated blocks will not be placed on user accounts. The blocks include for fines, and overdue recalled loans. 2. What institutions are affected? (field “Affected Institutions” in Jira to be populated) -- ALL INSTITUTIONS -- 3. What is the workaround if exists? -- None really.. Libraries, if they have an LDP may be able to generate reports to find users that should be blocked and place manual blocks on their accounts. they would then need to be manually removed. for larger institutions this is not feasible. 4. What areas will be impacted by fix (i.e. what areas need to be retested) - Automated patron blocks. 5. Brief explanation of technical implementation and the level of effort (in workdays) and technical risk (low/medium/high) - Low (already completed) 6. Brief explanation of testing required and level of effort (in workdays). Provide test plan agreed with by QA Manager and PO. - QA tstins is complete, PO testing is still needed and would be less then half a day. 7. What is the roll back plan in case the fix does not work? - the code woudl be rolled back to a previous state.

CSP Rejection Details

None

Potential Workaround

None

Attachments

6

is cloned by

relates to

Checklist

hide

Activity

Show:

Oleksandr Hrusha 2 days ago

Tested on https://folio-snapshot.dev.folio.org/, works as expected

Alexander Kurash last week

PubSub needs to declare these permissions from mod-patron-blocks

also, check permissions from other modules like mod-feesfines

Thomas Trutt March 17, 2025 at 5:47 PM

Thanks should this be moved back to In progress?

cc

Oleksandr Hrusha March 17, 2025 at 2:04 PM
Edited

Looks like issue still exists on https://bugfest-ramsons.int.aws.folio.org/

CC:

JenkinsNotifications March 17, 2025 at 1:01 PM

Deployed to the Ramsons bf env. Moved status to In bugfix review from status Awaiting deployment. Please proceed with the verification.

Done

Details

Assignee

Reporter

Priority

Story Points

Development Team

Vega

Fix versions

Release

Ramsons (R2 2024) Service Patch #1

RCA Group

TBD

CSP Approved

Yes

Affected Institution

!!!ALL!!!

TestRail: Cases

Open TestRail: Cases

TestRail: Runs

Open TestRail: Runs
Created January 13, 2025 at 5:46 PM
Updated 2 days ago
Resolved 2 days ago
TestRail: Cases
TestRail: Runs