Circ Rules and Loan Policies
(UXPROD-789)
|
|
| 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:
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
Out of scope
Use case(s) Proposed solution/stories Links to additional info Questions
|
| 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. |