AudienceView Connect
AudienceView Documentation

AudienceView 6.3.4 Fixes

Desktop Fixes

Issue Solution ID
The Find Bundles dialog box is producing duplicate results when a link is being created within an article via the Content Management application Article|Text page. This has been corrected in AudienceView 6.3.4.
The Find Bundles dialog box is no longer producing duplicate results.
MAINT-74
When printing bundle admissions via the Utilities application, all of the tickets that have a pass assigned within the bundle are printing instead of the selected bundle and price type. This has been corrected in AudienceView 6.3.4.
Only the tickets for the selected bundle and price type are being printed via the Utilities application.
MAINT-82
The search results returned on the Customer Services application Order|Order History pages are not stretching to fit the window. This has been corrected in AudienceView 6.3.4.
The search results are now stretching to fit the size of the window. If the result columns are wider than the window, the scroll bar appears.
MAINT-84
An error occurs when searching for a performance via the Customer Services application Seats|Search page using the 'Available Section' field. This has been corrected in AudienceView 6.3.4.
The error no longer occurs, and any applicable search results are returned as expected.
MAINT-86
Admission hold statuses are not in sync across servers. This has been corrected in AudienceView 6.3.4.
Admission hold statuses are syncing across servers.
MAINT-156
Message 5585: There are price rows that are not zero that do not have charges. Continue? still appears even if the price chart contains only zero-value rows. This has been corrected in AudienceView 6.3.4.
The message no longer appears if the price chart only contains zero-value rows.
MAINT-162
The Same Seats bundle 'Option' is not working when customers purchase bundles via AudienceView Online. This has been corrected in AudienceView 6.3.4.
The same seats are being selected when customers purchase appropriately configured bundles via AudienceView Online.
MAINT-168
Partial payments applied to bundle admissions are erroneously being allocated to the last performance first. This has been corrected in AudienceView 6.3.4.
Partial payments are now being applied to the performance with the earliest start date first.
MAINT-178
After customers have exchanged their seats for every performance in a bundle (for single performances), but their bundle and renewal seats have remained the same, when the bundle with the same seats are sold to another customer both of the customers share the same renewal seat. This has been corrected in AudienceView 6.3.4.
Two customers can no longer share the same renewal bundle seat. Message 5333: No possible bundle seat(s) in your current admissions are available for use as a renewal seat for your bundle(s). Release and re-create the bundle(s) will appear if an order attempts to use a renewal seat that has already been assigned to a customer.
MAINT-189
An error occurs when a new brand is added to a site via the Content Management application Site|Branding page that utilizes the same 'Primary Linked Featured', 'Secondary Linked Featured' and/or 'Tertiary Linked Featured' This has been corrected in AudienceView 6.3.4.
The error no longer occurs, and multiple brands can share linked feature articles.
MAINT-219
An internal application database error occurs when attempting to access an audit entry via the Application Security application Audit|Search page. This has been corrected in AudienceView 6.3.4.
The error no longer occurs and audit entries can be accessed.
MAINT-238
An error occurs when seats are exchanged on a multi-venue/series Drawdown bundle. This has been corrected in AudienceView 6.3.4.
The error no longer occurs and the seats can be exchanged.
MAINT-246
Drawdown bundles are not being recalculated properly when items on the bundle are refunded. This has been corrected in AudienceView 6.3.4.
Drawdown bundles are being recalculated properly when items are refunded.
MAINT-319
When a performance has two calendar rows, one with a promotional code and one without, and the associated price chart contains price types without promotional codes and a price type with a promotional code, all of the price types (regardless if they are on promotion) are displayed when the promotional code is entered. This has been corrected in AudienceView 6.3.4.
The price types are displaying properly.
MAINT-331
The 'Site Option' field is missing from the Content Management application Sites|Basic page. This has been corrected in AudienceView 6.3.4.
The 'Site Option' field has been added to the Content Management application Sites|Basic page. Select eCommerce to identify the site as an online/ecommerce site so that transactions can be processed.
The Registry application System::Configuration::Payment Gateways::Servebase node's 'internet_transaction' dropdown has been removed and replaced with '3DSecure_enabled' dropdown. Selecting Yes from this dropdown will enable 3D Secure transactions.
MAINT-344

Online Fixes

Issue Solution ID
If a promotional code is entered before a performance's on-sale time then a No price for the admission (when using seat select) or a No seats were found that match your criteria. Modify your search or select a different performance. (when using best available) error is displayed. This has been corrected in AudienceView 6.3.4.
The error messages no longer display when a promotional code is entered before a performance's on-sale time.
MAINT-48
When the ship-to functionality has been disabled, the timeout clock in the shopping cart are (in the upper right-hand corner of the screen) does not appear on the loginDelivery.asp page, but reappears when custoemrs continue to the orderContact.asp page. The clock does appear on the loginDelivery.asp page when the ship-to functionaligy is enabled. This has been corrected in AudienceView 6.3.4.
The timeout clock appears on the loginDelivery.asp page regardless if the ship-to funtionality has been disabled or not.
MAINT-76
Recommended gift amounts do not appear on the donationDetails.asp page. This has been corrected in AudienceView 6.3.4.
Recommended gift amounts now appear on the donationDetails.asp page. The Recommended Amount label is configurable via the Registry application Registry::EN::Application::Online::Gifts node's 'Value Types' field.
MAINT-151
When customers log-in via a Login widget that has been inserted in an article, they are redirected to the maintainAccount.asp page instead of being returned to the article that was being viewed. This has been corrected in AudienceView 6.3.4.
When customers log-in via a Login widget, they are returned to the article that was previously being viewed.
MAINT-249
When customers create reservations for print-at-home tickets after their card was declined, they are receiving PDF tickets along with their reservation confirmations. This has been corrected in AudienceView 6.3.4.
Customers are no longer receiving PDF tickets with their reservation confirmations.
MAINT-190
Users are unable to add money to reloadable stored value items nor can they check the existing balance. An error occurs stating that the gift certificate/card does not exist. This has been corrected in AudienceView 6.3.4.
Stored value items can now be reloaded and existing balances can be checked.
MAINT-342

