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

    UB: routing slip not generated upon processing callslip

    • Article Type: General
    • Product: Voyager
    • Product Version: 2001.2

    Description:
    Bug Report for Issue # 17341

    Module: CallSlip
    Other Modules that are affected or might have an affect: circ
    Release(s) - indicate both first reported in and most recent replicated in: 2001.2.1 we do not
    have a test UB Unicode environment at this time
    PC O/S (if this is PC specific): All
    Server Platform(s) affected: All
    Browser type & version (if WebVoyage):
    Loss of functionality from (previous version or prior build):

    Expected Results:
    routing slip prints in CallSlip when a UB Request: Normal Charge is processed in callslip.exe

    Actual Results:
    no routing slip prints in CallSlip when a UB Request; Normal Charge is processed

    Workflow implications:
    routing slips not being printed in CallSlip cause confusion as to where the item should be
    routed to for pickup. Discharging UB items in Circ does produce a routing slip but it also changes
    the item's status 10 (In transit on hold) to a 9 (In Transit Discharged. The details regarding item
    status being changed is reported in another bug. The changing of the status causes the error "unable
    to discharge item" at the pickup location.

    Replication steps:
    1. opened test WebV
    2. searched db1 for item via simulsearch
    3. logged in as db1 patron
    4. requested db1 item to be picked up at gwcc circ desk
    5. opened db1's callslip.exe--printed form
    6. processed request--NO FORM PRINTED in callslip.exe
    7. discharged book from db1's circ desk--routing slip printed
    8. opened circ desk at db2, discharged item hold slip printed.

    Other information (ie SysAdmin settings):N/A

    Resolution:
    Problem no longer occurs in 7.2.2.[8/9/2010 11:53:44 AM Julie Bister]


    • Article last edited: 10/8/2013