Attention needed in mailer, with no information for user on how to fix it

[saseestone]

Need to figure out all the scenarios when we are showing this to the user, and if we can give the user better information.

Formatting of the "attention needed" in the body of the email is not great. More details coming...

[saseestone]

Jira issues where this is reported:

• SW-4226 - Chris determined that Page requests are not allowed for this patron and item combination

Scenarios reported, but shouldn't happen after we move Hold/Recall request types to ILLiad:

• SW-4222 - Item was "Aged to Lost".

Based on errors today, Chris saw in the logs that we might see issues for On Order items. Error reason is: "Cannot create page TLR for this instance ID - no pageable available items found", but Chris verified we're sending a title level hold request at the instance level. So we need to figure out why FOLIO is erroring with a message about paging an item.

Also in errors from today, we saw reason: "This requester already has an open request for this instance", we should show a message to the user in the body of the confirmation mailer.

Text forthcoming for all these scenarios...

[saseestone]

For reason "This requester already has an open request in this instance"

• can we send the confirmation mailer as a success and suppress "Attention needed" in the subject line and at the item level in the mailer body? I believe that is parity with what we did w/Symphony.

For "Page requests are not allowed for this patron and item combination"

• can we continue to show "Attention needed: There was a problem with your request [insert title]" in the subject line.
• In the body of the text, next to the item, can we display "Attention needed: There was a problem with your request. Please use the contact information listed below to contact a library staff member about the issue."

Still trying to assess if there are more scenarios that we need to account for.

[saseestone]

Closing this issue since it pre-dates the Requests 2024 workcycle, and we're handling this another way.