Version 6.57

This is an enhancement release for Theatre Manager.

The primary new features are addition of reason to buy for web sales, addition of page selection for long lists of events on the internet and enhancement of controls around credit card security.

Version 6.56 • Updates

Released Feb. 4, 2005

Key changes:

Added reason to buy for web sales
Added pagination to the web list of events
enhanced the controls around credit card security
Fixed auto-renewal process for tickets
fixed entry of account number for events and dates window
enhanced reporting of credit card information on a number of reports.

Note: Upgrading from version 6.5x has seven (7) web page changes (two are mandatory and must be made otherwise web sales will not work).

Upgrading from earlier versions, please read version 6.56 notes - that was a major upgrade and those upgrade requirements are explained - be warned.

We suggest reading the prior release notes completely - especially if you are not at version 6.56.

Preparing for the Update

Theatre Manager will

Reorganize the database
fix all auto renewal subscriptions and associate the first credit card number belonging to the patron to that subscription for next years renewal processing

The user will need to

Before upgrade

if upgrading from a version before 6.48, read version 6.48 release notes

Complete your end of day. Deposit all funds, create all sales entries and post to the GL.

Verify the database using data utilities and ensure that everything is ok.

Make a backup copy of the database.

After upgrade

add two new web pages

upgrade PC charge payment server to version 5.7.1D if you have not already done so

Optional Steps

optionally, modify two checkout web pages

optionally, modify three pages to enable page scrolling on the event selection window

make some 'why did patron buy' selections for web sales. Go to setup->System Tables->Code tables and edit the 'reasons to buy' table for those to appear on the internet.

run the auto-renew credit card expiry date to find/fix those cards that have expiry and verify that the correct one has been associated to the patrons account

Time Required

It will take a long time from version 6.48 (see release notes)

From any version 6.5x or later, it will be relatively fast.

Before upgrade	if upgrading from a version before 6.48, read version 6.48 release notes Complete your end of day. Deposit all funds, create all sales entries and post to the GL. Verify the database using data utilities and ensure that everything is ok. Make a backup copy of the database.
After upgrade	add two new web pages upgrade PC charge payment server to version 5.7.1D if you have not already done so
Optional Steps	optionally, modify two checkout web pages optionally, modify three pages to enable page scrolling on the event selection window make some 'why did patron buy' selections for web sales. Go to setup->System Tables->Code tables and edit the 'reasons to buy' table for those to appear on the internet. run the auto-renew credit card expiry date to find/fix those cards that have expiry and verify that the correct one has been associated to the patrons account
Time Required	It will take a long time from version 6.48 (see release notes) From any version 6.5x or later, it will be relatively fast.

Web Sales

