Version 7.32.00

Theatre Manager will

• Change the toolbar fields to handle OS-X Leopard compatibility which requires clearing any saved preferences
• Recalculate any payments that are missing credit card fees. If you have not set these up, you may wish to do so before the upgrade.

The user will need to

7.32.00 Changes & Enhancements

Interface

• This release introduces new Leopard & Vista interface elements, especially around the toolbar display.

Reports

• The dynamic reports produced by printing a list field has been enhanced to reflect the current width of the fields in the list. Previously, it printed the report using the saved width of the list columns. This way a user can simply change the width of a column on the window and see it on the next report printed.
• The deposit detail report no longer prints address verifications information if a venue is not using that option.
• The deposit 'Check' listing report now prints the value of 'check' from the code tickets.
• Printing of raffle tickets has been added to this version.
• Automatically save the query for form letters. Each letter will have its own criteria saved.
• Criteria now allows a quick selection of the primary household patron, the non-primary patrons, or all patrons in a household for mail list building, letter merging and/or report queries.
• Added a timer to the criteria window - if you are typing in the name of a field and pause for 3/4 of a second, any fields that match the criteria will be displayed automatically.
• Royalty Report by Payment Mthod - fixed a small issue so that the columns that appear on the report are the same as the columns selected in the criteria.

Form Letters

• Linked up the Format and View menus to work in conjunction with the palette for the documents.
• The batch merge process now defaults to show only letters for today and earlier in the criteria. You can remove the criteria and see all future merge letters if you wish - as they are ignored automatically during the merge process.
• A form letter is reloaded prior to the batch print so that it has the latest version.
• Editing letters in the batch merge process now saves the letter for all items in the batch merge list. Some could not be changed or saved because of how form letters were cached in the batch merge process. This has been fixed.
• There is now an icon column in the list of form letter/note history that shows the type and status of the notes.
• You can now edit form letters while view merged letters. Any letter that has not yet been merged will show the new letters contents next time it is viewed and/or when the merge happens
• Corrected a join condition for letters merges against an outlet database.
• The Form Letters-> Tasks process that is sued to print unprinted letters has received a number of enhancements
  • it now shows the letters status (customized or if it will use the current merge letter)
  • you can reset any letter that has been customized to use the current form letter (i.e. re-merges the form letter)
  • you can remove letters from the batch

Tickets Sales

• The custom ticket hold window now allows setting of any future date when tickets are to be automatically released
• Added a small comment in the list of events to indicate that the event is past performance (in addition to the entire performance line being 'blue')
• Changing an order from reservation only to an actual order now updates 'Deposit Date Due', 'Final Date Due' and 'Co-pay Date Due' in the contractual notes tab so that they are ar least as current as the revised 'Order Date'
• In the ticket fee setup window, the 'Events' tab has been changed to 'Performances'. You can now indicate which performances a ticket fee will be applied to. If there are no entries in this list, the fee will be applied to all performances. If there are some performances in this list, the fee will be applied to only those performances. Only enter something in this tab if there is a difference in the order fees attached to specific renters or specific venues.
• Fixed where tickets exchanging 'from' were not being released from the order, when the order was flagged as reservation only
• Fixed where database was set in 'transaction in progress mode' when attempting to exchange tickets that were in a reservation only order
• Fixed an issue where the credit card cost was not being calculated into the payment records. Upgrading will fix all prior payments where this fee was missing

Donations

• Enhanced to allow changing a donation record from a Corporate donation to an Individual donation, if the donation is flagged as a Corporate donation but there is no company name in the patron record. Once the donation is changed to Individual, you are required to have a company name in the patron record to change it back to Corporate. Previously the button would only be active if the donation could be either a Corporate OR Individual. This allows fixing of donations that were flagged as Corporate but the patron has since had their company name removed from the patron record.

Miscellaneous

• Changing only an employee data or function preference and closing the employee record will now save the change.
• Some fixes in the report engine.
• The ticket scanning process now defaults to place the user on the ticket number field when the window is opened (for convenience).
• Notifications now get sent on the close of a window. It was possible that notifications may be ignored under some circumstances.
• Employee record now updates properly if the only thing changed is to click on a checkbox for a permission.
• Changed the capitalization routines to remove multiple spaces out of a record regardless.
• Improved PABP clompliance in tracking access to credit cards displaying the full number - these are now tracked in the audit log for Theatre Manager in an 'AC' transaction.

Web

• Tuned the abandoned shopping cart timer process to check a little less often and provide more time to the server.
• The maximum number of tickets in any shopping cart has been limited to 100 tickets. This is a physical restriction based on the number of parameters in a web form.
• Pause sending mail button on the toolbar now works.
• The credit card popup on the web is now sorted alphabetically.
• Corrected the calculation of the savings obtained from using a plug in and place it in the cart.
• Fee descriptions are now properly displayed in the shopping cart
• There is a new apache module that addresses a memory issue under cases of high load. If the listeners reached the point where a timeout would occur for the client, there was a small memory issue in the apache module that would cause it to restart and keep on running. The net effect is that end users would see a blip in the browsing experience if they'd submitted a requests and they may have to submit it again. Other changes to the apache module:
  • log people who were forced to wait longer than the TM_WAIT_TIME out before getting any service. This can be used to track if you are experiencing a lot of load and need an extra listener. The odd one of these means that there may be odd spikes (and I'd do nothing) ... a lot of these in the logs in a short time means you are busy and need another listener
  • There is a new timeout TM_PROCESS_TIME for processing requests. This is the time allowed to the listener by apache to process any request - before giving up on the listener and thinking that it died. Defaults to TM_WAIT_TIME for backward compatibility.
  • The single error page have been split into 3. There is now:
    • TM_CLOSED_PAGE - which is where the user is sent if no listeners are running and so there is no service.
    • TM_WAIT_PAGE - which is where a user is sent if the apache module finds it can't find a listener to allocate the request to within the TM_WAIT_TIME. This implements what a couple of sites have asked for - something called a 'waiting room' (they saw it on ticket master). Essentially a page to hold the user and ask them to try again in a nice way ... after saying .. the shows are going like hotcakes. So we did that we did that as well. Defaults to be the same as TM_CLOSED_PAGE for backward compatibility.
    • TM_ERROR_PAGE - which is a page to go to if we encounter an unexpected error. Currently the only way that we've been able to hit the page is if we can force the listener to take to long to process a request (as in short timeout and try book 100 tickets so the listener gets over busy and can't tell apache its busy). Defaults to be the same as TM_CLOSED_PAGE for backward compatibility.
  • and we've improved the queue process if there are many request and not enough listeners to hold open the connection to the end user longer. This should lead to less timeouts at the end user.

Implementing the changes to the apache module and web listeners: