Circ Rules and Loan Policies (UXPROD-789)

[UXPROD-3180] Show error messages in the Circulation Rules editor when rules set is first loaded in pane Created: 13/Jul/21  Updated: 13/Jun/23

Status: Draft
Project: UX Product
Components: None
Affects versions: None
Fix versions: None
Parent: Circ Rules and Loan Policies

Type: New Feature Priority: TBD
Reporter: Erin Nettifee Assignee: Cheryl Malmborg
Resolution: Unresolved Votes: 0
Labels: enettifee-reviewed
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Epic Link: Circ Rules and Loan Policies
Development Team: Vega
PO Rank: 0
Rank: Cornell (Full Sum 2021): R2

 Description   

Current situation or problem: The Circulation rules editor has an existing feature that validates rules and shows errors when a rule does not follow required syntax or a piece of a rule (like a policy) does not exist.

Currently, the error message(s) do not appear until a FOLIO user attempts to save the ruleset. So, a not-uncommon workflow happens like this:

  1. A FOLIO user removes a loan, overdue, lost item, request or notice policy;
  2. The FOLIO user goes to view the circulation editor to see if there are any rules that need to be edited (since deleting one of the relevant policies leaves the UUID behind in the rule);
  3. The FOLIO user does not see any error messages and assumes that the ruleset is fine.

In fact, there may be error messages from removing the policy, but the editor doesn't show them to you until you save the circulation rules. So you could miss an error that would influence circulation behavior later on.

This feature is meant to incorporate the work needed so that when a FOLIO user with appropriate permissions opens up the circulation rules editor, errors are checked for, and the first error found results in an error message.

In scope

  • When the circulation rules editor is loaded, check for errors using the same functionality that checks when rules are saved. If an error is found, display the error code inline (similar to current functionality.) (See question below about whether the rules editor should jump to the error if it is off the screen.)

Out of scope

  • Adjustments to the error checking code / script, including having it check for more than one error at a time (currently it checks for one error at a time.)

Use case(s)

Proposed solution/stories

Links to additional info

Questions

  • If the error is below the visible circulation rules when the page is first loaded (e.g., you'd have to scroll to get to it,) should the page scroll automatically to the rule? It does when you save the record.


 Comments   
Comment by Erin Nettifee [ 13/Jul/21 ]

Cheryl Malmborg I didn't see a jira for this already but noticed this feeling very clunky when cleaning up bugfest. Glad to talk more when you have a chance.

Generated at Fri Feb 09 00:29:58 UTC 2024 using Jira 1001.0.0-SNAPSHOT#100246-sha1:7a5c50119eb0633d306e14180817ddef5e80c75d.