Details
-
Story
-
Status: Closed (View Workflow)
-
P2
-
Resolution: Done
-
None
Description
Purpose: We've had bulk renewals of loans in place for some time, but have only recently implemented logic that could cause renewals to fail (because we are now connecting loan policies with loans). The fact that renewals can sometimes fail means that we need the ability to provide a confirmation message that tells users which of the items that we attempted renewal on could be renewed and which failed (and for what reason/reasons)
User story: As a user who is has attempted a bulk loan renewal, I want to know which loans were successfully renewed and which failed (and why)
Scenarios:
- Scenario
- Given I select more than one loan from Users > Loans
- When I click the renew button
- Then I should see a bulk renewal popup as shown in the linked mockup
- Header: Renew confirmation
- Subtext below header: X items not renewed. X items successfully renewed.
- Failed renewal subtext should be accompanied by a red exclamation point icon.
- Successful renewal subtext should be accompanied by a green checkmark icon.
- Column headers:
- Renewal status - Default primary sort (failures at top)
- Title - Default secondary sort
- Item status
- Due date
- Requests CB: Please use Requests instead of Request queue, even if that's shown in the mockup
- Barcode
- Call number
- Loan policy
- All columns are sortable by clicking on the column header
- Follows standard sort patterns in FOLIO:
- Second click does reverse sort
- Previously sorted column becomes secondary sort
- Follows standard sort patterns in FOLIO:
- Scenario
- Given Loans A and B can be successfully renewed
- When I bulk renew loans A and B from Users > Loans
- Then I should get a bulk confirmation popup as shown in the mockup with the following details:
- Subtext below header: 2 items successfully renewed.
- Renewal status: Item successfully renewed
- Scenario
- Given Loans A can be successfully renewed and Loan B cannot for any reason such as:
- The loan has reached the renewal limit specified in the loan policy (
UIU-448) - The renewal date for Loan L does NOT fall within a date range in Fixed due date schedule associated with the loan (see
UIU-433andUIU-449) - Renewing on this date will not update the due date so renewal is prevented (
UIU-429)
- The loan has reached the renewal limit specified in the loan policy (
- When I bulk renew loans A and B from Users > Loans
- Then I should get a bulk confirmation popup as shown in the mockup with the following details:
- Subtext below header: 1 item not renewed. 1 item successfully renewed. CB: Note the use of singular "item"
- Loan A Renewal status: Item successfully renewed
- Loan B Renewal status: Item not renewed
- Given Loans A can be successfully renewed and Loan B cannot for any reason such as:
- Scenario
- Given I click on the Item not renewed status
- Then I should display a popup explaining why the item has not been renewed using the renewal reasons outlined in
UIU-484. (Additional renewal reasons will be specified going forward as stories that can result in failures are written)- Format: Loan can't be renewed because: <RenewalFailureReason1>, <RenewalFailureReason2> and <RenewalFailureReason3>. See <LoanPolicyAssociatedwLoan> for more information.
- NOTE: A renewal failure reason should populate for each reason the renewal failed. Ideally, they would be comma separated with an "and" before the last reason, but if that's too difficult to program, we can just list them with commas.
Mockups: https://drive.google.com/drive/folders/1w147VyfL1CpmErP4eEg7cN1RZyul7bXh
TestRail: Results
Attachments
Issue Links
- blocks
-
UIU-467 Truncate Renewal Period According to Fixed due date schedule (due date limit)
-
- Closed
-
- relates to
-
FOLIO-1101 Move Renewal Due Date Logic to the Server
-
- Closed
-
-
UIU-484 Multi-Reason Renewal Error Popup for Single-Loan Renewal
-
- Closed
-
-
UX-171 UX: User Feedback for Bulk Actions That Partially Succeed
-
- Closed
-
-
UXPROD-273 Loan Policy: Impact on loans part 1 (Q2 2018 release)
-
- Closed
-