Release Date: December 3, 2012
Desktop Fixes
|
Issue |
Solution |
ID |
|
Several reports are consuming the servers CPU and causing performance issues. |
This has been corrected in AudienceView 6.3.1 HotFix 2.
The performance of the reports has been optimized, and the server CPUs are no longer being consumed. |
AVT-8584 |
Orders containing more than one pass are not pushing the admission details of the secondary customer to the second pass.
When orders are created that contain more than one pass, the second pass (with a customer assigned to it) is printing but without the customer details on it. The first pass prints via as expected. |
This has been corrected in AudienceView 6.3.1 HotFix 2.
All of the passes are printing with the apporpriate customer information. |
AVT-8595 |
Business Intelligence and Reports Fixes
|
Issue |
Solution |
ID |
|
When the GL report is executed, the following SQL error occurs: Incorrect syntax near the keyword with... |
This has been corrected in AudienceView 6.3.1 HotFix 2.
The SQL no longer occurs when the GL report is executed. |
AVT-8574 |
Payment Fixes
|
Issue |
Solution |
ID |
|
Transactions were going through the RedCard payment gateway without a valid PosID. |
This has been corrected in AudienceView 6.3.1 HotFix 2.
RedCard payments are being sent with valid PosIDs and are being processed correctly. |
AVT-7224 |
|
Declined 3DSecure transactions are causing a 500 error. |
This has been corrected in AudienceView 6.3.1 HotFix 2.
Declined 3D Secure transactions work. |
AVT-8635 |
Database Fixes
|
Issue |
Solution |
ID |
The TSmapBO does not clear updated data, generating unnecessary database traffic.
When changes are made to a number of admissions via the Venue Configuration application Performance Management pages, the previously updated admissions are being saved each time that 'Apply' is clicked. This generates unnecessary database traffic. |
This has been corrected in AudienceView 6.3.1 HotFix 2.
Only one record for each update is being adding to the database. |
AVT-8593 |
|
TSmapBO does not generate audit_ID and causes changes attributed to the previous audited event. |
This has been corrected in AudienceView 6.3.1 HotFix 2.
A unique audit_id is now being created for each record and each sequence number. |
AVT-8594 |