Skip to main content
ExLibris
  • Subscribe by RSS
  • Ex Libris Knowledge Center

    2023 RN 12 Issues

    • December 2023 Acquisitions SF: 06963554 06989108 06977290 06959029 06991106 06564712 06993990 06989019 06990431 06964709 06967758 06988184 06972275 06967378 URM-211795
      In open predicted items, for weekly (52) or daily (365) patterns, the items were created with incorrect data. This was fixed. This was caused by a regression from the issue in the November release where weekly and daily prediction patterns did not count the next cycle correctly. That regression was cancelled from November and will be fixed in February.
    • December 2023 Acquisitions SF: 06842716 URM-206253
      Recently used reporting codes were not displayed. This was fixed and they are now displayed. Note that this only works when there are 10 or more items in the list box.
    • December 2023 Acquisitions SF: 06853972 06894334 URM-205138
      In the new UI, when trying to save a migrated PO Line where the Subscription interval was -1, the PO line could not be saved and an error message "Subscription interval field is invalid" was displayed. This was fixed.
    • December 2023 Acquisitions SF: 06873410 URM-207211
      An error message was displayed when rejecting a Purchase Request created from a citation, after the citation was removed. This was fixed.
    • December 2023 Acquisitions SF: 06916779 06958584 URM-207792
      When saving POLs in the new UI, an error would sometimes display: Acquisition method was not selected, please enter the required data. This was fixed.
    • December 2023 Acquisitions SF: 06950755 06950824 06950593 URM-209594
      When trying to create manual PO for PO Lines that are in "In Review" status and their "Manual packaging" indicator is checked - an error message was displayed. This was fixed and now a warning message explain the customer that the PO line is not in the correct status is displayed.
    • December 2023 Acquisitions SF: 06766995 URM-198754
      In some cases, the disencumbrance amount was a few KRW less than encumbrance/expenditure. This was fixed.
    • December 2023 Acquisitions SF: 06786441 URM-199602
      When the invoice lines tab in a PO Line was sorted by line number, in some cases some of the lines would disappear. This was fixed.
    • December 2023 Acquisitions SF: 06867353 06806833 URM-205213
      The Note column was not added to an invoice created from an Excel file. This was fixed.
    • December 2023 Acquisitions SF: 06877390 URM-206143
      There was no invoice payment date in fund transactions for an invoice marked as internal copy. This was fixed, and now if an invoice is marked as internal copy or prepaid, the invoice payment date in the fund transaction is updated when the invoice moves to the Closed status.
    • December 2023 Acquisitions SF: 06856305 URM-207621
      A mistake in translation was corrected for the following label: "Invoice Total Price is over {0}. It may require Managerial Approval".
    • December 2023 Acquisitions SF: 06898046 URM-207692
      In the Invoice Approval queue users were able to “assign to” users that could not approve them. This was fixed and now only users that have the "Invoice Manager" role appear in the list.
    • December 2023 Acquisitions SF: 06631090 06754707 05300329 URM-155048
      An error message was displayed when a Staff user at a customer tried to receive a specific PO Line. This was fixed.
    • December 2023 Acquisitions SF: 06773322 URM-206118
      The PO Line Claim Aggregated Letter subject was taken from the PO Line Claim letter. This was fixed.
    • December 2023 Acquisitions SF: 06756483 URM-195410
      Overencumbrance Limit Percent was not blocking the creation of the encumbrance transaction due to an error in calculation (the available balance was not taken into account). This was fixed.
    • December 2023 Acquisitions SF: 06815133 URM-203440
      In the new UI, after saving an order, there was a difference between fund and net price. This was fixed. The amounts now match and the (rounding) calculation is consistent in the UI and server. For example, in both calculations 47.405 = 47.41 (and not 47.40).
    • December 2023 Acquisitions SF: 06737831 URM-196836
      When a Vendor was changed on an invoice that had the vendor account populated, the change did not remove the vendor account from the invoice. This caused incorrect 'Vendor Account' information in re-exported invoice files for the ERP. This was fixed. Now, when the vendor is changed and the invoice is saved, Alma verifies that the vendor account is valid.
    • December 2023 Acquisitions SF: 06557556 URM-180280
      Previously, when the Change PO Line Status job was used to close PO lines for electronic resources, the PO lines were closed, but the job report said that they were skipped and could not be closed. This was fixed. Now the job report correctly states that these PO lines are closed.
    • December 2023 Acquisitions SF: 06855546 URM-207413
      In the Acquisition health check process, the "Reporting codes for funds and invoices/orders match" error did not hold the invoice number, only the invoice line number. This was fixed.
    • December 2023 Administration and Infrastructure SF: 06738500 06640552 URM-190055
      Previously After marking a loan as lost, the Advanced search for users with the "Fine/Fee total sum" field did not work properly. This was fixed.
    • December 2023 Administration and Infrastructure SF: 06738500 06640552 URM-207781
      Previously when doing an add/waive/dispute/restore fee without selecting the "Save" button, the Advanced search for users with the "Fine/Fee total sum" field did not work properly. This was fixed, and users can now add/waive/dispute/restore fees without having to select the "Save" button.
    • December 2023 Administration and Infrastructure SF: 05312403 05330237 URM-131691
      Certain links with special characters did not resolve correctly. This was fixed by creating a new customer parameter (temp_use_encode_uri_for_all_parsers). This customer parameter can be activated by Ex Libris Support.
    • December 2023 Administration and Infrastructure SF: 06819823 URM-199830
      General Configuration menu disappears from user with proper roles. This is fixed
    • December 2023 Administration and Infrastructure SF: 06854816 06859868 URM-203119
      Notes added to any "Other Settings" configuration table are incorrectly visible on all of the equivalent other settings tables. This was fixed and the Notes no longer appear.
    • December 2023 Administration and Infrastructure SF: 06853262 06862264 URM-204310
      It was not possible to search for translations in code tables. This was fixed by adding the search by "Translation" for Code Tables (relevant languages are displayed) and only applied in multi-language environments.
    • December 2023 Administration and Infrastructure SF: 06891657 URM-206805
      The "more action" text does not display when the cursor hovers over the ellipsis button. This was fixed
    • December 2023 Administration and Infrastructure SF: 06777632 URM-198851
      The number of standalone portfolios recommendations was different from the real number when pressing the link. This issue was fixed by updating the recommendations in the "Smart Recommendation Reflection Job".
    • December 2023 Analytics SF: 06709400 06846976 URM-192010
      After previewing an Alma report with the Analytics New Layout the Primo report previews did not work. This was fixed.
    • December 2023 Analytics SF: 06797041 06737107 06704635 06865123 06719836 06682513 06796047 URM-206884
      When exporting analytics reports, the reports never complete the export process. This was fixed by adding the RCOUNT(1) column to the report.
    • December 2023 Analytics SF: 06956025 URM-209646
      An incorrect value appeared for the Analytics Objects > Analytics Object Details > Scheduled Frequency field in analytics reports. This was fixed.
    • December 2023 Analytics SF: 06880726 06856644 URM-205038
      The report URL of analytics objects did not work if the report name contained diacritics. This was fixed.
    • December 2023 Analytics SF: 06875183 URM-207756
      Users with many roles assigned to them received an error message when clicking the Shared with Me link from the main Analytics menu. This was fixed.
    • December 2023 APIs SF: 06861816 URM-204402
      Performance improvements were done in the create loan API.
    • December 2023 APIs SF: 06817852 URM-204721
      In the Get Vendor API, the contact people from the vendor account were missing in the response XML. This was fixed.
    • December 2023 APIs SF: 06766918 URM-207843
      User block expiry time was changed by Update User Details API requests. This was fixed.
    • December 2023 APIs SF: 06845568 URM-207363
      The new PO Line task list did not support Cloud Apps. This was fixed
    • December 2023 Digital Resource Management SF: 06741566 URM-207111
      When accessing digital representations on a mobile device, the user was able to bypass the obtrusive copyrights by using the top toolbar. This was fixed.
    • December 2023 Digital Resource Management SF: 06900780 URM-207209
      Representations with access rights configured to not allow downloading were able to be printed by pressing CTRP+P. This was fixed, so now pressing CTRP+P does not print the representation.
    • December 2023 Digital Resource Management SF: 06675294 URM-207365
      In the Alma Viewer, some pages of PDFs were cut off at the bottom of the page. This was fixed.
    • December 2023 Digital Resource Management SF: 06595961 URM-189485
      Duplicate digital services appeared when selecting the View It link from Primo. This was fixed.
    • December 2023 Electronic Resource Management SF: 06820705 URM-202166
      Previous coverage in the portfolio editor is removed from the history tab when coverage is updated. This was fixed. The history now displays all of the previous changes.
    • December 2023 Electronic Resource Management SF: 06838917 URM-206370
      In collections management, when a name column was moved to the first column, the link in this column was redirecting to the wrong collection. This was fixed.
    • December 2023 Fulfillment SF: 06844213 06759154 URM-194816
      The Pick From Shelf page sometimes failed to open if there were very long call numbers that contained special characters. This was fixed.
    • December 2023 Fulfillment SF: 06684433 06762570 06730805 06708573 06847405 06681627 06947566 06956077 06731941 URM-192103
      In some cases, the Quick print dialog window for the Resource Sharing Shipping Slip Letter was not displayed as expected. This was fixed.
    • December 2023 Fulfillment SF: 06931958 06768588 06736512 06666558 URM-196657
      In some cases, the 'Loans - Due Date Correction after Calendar Change' job modified loans due date even though it did not fall on a closed day. This was fixed. Now, the loans due date is NOT recalculated when one of the following conditions is met: The library is open in the due date and the Regular Due Date policy specifies an exact hour. The library is open in the due date, the loan is a Resource Sharing loan and the ignore_lender_due_date Customer Parameter is false.
    • December 2023 Fulfillment SF: 06795512 URM-206550
      A new field was added to the XML of loan-related letters: loaned_at_library. It contains the name of the library where the loan was performed.
    • December 2023 Fulfillment SF: 05311949 06281313 06756119 06656620 05302120 06921394 URM-140217
      When changing the location of a digitization request, the pickup location is not recalculated. As a result, the pickup location is not the related location for the department. This was fixed.
    • December 2023 Fulfillment SF: 06720904 URM-197283
      Corrupted data caused creation of new requests to fail. Thiis was fixed. In addition, a check was added where if for whatever reason corrupted data does exist, it will not result in a failure to create new requests.
    • December 2023 Fulfillment SF: 06755377 06755364 URM-199517
      The Item history was displaying an incorrect Return circulation desk name. This was fixed for most cases. There is a specific case where the Return circulation desk name will be empty - this is still being resolved.
    • December 2023 Fulfillment – Resource Sharing SF: 06767740 URM-198752
      Using the create request form with the "send directly to partner" functionality resulted in trying to create a Rapido request with an offer, even though a partner was chosen for the request. This was fixed and the regular send directly to partner workflow used.
    • December 2023 Fulfillment – Resource Sharing SF: 06873339 URM-206593
      For a certain borrowing request, the customer received an error when trying to reject a partner with the "Other" reason. This was fixed.
    • December 2023 Fulfillment – Resource Sharing SF: 06872486 URM-205148
      Manually marking a borrowing request as 'lost' would fail in some cases with an error. This was fixed.
    • December 2023 Fulfillment – Resource Sharing SF: 06620792 URM-196056
      Special characters in the 'atitle' caused differences in the target URL between SFX and Alma so that it did not resolve correctly. This was fixed.
    • December 2023 Physical Resource Management SF: 06885713 URM-206880
      When trying to run the Job Change "Physical items information" job, in the form Use Receiving number sequence / Use Weeding number Sequence, the "Select" button throws an error message. This was fixed.
    • December 2023 Resource Management SF: 06863747 URM-206031
      General Publishing > When publishing in 'Binary' format and selecting 'Include all records each time file is published', the finalizing phase sometimes took a long time to complete. This was fixed and the finalizing phase was improved.
    • December 2023 Resource Management SF: 06868929 URM-205954
      The utilization of Boolean nesting and 'Add Group' in the Advanced Search for Physical Holdings does not yield the expected results. This was fixed.
    • December 2023 Resource Management SF: 06790888 URM-201071
      The Hong Kong TSVCC characters conversion table was missing characters and needed to be enhanced. This was fixed by adding the missing characters (甯, 寗, 襍, 㱷, 䌖).
    • December 2023 Resource Management SF: 06683144 06790824 URM-189939
      Bib records with dual appearances of headings, one without subdivisions and the other with, experienced a full linking error for the latter. This caused the removal of subdivisions during the preferred term correction job. The issue has been rectified, ensuring that headings with subdivisions are now partially linked, and the subdivisions persist after the preferred term correction job. Importantly, the fix is safeguarded by the default-enabled customer parameter "temp_ptc_strips_subdivisions_fix."
    • December 2023 Resource Management URM-195300
      NACSIS Cloud App: The Shipping cost field was erroneously editable by the borrower. This was fixed and editing of this field is blocked for borrowers in all borrowing request forms.
    • December 2023 Resource Management URM-199801
      Numerous accessibility issues were reported pertaining to the Metadata Editor Records and Indication Rules Forms. All the reported issues (too numerous to list individually) were rectified.
    • December 2023 Resource Management SF: 5311740 05330440 05767812 05835863 URM-93797
      Facets counters issue in Holdings search and Physical items search. There was a difference in numbers between the facet and the displayed results. This was fixed.
    • December 2023 Resource Management SF: 06748296 06833004 URM-198726
      UNIMARC: F3 does not find authority and bib headings for the field 500 and does not link the headings. This was fixed by adding a new customer parameter: 'unimarc_uniform_title_headings_split'. When set to 'true' - F3 opens different lists for 410 (Series) and 500 (Uniform title). When set to 'false' - F3 opens a combined list for 410 (Series) and 500 (Uniform title). The default value is 'true'.
    • December 2023 Resource Management SF: 06687592 URM-191830
      SBN contribution of parent records - When '463' fields are removed in Alma, the record was changed to a regular record (instead of parent record) upon contribution. This was fixed. Now, when the new customer parameter 'sbn_dont_update_parent_links_upon_contribution' is set to 'true', the record remains a parent record after the contribution.
    • Was this article helpful?