UX: Success Confirmation for Actions on Loan(s)

Description

Purpose: Get UX guidance on how we can let users know that they have successfully taken action on one or more Loan on the Loans page.

Background:

  • This question is regarding the Loans page but I would expect we'd have similar needs elsewhere: https://www.dropbox.com/s/owyyqih5euj12jt/loan-history-open-4.png?dl=0

  • There are many actions you can take on this page both individually and in bulk. For example, Claim returned, Renew, Change due date etc.

  • The only action we currently have implemented is Renew and, if you go into folio-testing and renew an individual loan, you see that the due date is extended for that loan, but there is no confirmation that anything happened and you really wouldn't notice unless you knew where to look.

  • I think we need some kind of success confirmation message to display and I'm not sure if a pattern for that has already been established

  • Could UX please provide guidance here including, ideally, a mock-up?

Thanks!

Environment

None

Potential Workaround

None

Attachments

9
  • 01 Nov 2017, 05:16 PM
  • 01 Nov 2017, 05:16 PM
  • 01 Nov 2017, 05:16 PM
  • 01 Nov 2017, 05:16 PM
  • 01 Nov 2017, 05:16 PM
  • 01 Nov 2017, 05:16 PM
  • 01 Nov 2017, 05:16 PM
  • 01 Nov 2017, 05:16 PM
  • 01 Nov 2017, 05:16 PM

Checklist

hide

TestRail: Results

Activity

Show:

Cate Boerema November 2, 2017 at 4:49 PM

These are great, Darcy. I like the last 3 because they use similar styling as what John C's component is already using. I think we can mark this closed. Please re-open if you feel you need to do more work here.

Darcy Branchini November 1, 2017 at 5:18 PM

Variation on toast that allows for collapse/expand:

Darcy Branchini November 1, 2017 at 5:17 PM

Toast - As designed by primary UX team:

It's the last scenario that I'd like to get more information on. Is it important to see all the details at once? What's a realistic scenario regarding number of items, types of issues that come up? If only some of the items can be processed successfully, then should all of the request fail instead?

Darcy Branchini October 22, 2017 at 6:57 PM

I focused on bulk actions and the various outcomes - successes and errors. For a bulk action where only some of the items can be processed, should the entire bulk action fail? Or should it be partially processed? For example, if three items are selected for renewal but two of them have been recalled.

Confirmations will be handled with a toast. Mockups 3a & b and 4a & b reflect the pattern that's been already been identified by the FOLIO project team. Awaiting SIG feedback, however, at this point I'm assuming library staff would prefer to get to details regarding a bulk action success or error. I provided a modified version of the toasts (coming up from the bottom of the screen and can be expanded for details). These are mockups 5, 6 and 7.

https://www.dropbox.com/home/FOLIO%20UX%20Designs/Users/Loans%20and%20Loan%20Details/Bulk%20Actions

Done

Details

Assignee

Reporter

Labels

Priority

TestRail: Cases

Open TestRail: Cases

TestRail: Runs

Open TestRail: Runs
Created September 12, 2017 at 12:40 PM
Updated November 4, 2017 at 1:34 PM
Resolved November 2, 2017 at 4:49 PM
TestRail: Cases
TestRail: Runs

Flag notifications