Enhanced the checkout page to allow the user to specify a reason for purchasing on the internet. This functionality is completely optional if you do not require (or want) it. However, you will need to copy one page from our sample site to get your web pages to work (even if you don't want the functionality). The steps are:

Download the sample web page folder for Mac or Windows
Install the sample web page folder into a directory of your choice (you will need to provide the password you were previously given)
copy the file 'setREASON_TO_BUY_LIST.html' from TMTemplates into your TMtemplates folder. This is a new file and must be copied, even if you do not want to enable reason to buy on your web site. If the file is missing, the web site will not work.
OPTIONAL, the other two web files that were changed were TMcheckout.html and TMchekcoutNoPayment.html. They have an extra row in them that asks the patron how they heard about your venue. You may wish to either:
- replace your files with the new templates if you have not modified these two files (generally, there was no need to, so its relatively safe)
- or, look for the table row tag <TR> that has the 'how did you hear about us' comment in it and copy that row to your pages of the same name. The key HTML code for including the popup is
  <select name="ORD_REASON_BUY_FC_SEQ"><field>F_HTML_REASON_TO_BUY_LIST</field></select>

Enhanced the event search page to show the events in pages so that the user can scroll back and forth in the event list using internet paging metaphor. This functionality, even if you don't use it, also requires one page to be installed. Assuming you have downloaded the latest sample pages

copy the file 'rowTicketPageList.html' from TMTemplates into your TMtemplates folder. This is a new file and must be copied, even if you do not want this feature on your web site. If the file is missing, the web site will not work.
copy the file 'tmError.txt' from Webpages into your Webpages folder. This has a new message # for scrolling pages. if you have changed your copy of this file, simply copy message number 10086 at the end of the file into yours using a text editor and save the file as text only, tab delimited.
copy the file 'rowTicketEvent.html' from TMTemplates into your TMtemplates folder. This file has one additional column added to it that shows the 'event' number in the list. Some people have customized this page. If so, you will need to compare the part we added <td width="15"><field>F_LINE_LAST_DISPLAYED</field>.</td> and decide if you want that in your page or not.
copy the file 'tmTickets.html' from Webpages into your Webpages folder or change your copy to get the additional functionality if you have already modified this page. The key changes added to to this page show the 'Select Page' at the bottom to let the user scroll through the web site. In the sample, look for the new code below and see how to adjust your web page. NOTE: I added an extra column to the event list. If you did not change this page, simply replace it (this applies to most sites I've seen). If you did modify this page, then you need to look at this code and incorporate it, if you wish the functionality. Otherwise, you do not have to add it to your web page.
- <tr class="tablerowheader">
  <td colspan=6 align="center">
  <field>D_EVENT</field> <field>F_LINE_FIRST_DISPLAYED</field>-<field>F_LINE_LAST_DISPLAYED</field> of <field>F_LINE_COUNT</field> displayed
  <field>pick(len(F_HTML_PAGE_LIST)=0,'          Select page: ')</field><field>F_HTML_PAGE_LIST</field>
  </td>
  </tr>

Reports

Changed all reports with credit cards displayed in them to respect the new security settings. If the user is unable to see the credit card, reports now will only display the last 4 digits.
The Media Report now has the media person's email address on it
The Patron List report now has the patron's email address on it
The Mail List Contact report now has the patron's email address on it.
The Mail List Telemarketing report now has the patron's email address on it.
Added a new report to the database utilities area. It is called the System Activity report and displays a past summary of key events that occur in Theatre Manager to help identify any systemic problems that arise from using Theatre Manager.
In prior versions of Theatre Manager, the donation campaign was added to tax receipts. This may have caused pagination issues which have been fixed in this version. The donation receipt report parameters were also changed to default to print the receipt number on the report, consistent with the desires of most sites.
Searching by expiry date has been made a lot smarter. On a report, if you now search by expiry dates <= xx/yyyy or between xx/yyyy and ss/tttt, Theatre Manager will be able to find them using the same conditions as if it were a date.
The report that lists the GL accounts associated with an event has been changed to display the new currency account numbers. The report has also been made smarter to only show the accounts valid for the accounting options on that report.

Fixed a condition where a venue is set up with X seats in it, but not used for any performances. Then, if the venue is reduced in size before associating it to the first event, Theatre Manager will now remove the excess seats that were named if the user goes into the 'name seat' function.

Fixed a condition where typing account numbers may cause an issue and be rejected if a '-' was put in the account number.

Payments

Changed the default for credit cards to being the one that is most used (of the type specified) from the first one entered. This means that if the user selects MasterCard as the payment method and the patron has a number of those (encrypted) on file, then TM defaults to the one that has been used the most often.
Found some issues with PC Charge payment server 5.7.1 and are recommending all users upgrade to 5.7.1D to deal with them. If you are not using PC Charge, this does not apply
Updated the internal credit card table to accept Diner's club cards that start with 3816 (which is apparently a new range for diners club)

Subscriptions

Fixed the auto renew capability in the Season Subscription window. When a subscription is set up as auto-renew, the credit card selected was not being properly connected in the database to the credit card record.
During prior upgrades, this was 'auto-renew' credit card information was lost from the season subscription record. During the upgrade, the credit card information that used to be on the patron record is now automatically connected to the subscription (for auto renewers only).
searching for expired credit cards on auto-renew subscribers has been made much easier using the 'expiry date' search that the reports now provide.
The creation of payments for the auto-renew process now functions properly with the outlet edition and sets up the correct currency for the payment, as well as connecting it to the proper encrypted credit card. Each time the credit card is used for auto-renewal, its use count is also incremented.

Miscellaneous Changes

The database rebuild and verification process has an additional option. Now, when rebuilding a database, you can specify the amount of additional free space, ranging from 5% to 30%. The default is to create 20% free space for data over and above the actual data space required for the new database.
Fixed a bug when entering volunteer time availability - the proper outlet value was not being set on the time availability record.