AudienceView Connect
 Product Guides   Knowledge Base   Discussions   Support   Annual Conference   Developer Guide Login   Developer Guides  
 
AudienceView Documentation

AudienceView 6.3.1 Fixes

Table of Contents | Previous

Desktop Fixes

Issue Solution ID
When creating a ticket template, the does not contain 'Conditional Operator' does not work.
Does not contain 'Conditional Operator' elements that are added to ticket templates via the General Configuration application Tickets|Elements are not displaying on the printed tickets.		 This has been corrected in AudienceView 6.3.1.
Does not contain 'Conditional Operator' elements are displaying on printed tickets.		 AVT-5991
When a saved payment method is selected from the Payments dialog box on the Customer Sevices application Order|Summary page and the 'Card Number' is altered, a duplicate version of the payment method is saved to the payment information section of the Customer|Basic page. The duplicate payment method also appears in the 'Payment Method' dropdown of the Payment dialog box. This has been corrected in AudienceView 6.3.1.
The duplicate payment information is not being saved against the customer accounts.		 AVT-6154
Payments are being rejected when an address' apartment and building numbers are both included on address line 1. This has been corrected in AudienceView 6.3.1.
Addresses are being verified when apartment and building numbers are both included on address line 1, and payments are being processed.		 AVT-6476
When an order containing a gift certificate that used the Email delivery method is updated, the gift certificate's 'Redemption Number' changes. This has been corrected in AudienceView 6.3.1.
The 'Redemption Number' of a gift certificate on an order that used the Email delivery method will not alter when the order is updated (unless the order is reprint).		 AVT-6664
The AudienceView Calendar dialog box on the Venue Configuration application Performance Management|Seats page (after has been clicked) does not fully display nor can the calendar widget be moved. This has been corrected in AudienceView 6.3.1.
The AudienceView Calendar dialog box displays fully, and can be moved within the right-hand panel of the Venue Configuration application Performance Management|Seats page.		 AVT-6726
The 'Available Seats' column on the Customer Services application Seats|Search page is not intuitive.
When a performance is unavailable, a -1 is displayed in the 'Available Seats' column.		 This has been corrected in AudienceView 6.3.1.
The 'Available Seats' column on the Customer Services application Seats|Search page now displays the following:
  • On-Sale (with or without promotional codes) with active price charts: The cell is shaded green and indicates the number of available seats.
  • On-Sale (with or without promotional codes) without active price charts: The cell is shaded red and indicates Sold out or Unavailable as appropriate.
  • On-Calendar only (with or without promotional codes): The cell is shaded red and indicates Off-Sale.
 AVT-7125
An incorrect path causes a 404 error on the Customer Services application Order|Bundles|Request page. This has been corrected in AudienceView 6.3.1.
The path has been corrected and the 404 error on the Customer Services application Order|Bundles|Request page no longer occurs.		 AVT-7178
Updated renewal price types (for bundles) on the Customer Services application Order|Summary page are not reflected on the Order|Bundles|Seats page. This has been corrected in AudienceView 6.3.1.
Updated renewal price types (for bundles) on the Customer Services application Order|Summary page are reflected on the Order|Bundles|Seats page.		 AVT-7250
Performances must be on-sale on the Venue Configuration application Performance|Calendar page before they appear for sale within a bundle. This has been corrected in AudienceView 6.3.1.
As long as the performance is not explicitly off-sale, the Product Configuration application Bundles|Calendar page will override the Venue Configuration application Performance|Calendar page.		 AVT-7339
Bundle price type names concatenate on the Customer Services application Order|Summary and Order|Bundles|Bundles pages. This has been corrected in AudienceView 6.3.1.
The bundle price type names display properly on the Customer Services application Order|Summary and Order|Bundles|Bundles pages.		 AVT-7412
Seats are being displayed as Unavailable in the Customer Services application Seat|Map page when they have actually been sold because the price/price zone is not available to the currently used role. This has been corrected in AudienceView 6.3.1.
Sold seats are now being shown in Customer Services application Seat|Map page even if the price/price zone is not configured for the currently used role.		 AVT-7445
Deadlocks occur when adding/removing admissions to a performance via the Venue Configuration application. This has been corrected in AudienceView 6.3.1.
The deadlocks no longer occur when adding/removing admissions to a performance.		 AVT-7455
AVT-7457

Onlines Fixes

