AudienceView Connect
AudienceView Documentation

AudienceView 6.3.5 Fixes

Desktop Fixes

Issue Solution ID
Pass Ticket Templates do not print the 'Bundle Name' nor the 'Bundle Description'. This has been corrected in AudienceView 6.3.5.
'Bundle Name' and the 'Bundle Description' are now printing on pass ticket templates.
MAINT-346
The ticket numbers and statuses of miscellaneous items included within bundles are rolling back when orders are reloaded. This has been corrected in AudienceView 6.3.5.
The ticket numbers and statuses of miscellaneous items included within bundles remain when orders are reloaded.
MAINT-355
When the Delivery Method strategy is set to Intersection, a performance with delivery methods A, B, C and D is added to the shopping cart, delivery methods A, B, C and D are available on loginDelivery.asp page. If a stored value item with delivery methods A and B is then added to the shopping cart, delivery methods A and B are available on loginDelivery.asp page (an intersection of both items, as expected). When the stored value item is removed from the order, only delivery methods A and B are available on loginDelivery.asp page instead of all four options. This has been corrected in AudienceView 6.3.5.
The Delivery Method strategy re-evaluates the available delivery methods once items are removed from the shopping cart.
MAINT-372
The ticket numbers and statuses of miscellaneous items included within bundles are rolling back when orders are reloaded. This has been corrected in AudienceView 6.3.5.
The ticket numbers and statuses of miscellaneous items included within bundles remain when orders are reloaded.
MAINT-378
When a role is not Allowed to Leave Single Seats, and a single seat is left on the Customer Services application Seats|Map page, the expected pop-up message appears indicating that a single seat would remain; however, when the pop-up is closed and an attempt is made to select alternate seats error message 1242: This business object is in an invalid state and cannot be used. TSmapBO appears. This has been corrected in AudienceView 6.3.5.
The error message no longer appears, and alternate seats can be selected.
MAINT-550

Online Fixes

Issue Solution ID
If customers access an on-calendar/soon-to-be on-sale performance via an article's deep-link, they are directed to the seatSelect.asp page where the This event is not on sale yet message displays (as expected). When customers click the browser's 'Back' button and then attempt to access the performance again once it has gone on-sale, they receive the same message. It is not until that customers close their browser and begin a new session that they can purchase tickets to the performance via the deep-link. This has been corrected in AudienceView 6.3.5.
If customers have accessed an on-calendar/soon-to-be on-sale performance via an article's deep-link, they do not need to restart their browser sessions to purchase tickets once the performance goes on sale.
MAINT-163
The 'Display Month' field of the calendar widget is case senstive. If a month is not capitalized when it is entered, no results will appear on the calendar. This has been corrected in AudienceView 6.3.5.
The 'Display Month' field of the calendar widget is no longer case senstive. If a month is not capitalized when it is entered, results will still appear on the calendar.
MAINT-348
When reprint/forwarding bundle admission on a pass, the CancelEventOnCard request is no being sent to Fortress, and the original ticket number on the pass remains active. This has been corrected in AudienceView 6.3.5.
The CancelEventOnCard request is sent to Fortress when a ticket on a pass is forwarded or removed.
The CancelBarcode request is sent to Fortress when an admission on pass is cancelled.
MAINT-375
When sending a batch of emails, the record being inserted or updated in the AVScheduler is causing a not valid error. The error prevents the rest from being transmitted, and only one of the emails being is sent. This has been corrected in AudienceView 6.3.5.
The Registry application Registry::EN:: TScorrespondenceBO::Correspondence Details::Country and Registry::EN:: TScorrespondenceBO::Correspondence Details::State nodes' 'Unbound' attribute dropdown has been set to Yes, by default, so the validation error does not occur when the AVScheduler is trying to insert a 'Country' or 'State' value that is not on the list.
MAINT-408
The Comp Admission Details report is displaying an incorrect count (one additional comp ticket) in the price zone section. This has been corrected in AudienceView 6.3.5.
The Comp Admission Details report produces the correct admission count in all sections.
MAINT-510
The try again link on performances/items in the shopping cart is causing confusion during the purchase flow.
When seats are added to the shopping cart via the mapSelect.asp page, the try again link appears in the shopping cart. If users click the link, they are returned to the seatSelect.asp page for the performance in the cart. If users navigate to the mapSelect.asp page, the seat map does not render.
If a second performance is then added to the cart, the try again link appears for both performances; however, both links direct users to seatSelect.asp page for the performance most recently added to the shopping cart.
This has been corrected in AudienceView 6.3.5.
  • If seats are added via the mapSelect.asp page, the try again link does not appear in the shoppingCart.asp page.
  • If seats are added for a single performance via the seatSelect.asp page, the link appears with the performance.
  • If a second performance is added to the shopping cart, the link does not appear anymore.
