Hello all -
We're using a third party to help with price changes and revenue management on ticketing prices now. To aid their programming, all price changes need to be done through their software rather than in Tessitura itself. To try to keep that clean and troubleshoot potential issues, I'm looking for a 'last_updated_by' field on price events but I'm not seeing one in either T_PRICE_EVENT or T_PERF_PRICE. Is this logged anywhere so we can see who made a pricing change or am i missing a table or just out of luck?
Thanks!
RJ
RJ,
I will rarely ever argue against additional audit columns such as you stated above. And I can definitely agree that they make sense to be included on T_PERF_PRICE; seems like information I certainly would want to have saved somewhere for adjustments to the home prices. I can only assume that the reason they were not included is that there is no way to view them from within the application (to my knowledge). Still, from the notion of a complete database construction, I certainly agree that it would be nice if some future update added them in.
Regarding T_PRICE_EVENT, while, as I said above I cannot argue AGAINST their inclusion, for those I would be more wanting to see the "created_by" field. After all, for price events, I would assume, more often than not, instead of editing an existing event, you would instead simply create another event on the same performance/zone/price type/price layer grouping at that later date undoing/updating what had already been done. While it might feel redundant of course, there is no reason you cannot put price events down one after another continually doing and undoing some pricing change, and at least then you would have THAT record of what was done, if you cannot actually see who did it. (Again, through the database as I am also unaware of any way to see this information in the application as well, though there is the price event log for this information which seems like it would be easily adaptable to add that in, unlike the pricing grid above which is already cumbersome.)
Anyway, no, you are not missing anything to my knowledge (or else we both are). Might be worth submitting as an idea. Probably not going to be the most popular of ideas, but really, this should be a ridiculously simple update, and if you get enough support, it might just get done. Even if the data is just hidden in the database and not available in the application.
John A. Moskal II
Thanks John - i suppose an enhancement request might be next... but there are like 5000 Tessitura sites now and their focus seems to be moving to the web to cut costs rather than adding new functionality. But it wouldn't hurt to try. Suppose for now I'm just out of luck. Thanks!