Issue Solution ID
If a default landing page is not defined on a site, AudienceView Online will not load and a JScript error will be displayed. This has been corrected in AudienceView 6.3.1.
If a site is created without a 'Default Article' set on the Content Management application Sites|Basic page (prior to AudienceView 6.2) or the Sites|Branding page (after AudienceView 6.2), the site will still load with the configured menu items (Sites|Menu Items page), the 'Page Header' and the 'Page Footer' articles (Sites|Basic page).		 AVT-1455
All three of the Search Results widgets do not display any pagination; therefore, only one page of performance results can be viewed. This has been corrected in AudienceView 6.3.1.
When more than one page of search results is returned, customers can navigate between them using the pagination.		 AVT-4840
Payment methods are being displayed using the 'Labels' followed by the 'Name' in parentheseson on the AudienceView Online orderContact.asp page.
This is standard practice in the Desktop where disambiguation is required; however, this is not desirable in AudienceView Online and in instances when no disambiguation is required.		 This has been corrected in AudienceView 6.3.1.
The payment method 'Labels' are being displayed in AudienceView Online without the 'Names'.		 AVT-7201
When you attempt to check the balance of a gift card, a 500 error occurs in the pop-up. This has been corrected in AudienceView 6.3.1.
Gift card balances can be checked.		 AVT-7278
The payment installment option does not hold payment preference when data validation fails.
When a customer selects the payment installment option, and there is an error in the data entry (e.g. incorrect credit card data), the application displays an error message, and at the same time switches the payment option back to Pay in Full. This switch might go unnoticed, and once all information is corrected and submitted, the credit card is charged with the entire order balance amount, which is not expected by the customers.		 This has been corrected in AudienceView 6.3.1.
If an error occurs while completing a payment intstallment plan, the option remains selected.		 AVT-7282
Users cannot save 'Order Marketing Data' fields during the AudienceView Online sales process.
When customers enter information in a blank 'Order Marketing Data' field and then selects a payment method, the field refreshes; however, if users enter the information again after selecting a 'Payment Method' it is saved as expected.		 This has been corrected in AudienceView 6.3.1.
'Order Marketing Data' fields do not refresh when customers select a 'Payment Method'.		 AVT-7413
The Best Available flow gets stuck in a loop.
When the Add More Seats link on the shoppingCart.asp page is clicked, and then the 'Look for Other Events' button on the seatSelect.asp page is clicked, users are directed back to the shoppingCart.asp page instead of the default.asp page where they can search for more events.		 This has been corrected in AudienceView 6.3.1.
Users are directed to the default.asp page when they click 'Look for Other Events'.		 AVT-7606
When a large number of performances are on-sale, AudienceView Online hits an SQL limitation. This has been corrected in AudienceView 6.3.1. AVT-7388
The bundleSelect.asp page does not indicate when a performance is sold out. This has been corrected in AudienceView 6.3.1.
When the bundleSelect.asp page is loaded, the availability information is loaded. If there are no availabile seats for a performance, it Sold Out! is displayed.		 AVT-7479

Mobile Fixes

Issue Solution ID
When the AudienceView Mobile session times out and the user refreshes the UI to reload the site, the role is not maintained, giving the user access to events that should not be available to them. This has been corrected in AudienceView 6.3.1.
When a Mobile user refreshes the UI after a session time out, the Mobile role is maintained.		 AVT-7335
Mobile is not inheriting the branding.
When there are seperate Mobile and Online roles configured within the Content Management application, and users navigate from a mobile device to /online.default.asp the redirect does not pick up the branding from the Mobile role assigned, but instead used the original Online role. If the user navigates directly to the /online/mobiledefault.asp the role is assumed correctly.		 This has been corrected in AudienceView 6.3.1.
When customers access AudienceView Online via a mobile device, the application redirects them to the AudienceView Mobile site automatically, and only displays the performance applicable to the Mobile role. As the user goes through the order flow, only delivery methods and payments allowed for mobile user is seen.		 AVT-7352
When customers are redirected to a Mobile site a 500 error occurs. This has been corrected in AudienceView 6.3.1.
Mobile customers are redirected to the Mobile site and can make purchases.		 AVT-7390
Users cannot access the full AudienceView Online from a mobile device if the mobile redirect is configured. When users select a link that should redirect them to the AudienceView Online site, they are being redirected to the AudienceView Mobile optomized site. This has been corrected in AudienceView 6.3.1.
Users are being redirected to the AudienceView Online site when they select an appropriate redirect link.		 AVT-7459

Business Intelligence and Reports Fixes

Issue Solution ID
When here are gangways (entrances) in the middle of rows, and AudienceView has been configured so that the sections of seats on either side of the gangways are different (to prevent Best Available from assigning seats on both sides of the aisleway), the Hold Type Range report displays the rows with the incorrect number of seats on hold. This has been corrected in AudienceView 6.3.1.
The Hold Type Range report displays the correct number of seats on hold per row.		 AVT-3449
Scheduled reports are not adhering to allocated schedule.
The scheduler is sending saved reports on a Daily basis even though they are scheduled to be sent Weekly.		 This has been corrected in AudienceView 6.3.1.
Scheduled reports are being sent at the designated times only.		 AVT-3621
AVT-7121
Scanned third-party tickets do not appear in the Scanned Tickets by Hour report. This has been corrected in AudienceView 6.3.1.
The Scanned Tickets by Hour report now reports on scanned third-party tickets.		 AVT-5992
Parent ID is labelled as Source Table.
The Source Table criteria that is available for Notes BI queries via the Business Intelligence application Business Intelligence|Results, Business Intelligence|Criteria and Business Intelligence|Filters pages is incorrectly labelled.		 This has been corrected in AudienceView 6.3.1.
The Source Table criteria that is available for Notes BI queries via the Business Intelligence application Business Intelligence|Results, Business Intelligence|Criteria and Business Intelligence|Filters pages has been renamed Parent ID.		 AVT-6697
When the General Ledger report is run, it hangs and does not produce any data. This has been corrected in AudienceView 6.3.1.
The General Ledger report produces the expected results and does not hang.		 AVT-7096
Renewable Payment Method is not available as part of an Order BI. This has been corrected in AudienceView 6.3.1.
Renewable Payment Method is now available as part of Order BIs, can be selected on the Business Intelligence and Reports application Business Intelligence|Results, Business Intelligence|Criteria and Business Intelligence|Filters pages.		 AVT-7183
The seat information (section, row, seat) displayed in the 'Seatblock' column of the Donor Biography report is incorrect. This has been corrected in AudienceView 6.3.1.
The seat information (section, row, seat) displayed in the 'Seatblock' column of the Donor Biography report is correct.		 AVT-7208
The Donor Biography report is running for multiple customers.
When the Donor Biography report is run via the Customer Services application Customer|Basic page it returns results for all customers from the selected customer to the most recently created customer. It should only generate results for the one selected customer.		 This has been corrected in AudienceView 6.3.1.
When the Donor Biography report is run from the Customer Services application Customer|Basic page it is only returning results for the currently selected customer.		 AVT-7213
You cannot generate a list of customers with invaild email addresses so that you can remove them from the source BI query to ensure that they are not emailed again. The Email Response String and Email Response Code options are currently only available within the Correspondence object, preventing you from reporting on the required email delivery fields. This has been corrected in AudienceView 6.3.1.
Email Response String and Email Reponse Code have been added to the Customer object.		 AVT-7237
The 'Street' and 'City' fields are not available under the TSvenueCO. This has been corrected in AudienceView 6.3.1.
All of the address-related fields have been exposed in the Registry application Registry::EN::Collection Object::TSvenueCO::Field node.		 AVT-7317
Scheduled reports are not adhering to allocated schedule.
The scheduler is sending saved reports on a Daily basis even though they are scheduled to be sent Weekly.		 This has been corrected in AudienceView 6.3.1.
Scheduled reports are being sent at the designated times only.		 AVT-7332
When the Order Marking Data report is run, it hangs and does not produce any data. This has been corrected in AudienceView 6.3.1.
The Order Marking Data report produces the expected results and does not hang.		 AVT-7350
When running the Ticket Sales by Price Type and Price Zone report with 'Display Values' set to Paid, comp admissions are not returned. This has been corrected in AudienceView 6.3.1.
Comp admissions are being properly calculated and displayed the Ticket Sales by Price Type and Price Zone report is run with 'Display Values' set to Paid.		 AVT-7410
If you select more than two 'Campaigns' when running the Detail Donation Summary report, the selected Date Range is ignored. This has been corrected in AudienceView 6.3.1.
The Donation Detail Summary report generates the expected results when two or more 'Campaigns' are selected.		 AVT-7415
When the Venue Proof report is run for a venue with a large number of seats in a single section (e.g. 18,000), the report does not run and only displays a white screen. This has been corrected in AudienceView 6.3.1.
The Venue Proof report runs and displays the proper values.		 AVT-7498

