Hello! I am just beginning to experiment with the Recipient field in the sub line item tab. I can think of a few different uses that it seems like a good fit for. I'm surprised though that I can't see the activity anywhere on the constituent record of the person/organization marked as the recipient. I was expecting it to show up in their orders or at least their ticket history. I also heard in a conference session recently that you should be able to produce a recipient report. Is anyone doing this (perhaps people with camp programs)? Where in Tessitura can you see evidence of the recipients besides on the order itself? Any suggestions would be appreciated.
Hi all! Thanks for all your assistance. I had been trying this in our Test system, and it wasn't showing up in Ticket History. After discussing the procedure TP_UPDATE_TICKET_HISTORY that John mentioned with my colleague, we remembered that there are a lot of things that just don't run correctly in our Test system (like merge functions, for example). Does anyone else have this problem with things not working the same in their test systems?
I tried it in our Live system, and it did indeed show up in Ticket History the next day!
Things have always WORKED for us in the TEST system identically as they have in the LIVE system for us excepting a few things below:
1) Obviously if you have not done a LIVE - TEST copy recently, there could be data that looks weird because it is simply not there in TEST.
2) Anything that would normally get caught with standard nightly procedures in LIVE will likely NOT get updated in TEST (following that last LIVE - TEST copy). Unless you have scheduled some procedures to run in your TEST environment, which I think would be a little unusual (excepting standard syspolicy and RAMP type procedures (if you are on RAMP)), your TEST environment will just sit there.
3) All credit card information is deleted so that people are not accidentally charging real cards when working in the TEST environment, because that charge WILL go through; also, it is just good practice. Always best to use the fake credit card numbers in TEST.
4) Some reports, especially the InfoMaker reports (the green icon, not the blue icon, that is SSRS) will not have definitions in both LIVE and TEST and as such, will not work in TEST. That can be easily fixed by copying the report definition from the LIVE instance to the TEST instance through InfoMaker, but that will need to be done manually and is outside the realm of the LIVE - TEST copy.
5) Sometimes, depending upon your set-up, you could have trouble sending e-mails from TEST. Ours is set up to send e-mails now, so that works just fine for us, but I know we had to make that change in the past. Then of course, you have to make sure your staff do not really send a fake e-mail confirmation to a person outside of the organization (which did happen here; fun conversation there).
I think that is it. If anything else outside of the above is not working the same way in TEST as it is in LIVE, I would talk to someone at Tessitura, because it should otherwise be responding identically, though possibly slightly slower.
Courtney, Are you on RAMP or Locally Hosted. If RAMP, ask the RAMP team about the running of "Stored Procedures". Many or most automatic stored procedures that run on Live are turned off in your test environment. This would explain why things like Ticket History and Merges are not working. You may be able to request that these procedures be turned on for testing.