Mobile Fixes

Issue Solution ID
Suppress the 'Saved Payments' option on the Account Settings page, and convert the some fields to text entry in the Maintain Addresses section of the Create an Account page. This has been corrected in AudienceView 6.3.4.
The 'Saved Payments' option on the Account Settings page is now controlled by the Customer Saved Payments option in Application Security application User|Content and Group|Content* pages' Mobile property.
The following fields will become text fields when they are not bound to a list:
  • createAccount.asp: 'state/province' and 'Country' fields
  • maintainAddressDetails.asp: 'state/province' and 'Country' fields
MAINT-207

Business Intelligence and Reports Fixes

Issue Solution ID
The service charges list is erroneously bond to the Registry application Registry::EN::TSorderCO::Fields::Miscellaneous Items ID node, which is causing service charges to appear in the 'Values' field for Miscellaneous Items ID in Business Intelligence. This has been corrected in AudienceView 6.3.4.
The service charges list is no longer bound to the node. A picker has been added next to the 'Values' field that will open the Find Miscellaneous Items dialog box.
MAINT-38
The Miscellaneous Item Category options is missing from the Business Intelligence|Criteria and Business Intelligence|Results pages when creating an Order BI. This has been corrected in AudienceView 6.3.4.
The Miscellaneous Item Category options is available again.
MAINT-147
When applying a sub-total within the results of a BI query, the 'Performance Description' and the 'SUM Order Admission Net' are being duplicated when the BI is extracted as CSV. This has been corrected in AudienceView 6.3.4.
The 'Performance Description' and the 'SUM Order Admission Net' are not being duplicated.
MAINT-173

Payment Fixes

Issue Solution ID
Enabling credit card encryption in the database breaks the blacklist function. This has been corrected in AudienceView 6.3.4.
The encrypted account number is now compared with the blacklist entries so now both plain-text and encrypted values are checked.
MAINT-154
Declined 3D Secure transactions are causing a 500 error. This has been corrected in AudienceView 6.3.4.
Declined 3D Secure transactions work.
MAINT-177
When a 3D Secure card payment fails, the 3D Secure authentication returns a void, which is invalid. This has been corrected in AudienceView 6.3.4.
Failed 3D Secure payments return the correct authentication.
MAINT-216

Performance Fixes

Issue Solution ID
An unnecessary SQL is executed in Online to retrieve information about Box Office performances. This has been corrected in AudienceView 6.3.4.
A threading issue that occured when a performance was loaded has been corrected. A background thread that would clear the performance and cause another load the next time performance was accessed has also been corrected.
MAINT-291

Dataloader Fixes

Issue Solution ID
The command line dataloader.exe crashes when using a CSV input file. The job appears to complete succesfully, but the program crashes and causes in a Windows error. This has been corrected in AudienceView 6.3.4.
The batch log file was being closed before command line interface was written, cleaning up the logging. There are three interfaces using the dataloader (command line, UI and the AVscheduler). The command line no longer closes the batch log file handle after control file is processed, the UI and AVscheduler do.
MAINT-206

AVTiki Fixes

Issue Solution ID
You cannot accept reservations using Facebook's mobile application.
When Facebook's mobile applicating is used to accept an AVTiki reservation, a tampering error appears.
This has been corrected in AudienceView 6.3.4.
The tampering error does not display when accepting an AVTiki reservation through Facebook's mobile application.
AVT-7298
Users cannot send reservation codes to friends because the codes being sent were more than the 60 characters limit that Facebook allows. This has been corrected in AudienceView 6.3.4.
AVTiki's reservation codes now include less than 60 characters.
MAINT-159
When apostrophes are used in a 'Performance Description' a JScript errors on the seatSelect.asp and orderContact.asp pages. This also breaks the FacePile widget. This has been corrected in AudienceView 6.3.4.
Apostrophes can be used in a 'Performance Description' without causeing hte JScript error.
MAINT-160
The .CSS files uploaded via the Content Management application Sites|Branding page are not being rendered in the AVTiki UI. This has been corrected in AudienceView 6.3.4.
The .CSS files uploaded via the Content Management application Sites|Branding page are being applied to the AVTiki UI
MAINT-161
AVTiki does not properly set the 'Payment Return URL' for 3DSecure. The Return URL is referencing a missing Registry Node (AVTiki::TermURL), so the URL is always blank. Payments are sent for processing, but they are not return to the main site. This has been corrected in AudienceView 6.3.4.
AVTiki is now referencing the Content Managemtnt application Sites|Basic page's 'Payment Return URL' field, and processed payments are being returned to the main site.
MAINT-338