MAINT-532
Customers cannot complete orders using partial payments when a percentagae of the total is paid using a 3D Secure payment method and the other portion is not (e.g. accounts and gift cards). This has been corrected in AudienceView 6.3.5.
Customer can now complete orders using partial payments when one of the payments is 3D Secure and the other is not.
MAINT-583

Mobile Fixes

Issue Solution ID
Articles with deep-linked promtional codes are not loading in AudienceView Mobile, although the deep-link is working in AudienceView Online. This has been corrected in AudienceView 6.3.5.
Articles with deep-linked promotional codes are now loading in AudienceView Mobile.
MAINT-310

Business Intelligence and Reports

Issue Solution ID
When running the Performance Pricing by Price Type report for a large number of performances with an even greater number of price charts attached to each performance the report is taking too long to generate on screen. When the report is scheduled to be sent via email, the Registry locks preventing all other scheduled reports from running. This has been corrected in AudienceView 6.3.5.
The Registry is no longer locking when the Performance Pricing by Price Type report is sent via email.
MAINT-236
You are unable to report on customers who have used a promotional code via BI. This has been corrected in AudienceView 6.3.5.
The Promotion Code ID criteria has been added to the Customer BI.
MAINT-352
'Series Data 7' and 'Series Data 8' fields do not appear in Business Intelligence. This has been corrected in AudienceView 6.3.5.
The 'Series Data 7' and 'Series Data 8' fields are now available in the Admissions, Customers, Orders and Payments BIs.
MAINT-366
The Wrap report is incorrectly including all chrage type instead of just the Tax charge types. This has been corrected in AudienceView 6.3.5.
The 'Display Charge Type' field has been added to the advanced section of the Wrap report, enabling you to select the types of charges that you want to include in the report.
MAINT-480
The current CustomerPoints BI should be updated.. This has been corrected in AudienceView 6.3.5.
The default version of the CustomerPoints BI query has been updated and will now generate a list of customers containing the sum value of the formula that your organization is using to determine the customer points/rank, the Customer ID, the exisiting 'Customer Rank', 'Customer Points' and 'Customer Total Members' field values, the sort order of the customer and the total number of customers pulled via the BI. The CustomerPoints BI query should be customized via the Business Intelligence and Reports application Business Intelliegence|Formulas page to suit your organization.
MAINT-541

Performance Fixes

Issue Solution ID
Memory leak in the delivery manager handle. This has been corrected in AudienceView 6.3.5.
The memory leak has been resolved.
MAINT-581

WebAPI Fixes

Issue Solution ID
The WebAPI is consuming large amounts of memory. This has been corrected in AudienceView 6.3.5.
A memory leak in the TSorderBO doWork addPayment action has been fixed and the WebAPI is no longer consuming large amounts of memory.
AVT-9263
AVT-9371
The WebAPI calls the WebSales user. To get the WebAPI to work the WebSales user and site need to be configured and working.
The WebAPI should be completely seperated from the AudienceView Online.
This has been corrected in AudienceView 6.3.5.
The WebAPI does not attempt to initialize a site for an already authenticated session; however, it does allow for site initialization if the session is not authenticated.
MAINT-514
MAINT-534

AVTiki Fixes

Issue Solution ID
The incorrect admission count is displayed during the redemption process. If a customer has saved five seats for friends, and a friend redeems three of the seats, 'Seats for you - 5' (on the orderContact.asp page) and '5 Admissions' (on the shoppingCart.asp page) will still be displayed. This has been corrected in AudienceView 6.3.5.
The correct admission counts are being displayed. If a customer has saved five seats for friends, and a friend redeems three of the seats, 'Seats for you - 3' (on the orderContact.asp page) and '3 Admissions' (on the shoppingCart.asp page) will be displayed.
MAINT-205
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.5.
AVTiki's reservation codes now include less than 60 characters.
MAINT-470