Payment Processing Fixes

Issue Solution ID
3D Secure transaction do not trigger for Anonymous WebSales. (no-customer) orders. This has been corrected in AudienceView 6.3.1.
Two new fields ('Site Options' and '3D Secure Enabled') have been added to the Content Management application Sites|Basic page. These fields allow you to determine whether the site will use 3D Secure transactions. The system will first look at whether or not the selected payment method is configured for 3D Secure transactions (via the '3D Secure Enabled' field on the General Configuration application Payment Methods|Basic page), then it will look for the setting on the Site|Basic page.		 AVT-1825
When the 'Account Status' value is altered via the Payments dialog box on the Customer Services application Order|Summary page, the option selected from the 'Account Staus' dropdown in the customer payment information section of the Customer Services application Customer|Basic page is being overwritten. This has been corrected in AudienceView 6.3.1.
Changes made to the 'Account Status' dropdown available through the Payment dialog box.		 AVT-7181
The 'Renewal Payment Method' field value is being reapplied to orders.
When the 'Renewal Payment Method' is removed from an existing order, the original selection still appears once 'Apply' has been clicked.		 This has been corrected in AudienceView 6.3.1.
The 'Renewal Payment Method' field remains blank once the original selection has been removed and the order is saved.		 AVT-7182
Two-stage RedCard transactions require a unique POSID. This has been corrected in AudienceView 6.3.1.
A point of sale identifier, the 'PosID' field, has been added to the Registry application System::Configuration::Payment Gateway::RedCard node. The 'PosID' is the prefix that is used with the transaction reference.		 AVT-7257

Printing Fixes

Issue Solution ID
When a reporting server that has been set up to reduce the impact that running reports can have 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.1.
The error no longer occurs when the batch print job is run.		 AVT-7354

Performance Fixes

Issue Solution ID
A memory leak of correspondence print records occurs when an admission is released. This has been corrected in AudienceView 6.3.1.
The memory leak no longer occurs.		 AVT-7440

Database Fixes

Issue Solution ID
Bulk emails are failing when the 'remoteSMTP' option is used when mail server responses exceed the 256-character column width in the database. This has been corrected in AudienceView 6.3.1.
Failed record responses are being truncated to 255 character.		 AVT-7266
When you search for and select an updateTemplate action via the Application Security application Audit|Search page a database error (3024) occurs. This has been corrected in AudienceView 6.3.1.
The database no longer occurs and the results can be viewed on the Application Security application Audit|Details page.		 AVT-7442

WebAPI Fixes

Issue Solution ID
The generated JSON is invalid. This has been corrected in AudienceView 6.3.1.
The JSON generation methods have been modified to generate valid JSON.		 AVT-7757
The generated XML does not encode special characters, meaning that the generated XML which includes special characters is invalid. This has been corrected in AudienceView 6.3.1.
The generated XML encodes special characters.		 AVT-7784

AVTiki Fixes

