You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When a user in Alma who does not have a barcode logs into the request form the form should present them the options available to their Alma patron group even if they do not have a barcode value stored in Alma.
Actual behavior
If a user who has an active Alma account but does not have an assigned barcode, the request forms generates a HTTP 500 error screen.
Steps to replicate
Have credentials for a user who is active in Alma but that does not have an assigned barcode. See lastpass for a test user in this state.
2 Visit a Show page of an item which requestable copies
Click the request button
Acceptance Criteria
A test Alma user is created that is active but does not have a barocde.
The request page responds without an error when a user in this state visits one.
Impact of this bug
Users whose accounts are in this state have a confusing user experience.
Accounts in this state (Active User, no assigned barcode) are very rare and are mostly in the CASUAL Hourly patron group that is not eligible for any request services.
Need to reach out to someone in the Alma Tech Team to create a test user in the Alma sandbox and production environment that meets these parameters, since no one on the DACS team has the correct privileges to do so.
The text was updated successfully, but these errors were encountered:
Expected behavior
When a user in Alma who does not have a barcode logs into the request form the form should present them the options available to their Alma patron group even if they do not have a barcode value stored in Alma.
Actual behavior
If a user who has an active Alma account but does not have an assigned barcode, the request forms generates a HTTP 500 error screen.
Steps to replicate
2 Visit a Show page of an item which requestable copies
Acceptance Criteria
Impact of this bug
Users whose accounts are in this state have a confusing user experience.
Honeybadger link and code snippet, if applicable
See https://app.honeybadger.io/projects/54399/faults/113847454
Implementation notes, if any
Accounts in this state (Active User, no assigned barcode) are very rare and are mostly in the CASUAL Hourly patron group that is not eligible for any request services.
The text was updated successfully, but these errors were encountered: