Hebis. Reminder fee. When 0 EURO then the dash in the billed column, cause Bulk payment of Fee/Fines to fail

Description

Overview: Implement circulation module logic for setting charge amount to 0 EURO (or other currency) for reminder fee(s) when entering the Fee value. When paying all outstanding fee/fines, and one or more of the billed actions has the amount 0 charge, and in the billed column this is expressed with a '-' then the bulk payment fails.

Steps to reproduce:

  1. Log in to FOLIO Snapshot as user Diku_admin

  2. Go to Settings > Circulation > Overdue fine policy, and select a Overdue fine policy

  3. When viewing the Reminder fee accordion in Edit mode

  4. Then for the Fee section, it is possible to enter the value 0 for the first reminder, 3 for the second, and 6 for the third reminder

  5. Check out a couple of items, and await to the reminders are being charged, and later a lost item fee is charged as well

Expected result:
When the user want to pay all of his outstanding fee/fines, it's possible to pay these using the toggle which will select all fee/fines and pay them as one transaction.
Solution: When the fee is set to 0 (zero), then there should not be created any fee.

Actual result:
The bulk payment function is failing with an error message, if one of the billed actions has the 0 amount. See attached screen dump

Update: 11/13/2023 now the Pay button is not active - don't know if this is a different problem or the same. Charlotte has added a comment in the #bug-fest channel

See e.g. following users in Poppy Bugfest:

  • user with user barcode: 7777777

  • user with user barcode: 009688115077

CSP Request Details

None

CSP Rejection Details

None

Potential Workaround

None

Attachments

5
  • 05 Dec 2023, 04:21 PM
  • 10 Nov 2023, 06:22 PM
  • 10 Nov 2023, 06:22 PM
  • 10 Nov 2023, 06:22 PM
  • 10 Nov 2023, 06:13 PM

Checklist

hide

TestRail: Results

Activity

Show:

Charlotte WhittDecember 7, 2023 at 2:36 PM

Manual test in Bugfest Poppy. The first reminder which is set to 0 Euro is not listed as to be billed with this change. All works as expected. Thanks

Charlotte WhittDecember 5, 2023 at 4:21 PM

Manual test in Poppy Bugfest: Test begun: 12/6/2023. User barcode: 7777777, item barcode: cw-1970. Following following circulations rule:

JenkinsNotificationsNovember 27, 2023 at 11:25 AM

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

Charlotte WhittNovember 15, 2023 at 11:03 AM

Hi - with the Poppy Bugfix deadline now moved to 12/1/2023 - I have pulled in this fix to be done for Poppy.
CC:

Charlotte WhittNovember 10, 2023 at 6:25 PM

Hi and - I'm not 100% sure if this is a back end or a UI issue.

How critical is this to fix - should we push for Poppy Bugfest fix or can it wait for Quesnelia. Right now I have given it a P3?

Done

Details

Assignee

Reporter

Priority

Sprint

Development Team

Odin

Fix versions

Release

Poppy (R2 2023) Bug Fix

RCA Group

Lack of testing

TestRail: Cases

Open TestRail: Cases

TestRail: Runs

Open TestRail: Runs

Created November 10, 2023 at 6:13 PM
Updated March 21, 2024 at 2:53 PM
Resolved November 21, 2023 at 12:05 PM
TestRail: Cases
TestRail: Runs

Flag notifications