Update Ticket History Job Frequency

Kristine Astop $organization over 9 years ago

Hello! This is probably a silly question, but currently we have a job that runs the update ticketing history procedure once a day. Would there be any harm with running it once an hour? I'm trying to implement a subscriber add-on discount pricing rule with exclusion list based on # of tickets purchased per production. We currently only allow our subscribers to purchase 10 additional discounted tickets per production (we have five mainstage productions per season). The exclusion list would definitely help, but I am getting tripped up in my implementation because the ticket history is only updated once a day... this doesn't really help with our real-time online purchases. I'm just worried that making it update hourly may bog down the system... but I am not sure. Thank you! Kristine

Parents

Michele Keutsch $organization over 9 years ago

Kristine, Can you use Orders rather than Ticket History to pull your exclusion list? Michele
Cancel
Vote Up 0 Vote Down

Sign in to reply

Cancel
Kristine Astop $organization over 9 years ago in reply to Michele Keutsch

Hi Michele, I'm not sure. I can't find anything related to order history within our List Manager attributes. Also, Order History doesn't seem to identify pricing rules (which the exclusion list needs). Now, admittedly, I am pretty new to Tessitura and may just be missing the obvious. :)
Cancel
Vote Up 0 Vote Down

Sign in to reply

Cancel

Reply

Kristine Astop $organization over 9 years ago in reply to Michele Keutsch

Hi Michele, I'm not sure. I can't find anything related to order history within our List Manager attributes. Also, Order History doesn't seem to identify pricing rules (which the exclusion list needs). Now, admittedly, I am pretty new to Tessitura and may just be missing the obvious. :)
Cancel
Vote Up 0 Vote Down

Sign in to reply

Cancel

Children

Michele Keutsch $organization over 9 years ago in reply to Kristine Astop

I didn't have Tessitura open earlier when I responded, but just realized that we've created a local view that combines a bunch of data from different tables into an orders table. (ie: price type, customer, order #, comp code, perf code, perf #, perf date, time slot etc.) We do not currently have anything related to pricing rules in there, but aren't using pricing rules yet either. I anticipate that once we begin using we'll be adding that into this view.

[edited by: Michele Keutsch at 4:03 PM (GMT -6) on 20 Jan 2017]
Cancel
Vote Up 0 Vote Down

Sign in to reply

Cancel