| Issue |
Solution |
ID |
When selling tickets using Cash via Quick Sales a validation error occurs.
After selecting seats via the Customer Services application Seats|Quick Sales page, adding them to the order and changing the 'Payment Method' to Cash, some of the credit card specific fields remain visible. When the order is created, a validation error displays indicating that some of the required fields have not been completed althought the field are not applicable to the sale. |
This has been corrected in AudienceView 6.3.2.
When Cash is selected as a 'Payment Method' only the appropriate fields remain displayed and the order can be created. |
AVT-7825 |
| 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.2.
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.2.
Promotional code limits are being enforced correctly for the applicable roles. |
AVT-7815 |
| Making selections from the Utilities application Customer Merge|Query page's 'Merge', 'Contact' and 'Address' columns does not affect the merging of customer accounts. Customers are only merged if 'Merge Account Default Selected?' is set to Yes (the dropdown in AudienceView 6.3.2 is called 'Automatically Select Merge Customers'). |
This has been corrected in AudienceView 6.3.2.
Making selections on the Utilities application Customer Merge|Query page produces the expected results. |
AVT-7996 |
| The Utilities application Customer|Merge UI is not very intuitive, and multiple 'Create User' and 'Update User' options should be selectable. |
This has been corrected in AudienceView 6.3.2.
The Utilities application Customer|Merge UI has been improved so that the field names are more descriptive and the workflow is more direct. Queries can also be created using multiple 'Create User' and 'Update User' options. |
AVT-8004
AVT-8012 |
| 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.2.
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.2.
'Allowed Delivery Methods' can be removed the Legends application Price Types|Details page without any issues. |
AVT-8046 |
| The Utilities application Customer Merge tool causes a significant memory spike. Memory usage is normal for a couple of minutes followed by a rapid consumption of all of the available memory after which the server becomes unresponsive. |
This has been corrected in AudienceView 6.3.2.
The memory spike no longer occurs when the Utilities application Customer Merge tool is run. |
AVT-8063 |
| Several of the reports are consuming the servers CPU, causing performance issues. |
This has been corrected in AudienceView 6.3.2.
The performance of the reports has been optimized, and the server CPUs are no longer being consumed. |
AVT-8073 |
| Events with $0.00 pricing models can not be updated. |
This has been corrected in AudienceView 6.3.2.
Pricing models can now contain $0.00 pricing models. The default pricing amount has been changed from 0.01 to 0.00 in the Registry::EN::Business Objects::TSperformanceBO::Model Pricing node 'Amount' field and the Registry::EN::Business
Objects::TSmapBO::Model Pricing node 'Amount' field. |
AVT-8158 |
| Benefits.xml and Points.xml dataloader files are not displaying in the Utilities application Dataloader|Search page's 'Control File' field. The two files are used in conjuction with the CustomerBenefits and CustomerPoints BI queries as examples of how to populate the Customer Services application Customer|Basic page's customer value and customer statistics sections. |
This has been corrected in AudienceView 6.3.2.
The Benefits.xml and Points.xml dataloader files are not displaying in the Utilities application Dataloader|Search page's 'Control File' field. |
AVT-8168 |
| AudienceView incorrectly identifies itself in the HELO/EHLO command using the local machine name when communicating with the remote SMTP server. |
This has been corrected in AudienceView 6.3.2.
The Registry application System::Configuration node 'FQDN' (fully qualified domain name) field has been added. This field must contain a value if you are using the Remote SMTP server option. This value will appear in the email header. |
AVT-8320 |
| The file size of print-at-home tickets is too large, and large orders (e.g containing 20 tickets) are not being received because the attachment exceeds the email file size limit. |
This has been corrected in AudienceView 6.3.2.
The majority of the file size was related to the drawings coordinates of the barcode. The scale and size of barcodes have been changed. Orders with 110 tickets are being sent/received as expected. |
AVT-8322 |
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.2.
All of the passes are printing with the apporpriate custoemr information. |
AVT-8595 |
| The Customer Services application Bundle|Search page is displaying the availablity based on the performance price chart and not the bundle price chart. |
This has been corrected in AudienceView 6.3.2.
The bundle price chart is loading instead of performance price chart, and the availability Customer Services application Bundle|Search page is displaying properly. |
AVT-8657 |