Voiding Batch Ticket Prints

Hello again,

So sorry....I re-read your question and I don't think what happened to us
today is the same problem you're having, unfortunately. Our problem was a
hardware issue with our BOCA (it started eating tickets mid-batch print).
Rather than continue to use the same BOCA to finish the print we decided to
reprint the entire batch on a different BOCA, so all we did was delete the
job from the bad BOCA's printer properties queue.

If you're asking about deleting the Event Desc "Printing" at the perf level
of an order (or, for lack of a better way to describe it, "unprinting" the
bad tix) I can't say we've ever had to do that. Not sure that it's
possible, but if you open a ticket with the network you'll know for sure!

Good luck,
Mary




"Beth Hawryluk"

luk7830@tessitura To
network.com> mmueller@lyricopera.org
Sent by: cc
"Tessitura
Ticketing Forum" Subject

@tessituranetwork Voiding Batch Ticket Prints
.com>


07/07/2011 02:58
PM


Please respond to
"Tessitura
Ticketing Forum"

@tessituranetwork
.com>






Hi Tessitura friends!


I'm assuming by the lack of response that no one has an answer for me.


However, if someone has been holding back I could really appreciate any
feedback you might have regarding voiding a ticket batch that has gone
horribly wrong.


This has just happened right now and I'm not sure what to do. The batch
parameters were incorrect and the person printing the batch didn't notice
until it was far too late.


Help?!


Thanks :(


From: Beth Hawryluk
Sent: 5/9/2011 4:27:51 PM


I'm wondering if anyone has ever had the need to void printed tickets and
how you did it.


Reading the documentation on Batch Printing I didn't see anything
referencing a "what to do if you mess it up" scenario. Sometimes it's a
human error thing (I printed a whack of tickets that I shouldn't have
printed...) but sometimes it's because our Boca printer decided to have a
temper tantrum and print the tickets wrong or not print them at all.


Our ticket types have a Reprint flag on them which we are not interested in
getting rid of. So if we simply reprint the batch then all of the tickets
that were previously printed will have the Reprint flag on them.


So what has everyone else done in the case of "this batch really didn't
work the way it was supposed to"? I refuse to believe I'm the only one that
has problem batches every once in a while. :)





This message was sent automatically to you by www.tessituranetwork.com
because you subscribed to the Tessitura Ticketing Forum. You may reply to
this message to post to the Ticketing forum or visit the site to search,
read and post to the forums. In the interest of keeping the forum posts
from becoming cluttered, we encourage you to delete previous message text
from your reply before sending. Thank you!

Hello again,

So sorry....I re-read your question and I don't think what happened to us
today is the same problem you're having, unfortunately. Our problem was a
hardware issue with our BOCA (it started eating tickets mid-batch print).
Rather than continue to use the same BOCA to finish the print we decided to
reprint the entire batch on a different BOCA, so all we did was delete the
job from the bad BOCA's printer properties queue.

If you're asking about deleting the Event Desc "Printing" at the perf level
of an order (or, for lack of a better way to describe it, "unprinting" the
bad tix) I can't say we've ever had to do that. Not sure that it's
possible, but if you open a ticket with the network you'll know for sure!

Good luck,
Mary




"Beth Hawryluk"

luk7830@tessitura To
network.com> mmueller@lyricopera.org
Sent by: cc
"Tessitura
Ticketing Forum" Subject

@tessituranetwork Voiding Batch Ticket Prints
.com>


07/07/2011 02:58
PM


Please respond to
"Tessitura
Ticketing Forum"

@tessituranetwork
.com>






Hi Tessitura friends!


I'm assuming by the lack of response that no one has an answer for me.


However, if someone has been holding back I could really appreciate any
feedback you might have regarding voiding a ticket batch that has gone
horribly wrong.


This has just happened right now and I'm not sure what to do. The batch
parameters were incorrect and the person printing the batch didn't notice
until it was far too late.


Help?!


Thanks :(


From: Beth Hawryluk
Sent: 5/9/2011 4:27:51 PM


I'm wondering if anyone has ever had the need to void printed tickets and
how you did it.


Reading the documentation on Batch Printing I didn't see anything
referencing a "what to do if you mess it up" scenario. Sometimes it's a
human error thing (I printed a whack of tickets that I shouldn't have
printed...) but sometimes it's because our Boca printer decided to have a
temper tantrum and print the tickets wrong or not print them at all.


Our ticket types have a Reprint flag on them which we are not interested in
getting rid of. So if we simply reprint the batch then all of the tickets
that were previously printed will have the Reprint flag on them.


So what has everyone else done in the case of "this batch really didn't
work the way it was supposed to"? I refuse to believe I'm the only one that
has problem batches every once in a while. :)





This message was sent automatically to you by www.tessituranetwork.com
because you subscribed to the Tessitura Ticketing Forum. You may reply to
this message to post to the Ticketing forum or visit the site to search,
read and post to the forums. In the interest of keeping the forum posts
from becoming cluttered, we encourage you to delete previous message text
from your reply before sending. Thank you!

lol Well thank you very much for checking! Sorry to hear about your misbehaving BOCA.

Actually, after re-checking the batch parameters I don't think it's too big of an issue so I'm not worried now. But opening a ticket to find out would definitely be a smart way to go I think.

 

Thanks again!