Issue Solution ID
The performance listing shown in AVTiki gives no indication that a performance is sold out or has no availability. This has been corrected in AudienceView 6.3.1.
A performance availability indicator has added to AVTiki's performance listing.		 AVT-5268
AVTiki currently only adds a table column cell to each row of the performance listing if an image has been configured in the 'Logo 1' field of the Venue Configuration application Performances|Basic page. This causes a table rendering issue when some performances have logos and others do not. This has been corrected in AudienceView 6.3.1.
A table column cell is now rendered whether or not a an image has been configured in the Venue Configuration application Performances|Basic page's 'Logo 1' field. All table rows have a consistent number of columns.		 AVT-5337
When accessing AVTiki using Chrome, a JScript error occurs.
If third party cookies are not accepted (a common configuration for internet users) then a server error is being displayed instead of requesting that cookies be enabled.		 This has been corrected in AudienceView 6.3.1.
The server error no longer displays, and a proper no-cookie error message is being displayed.		 AVT-5372
Change AVTiki to render the reservation timeout value on a dynamic basis, and remove the hardcoded 1 from the seatSelect.asp and default.asp pages. This has been corrected in AudienceView 6.3.1.
The reservation timeout value is rendered dynamically. The hardcoded 1 has been removed from the default.asp and seatSelect.asp pages, and the default value of the Registry application Registry::Application::Tiki::Messages node 'reservation timeout interval' field is 1 hour(s).		 AVT-5373
Like gates can be bypassed.
When users arrive at a performance via a search, they can purchase tickets without having Liked the AVTiki page.		 This has been corrected in AudienceView 6.3.1.
Users cannot purchase tickets without Liking the page.
Hint
It is recommeneded that you do not put links to the default.asp page in the 'Default Header' of the primary article. It just links you to the page you are on anyway.
AVT-5777
Change AVTiki to display the venue 'Name' when the venue 'Description' is blank instead of the 'Performance Code'. This has been corrected in AudienceView 6.3.1.
AVTiki now displays the venue 'Name' when the venue 'Description' is blank instead of the 'Performance Code'.		 AVT-5885
When users first visit the AVTiki page, the Permission Authorization loads the same pop-up window twice. Users are then prompted to log in. Once the permissions have been authorized, the window does not close. This has been corrected in AudienceView 6.3.1.
The permission authorization is only being submitted once. The Permission Authorization pop-up only appears once.		 AVT-5974
Even when a user is logged into an existing account, the 'Cardholder Name' and 'Bank Account Name' on the orderContacts.asp page are not being auto filled. This has been corrected in AudienceView 6.3.1.
The cardholder name and bank account name on the orderContacts.asp page is being pulled from the customer account instead of the order.		 AVT-6273
The 'Price Zone' is not displaying on the AVTiki's seatselect.asp page.
When logging onto the AVTiki via Facebook, you can choose your seat quantity for 'Price Type'; however, the Price Zone section does not display correctly. You are unable to continue with purchase or reservation.		 This has been corrected in AudienceView 6.3.1.
You can select the 'Price Zone' and continue with the purchase/reservation.		 AVT-7118
Missing branding images.
A number of images referenced in the .CSS file for AVTiki are missing.		 This has been corrected in AudienceView 6.3.1.
The the header.jpg file in the UI/FB/branding folder has been updated, and the following images have been added in the new UI/FB/branding/images folder:
  • header_background.png
  • logo_avtiki.png
  • logo_audienceview.png
  • order_info_border.png
  • order_info_background.png
 AVT-7130
The AVTiki is referencing the default 'Page Header' article set on the Content Management application Sites|Basic page instead of the brand specific article set in the 'Header' field on the Site|Branding page. This has been corrected in AudienceView 6.3.1.
The article set in the 'Header' field on the Content Managment application Site|Branding page overrides the value set in the 'Page Header' field on the Sites|Basic page.		 AVT-7150
When a user tries to access a sent reservation, and there are zero tickets available on the reservation, a 500 error is displayed. This has been corrected in AudienceView 6.3.1.
The 500 error no longer displays.		 AVT-7165
All alert pop-ups cause the screen to grey out, preventing customers from completing order. This affects both AVTiki and AudienceView Mobile.
On the final step of the order creation, the entire page is greyed out and none of the buttons on the page can be clicked; therefore, the reservation codes cannot be sent to friends.		 This has been corrected in AudienceView 6.3.1.
closeButton text has been added to AVTiki and AudienceView Mobile, allowing customers to close the pop-ups and continue through the order/reservation process.		 AVT-7202
If Google Analytics is enabled on the Content Managment application Site|Applications page, a 500 error occurs when customers are completing an order. This has been corrected in AudienceView 6.3.1.
The 500 error no longer occurs on the viewOrders.asp page, and order can be completed successfully.		 AVT-7490
The delivery method gets reset when changes are made to the payment method.
If AVTiki customers select 'Payment Method' after they have selected a 'Delivery Method', the 'Delivery Method' is reset to the default value.		 This has been corrected in AudienceView 6.3.1.
Changing the 'Payment Method' does not reset the 'Delivery Method'.		 AVT-7515
The 'Delivery Method Charges' are not reflected in the 'Order Total'.When there are two delivery methods, one with a charge and the other without, and the user switches between the two available delivery methods, the grand total does not automatically update. The charge and fee display when a payment method is selected. This has been corrected in AudienceView 6.3.1.
The page now refreshes page when the user switches between delivery methods, and the applicable charges are calculated and displayed correctly.		 AVT-7605