ILLiad Known Issues
4 results found
-
Client work form leaves phone/fax & email blank for constant data workaround for this issue is available through the Workformapping in the Customization Manager. See details here: https://support.atlas-sys.com/hc/en-us/community/posts/360050022954-Adding-Email-and-Fax-Information-to-Constant-Data-for-OCLC-Requests
Bug# 7924
0 votesClosed due to not being an ILLiad bug.
OCLC has confirmed an issue with constant data for email and phone/fax fields in the web service. They are expecting to have a fix in their December release. In the meantime, Heather’s workaround in the comments below should help anyone relying on those fields from ConstantData.
-
Clones original request instead of request with staff changes When the user goes back into the web and clones the request again, it takes them back to the loan request page and submits a loan request without any changes staff made to the original request. This occurs for situations where a user creates a loan request on the web and staff changes the loan request to an article request and updates the doctype, then fulfills the request.
Bug# 8345
0 votesThis works as created. The enhancement request has been added to the ideas section of UserVoice. To vote on the idea, go to this link: https://uservoice.atlas-sys.com/forums/581665/suggestions/42416338
-
Article Exchange Documents not Delivered when Odyssey Trusted Sender is set to Always Documents delivered via Article Exchange are getting stuck in Awaiting Odyssey Processing even though the Customization Manager key ArticleExchangeTrusted is set to Always and Override Trusted Sender is NOT checked in the Lender Address record.
Bug# 4837
0 votesThis issue is resolved by ensuring that patrons have the proper Electronic Delivery method configured. See the “Enabling the Electronic Delivery Method for Patrons” section in the OCLC Article Exchange Receiving article for more information: https://support.atlas-sys.com/hc/en-us/articles/360011808234
-
Lender password change from client only changes the password for NVTGC logged into client When a user changes a Lender's password from the ILLiad client, it only changes the password for the NVTGC that the user is logged into the client under, instead of changing it for all NVTGCs. As a result, the lender may be able to log into the client under that particular NVTGC but unable to log into the web.
We don't think this is a bug. It is currently working as desired (if you are using LenderAddressesALL and views to have your own list of lenders, it should only be updating the password for your lender). KB created for the…
0 votesClosed due to desired functionality can be achieved if you are using LenderAddressesALL and views to have your own list of lenders. The info was added to the following KB: https://support.atlas-sys.com/hc/en-us/articles/1500000433001
