Release Date: October 29, 2012
Desktop Fixes
|
Issue |
Solution |
ID |
|
When you change the 'Default Value' for the Registry application Registry::EN::Collection Objects::TSCorrespondenceCO::Fields::Status node error Message # 4004: %n validation error(s) occurred. appears. |
This has been corrected in AudienceView 6.3.0 HotFix 7.
The error message no longer appears, and the 'Default Value' of the Registry application Registry::EN::Collection Objects::TSCorrespondenceCO::Fields::Status node can be altered. |
AVT-7650 |
Promotional code limits are not being enforced when the promotional code is applied to a performance for one role, and a price chart for another.
When a promotional code with a limit of two is assigned to:
-
a customer via a benefit;
-
a performance via the Venue Configuration application Performance|Calendar page for one role (e.g. Box Office); and
-
a price chart via the Venue Configuration application Price Chart|Pricing page for another role (e.g. Internet); the promotional code limits are not being enforced and the customer with the benefit can purchase more than two tickets to the performance.
|
This has been corrected in AudienceView 6.3.0 HotFix 7.
Promotional code limits are being enforced correctly for the applicable roles. |
AVT-7815 |
|
When seats are removed from an order that contains both 'Ship to' and 'Billing' customers (with or without refunding the purchase price) a database error occurs. |
This has been corrected in AudienceView 6.3.0 HotFix 7.
The database error no longer occurs and seats can be removed/refunded as expected. |
AVT-8006 |
Removing delivery methods from price types causes database blocking.
When 'Allowed Delivery Methods' are removed from the Legends application Price Types|Details page, a database error occurs. |
This has been corrected in AudienceView 6.3.0 HotFix 7.
'Allowed Delivery Methods' can be removed the Legends application Price Types|Details page without any issues. |
AVT-8046 |
Business Intelligence and Reporting Fixes
|
Issue |
Solution |
ID |
|
If an associated charge uses a percentage calculation, the 'Taxes' and 'Totals' columns of the Ticket Sales by Price Type and Price Zone report displays NaN when the report is generated using 'Display Values' of Sold. |
This has been corrected in AudienceView 6.3.0 HotFix 7.
The Ticket Sales by Price Type and Price Zone report displays the correct values within the 'Taxes' and 'Totals' columns regardless of the charges' calculation. |
AVT-5122 |
The Payment Allocation report is not balancing with the Ticket Sales report or the End of Day Summary report.
When a scheduled payment has been cancelled/voided, the Payment Allocation report is not recognizing it as such. |
This has been corrected in AudienceView 6.3.0 HotFix 7.
The Payment Allocation report now balances. |
AVT-7966 |
|
The Ticket Sales report is producing different results in AudienceView 6.3 compared with AudienceView 5.1. |
This has been corrected in AudienceView 6.3.0 HotFix 7.
The AudienceView 6.3 version of the Ticket Sales report template has been updated. The results of both versions of the report are now identical (when using the same data). |
AVT-8038 |
Printing Fixes
|
Issue |
Solution |
ID |
An error occurs when attempting to batch print on a designated reporting server.
When a reporting server (set up to reduce the impact of running reports on the performance of the application) is used to run a batch print job, an error occurs. |
This has been corrected in AudienceView 6.3.0 HotFix 7.
The error no longer occurs when the batch print job is run. |
AVT-8042 |
Payment Processing Fixes
|
Issue |
Solution |
ID |
|
Improve application logging around payment processing calls. |
This has been improved in AudienceView 6.3.0 HotFix 7.
The payment processing logging has been moved from the payment handle to the payment interface level. |
AVT-8090 |