Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

Cant save changes to circ rules in BugFest due to error

Description

Steps to repro:

  1. Log into https://bugfest.folio.ebsco.com/ as folio/folio

  2. Go to Settings > Circulation > Circ Rules

  3. Add a valid row to the bottom such as: m electronic-resource: l 2-1 r allow-all n send-notices

  4. Attempt save

Expected: Should save

Actual: Get error message up under the priority row reading "mismatched input 'g6399967d-9901-4cb8-bbf7-449e8b453616' expecting CRITERIUM_LETTER" I don't know how to resolve this error. I have compared the priority line with what is showing in the folio-snapshot and they seem identical. I have tried re-typing the priority line. Nothing is working.

Additional info: This is blocking BugFest testing.

CSP Request Details

None

CSP Rejection Details

None

Potential Workaround

None

Attachments

4

Checklist

hide

TestRail: Results

Activity

Show:

Cate Boerema September 24, 2019 at 7:56 AM

Thanks ! It seems we need to make location code required on the backend so we don't run into this in the future: UITEN-60

I will close this, as I verified that I could edit circ rules in BugFest.

Thanks again !

Kruthi Vuppala September 23, 2019 at 5:19 PM
Edited

Also, the record was added to specifically test if "CODE" is mandatory

Kruthi Vuppala September 23, 2019 at 5:09 PM
Edited

The issue is fixed now, and I am able to save the circulation rules
The root cause was, one of the location did not have a CODE specified. The screenshot shows the record I had to modify


Although it it not possible to create a location without code from the UI now, I think it was added to the DB directly

Cate Boerema September 23, 2019 at 6:53 AM

Thanks for the update . If you are working on this, can you please mark it In progress? Thanks!

Kruthi Vuppala September 20, 2019 at 9:36 PM

Update: I cleaned up the 2 versions, and also made sure the latest version is deployed, which did not resolve it
Still looking into the issue.

Done

Details

Assignee

Reporter

Labels

Priority

TestRail: Cases

Open TestRail: Cases

TestRail: Runs

Open TestRail: Runs
Created September 20, 2019 at 10:09 AM
Updated September 24, 2019 at 7:56 AM
Resolved September 24, 2019 at 7:56 AM
Configure
TestRail: Cases
TestRail: Runs