Version 6.67.00

This version of Theatre Manager contains one main change - an enhancement to the logon and password security options.

There are some additional reports and minor enhancements.

Version 6.65 • Updates

Released July 5, 2005

Key changes:

implementation of password use and retention policies to force passwords to expire and prevent reusing passwords. The default on the upgrade is to leave password settings consistent with prior versions of Theatre Manager.

Note: Read prior release notes for any mandatory web pages changes. There are no web page changes for this version.

Theatre Manager will

The user will need to

Before upgrade	Read the release notes for any version prior and follow the directions 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	None
Optional Steps	Go to the setup->System preferences window and click on the 'Password' tab. Make any changes to the password security that you wish.
Time Required	Updating the database from 6.65 will take less than a minute

Before upgrade

Read the release notes for any version prior and follow the directions
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

None

Optional Steps

Go to the setup->System preferences window and click on the 'Password' tab. Make any changes to the password security that you wish.

Time Required

Updating the database from 6.65 will take less than a minute

System Preferences

Added a new tab in the system preferences window (Setup->System Preferences) that can be used to set the password policies for your site. This is in response to some support calls about some recently released system guidelines from Visa/Mastercard merchant services. These guidelines are very useful in describing security polices for any system, whether or not they contain credit card information.

We have reviewed their policies and feel that Theatre Manager meets the system component if some additional password features are imposed. If you would like to place stricter policies in place, open this window and make any changes you wish. To meet the minimum we understand is suggested in the document, click the button on the screen 'set to PC Card Industry Data Security Recommendations'.

Minimum Length	Sets the minimum length of the password. Anything less than this will be rejected.
Unique Passwords	Tells Theatre Manager how many of the users prior passwords should be remembered. If the user tries to re-use a password that is in the list of prior passwords, they will not be allowed to used it.
Days before change allowed	this indicates the minimum number of days that a password must be in use after being changed by a user. This prevents the user changing the password a number of times to be able to use the original password. note: Master users may reset any password at any time.
Days until expiry	indicates the number of days since last password change whereupon another password change must occur. If set to zero, passwords may be used forever.
Attempts before lockout	Indicates how many invalid attempts will be allowed before a user account is locked out and must be reset by a master user. If you lock out a master user password, it can only be reset by another master user (or failing that, by sending the database to us to zap the password).
Prevent repeating characters	if checked, the user cannot have two letters in a row that are the same in any password.
Require mixed case	if checked, passwords must contain at least one upper case and one lower case letter.
Password is all upper case	if checked, passwords are all upper case. In the past, this was true. For enhanced security, uncheck this field
Require number and character	If checked, there must be at least one character and one number in the password.

Misc Changes

Fixed problem when swiping credit cards and sending the swiped information to PC charge. On some credit card swipes, if the swipe was programmed to read both track I and II data and the delimiter was not a New line, then Theatre Manager tried to send both tracks to PC charge, resulting in an inability to process the card. Theatre Manager now parses out Track I if it exists before sending it to the bank.

Fixed the display of two fields (age code and volunteer status) on the Patron Volunteer Report.

Fixed a problem adding volunteer time availability. If the user deselected some months (i.e. the volunteer was not available for all month), then Theatre Manager would hang. This is fixed.

Fixed an issue with year end rollover for databases where the fiscal year runs from January to December. It now consolidates everything within the fiscal year properly for years older than 4 years.

Fixed an issue when adding a gift certificate to an order. If the default data settings indicate that an order fee applies to gift certificates, Theatre Manager would add a transaction to the system without adding the actual order fee. The result was an end of day imbalance. TM no longer adds order fees on new gift certificates if added from the payment window.