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

AudienceView 6.3.9 Fixes

Table of Contents | Previous

Desktop Fixes

Issue Solution ID
When selecting ten or more admissions that have a message configured on the section via the Customer Services application Seats|Map page, the pop-up message that appears on the Order|Summary page displays a 404 server error. The order can still be completed, but users do not see the section message. This has been corrected in AudienceView 6.3.9.
You can now select multiple seats with section messages without seeing the 404 error.		 AVD-766
When you hover over a screen on the mapSelect.asp page while in the Full Map, the block of seats are 100% opaque. This has been corrected in AudienceView 6.3.9.
When you hover over a screen on the mapSelect.asp page while in the Full Map, the block of seats are now only 25% opaque, so that it is easy to tell which block you are hovering over.		 AVD-2599
When searching bundles via the Customer Services application Bundles|Search page, the 'Next On Sale' date value renders as an invalid date value when a bundle is both on-calendar and on-sale (i.e. the year is 1900). When a bundle is on-calendar now but on-sale later, the date value renders correctly. This has been corrected in AudienceView 6.3.9.
The column header has been renamed 'On Sale', and the date is displayed correctly for the role being used to view bundle search results.		 AVD-2538
AVD-3612
Applying a 'Default Value' to a field where the field is Unbound causes the UI to display the attached list's 'Key' instead of the label/'English' value. This has been corrected in AudienceView 6.3.9.
The label/'English' values are now being displayed when a 'Default Value' has been added to an Unbound field.		 AVD-3386
When a seat has message on it, the screen shakes when you attempt to select it on the Customer Services application Seat|Map page. This has been corrected in AudienceView 6.3.9.
The black bar that displays the message at the top of the Customer Services application Seat|Map page was attempting to accommodate the full text. The screen no longer shakes when, and seats can easily be selected.		 AVD-3732

Online Fixes

Issue Solution ID
The price type 'Name' is being displayed instead of the 'Label'. This has been corrected in AudienceView 6.3.9.
The price type 'Label' is now being displayed.		 AVD-1939
When re-visting an event that has previously been selected, you are returned to the previously selected section of the pick-a-seat map. This has been corrected in AudienceView 6.3.9.
When you reselect a previously selected performance, you are directed to the seat map overview screen where you can select a section.		 AVD-2188
It is unclear that the 'Update Changes' button on the orderContact.asp page allows users to change their selected payment method. This has been corrected in AudienceView 6.3.9.
The 'Update Changes' button on the orderContact.asp page has been renamed 'Change Payment Method'.		 AVD-2860
The 'Download' button on the viewOrder.asp page does not allow online customers to print unprinted items on a previously printed order. This has been corrected in AudienceView 6.3.9.
The 'Download' button on the viewOrder.asp page now allows customers to download any items on the order that are currently in an unprinted state. In earlier versions the button was disabled if any order items had previously been printed.
The following labels in the Registry have been added/modifed:
  • Registry::EN::Application::Online::Orders node's 'Download Tickets Label' field now states Only items that have not been downloaded previously will be downloaded. Ensure that you save or print the file immediately after downloading it.
  • Registry::EN::Application::Online::Orders node's 'Download Tickets Full Reprint' field has been added and states All of the tickets on this order have already been downloaded.
 AVD-2688
Upsell articles do not display when Enable Online Pick a Seat is not selected from the 'Option' field on the performance's Venue Configuration application Performance|Basic page.. This has been corrected in AudienceView 6.3.9.
Upsell articles are displaying regards of whether or not Enable Online Pick a Seat is selected on the performance.		 AVD-3275
Customers are unable to update their credit card information after entering an invalid card on the orderContact.asp page. This has been corrected in AudienceView 6.3.9.
Customers can update their credit card information on the orderContact.asp page.		 AVD-3908
When an online form is sent to customers using a permalink, the forms can be submitted without completing all of the required fields. This has been corrected in AudienceView 6.3.9.
All required fields must be completed before an online for is submitted regardless of how customers access it. An updated webConfig file has been created.		 AVD-4145

Business Intelligence and Reports Fixes

Issue Solution ID
The 'Projected Value' in the Wrap report does not equal the 'Projected Value' on Performance Availability report, and it does not update correctly when the admission Price Zone is changed. This has been corrected in AudienceView 6.3.9.
The 'Projected Values' for the Wrap report and Performance Availability report are the same across all performances.		 AVD-2309
When a saved BI uses the Does not equal condition in the criteria, the list of multiple criteria joined by a + become a range using only the first two values that are listed. This has been corrected in AudienceView 6.3.9.
Saved BIs that use Does not equal display the individual items instead of becoming a range.		 AVD-2691
The Performance Settlement report is not displaying the price types in the correct order. This has been corrected in AudienceView 6.3.9.
The Performance Settlement report is now displaying the price types in alphabetical order.		 AVD-3989

Payment Fixes

Issue Solution ID
Rolling back ServeBase Chip and Pin transactions fail because the capture method is not being sent. This has been corrected in AudienceView 6.3.9.
The capture method is now being sent when ServeBase Chip and Pin transactions are rolled back.		 AVD-422
The Redcard DLL does not send the correct POSid on void by reference for web transactions with 3-D Secure. This has been corrected in AudienceView 6.3.9.
The correct POSid is being sent and online voids are beign processed.		 AVD-159
AVD-4382
Cannot process Direct Debit payments because the bank address exceeded the 128 character limit. This has been corrected in AudienceView 6.3.9.
The character limit has been increased to 250 and extraneous character spaces have been removed. Direct Debit payments are being successfully processed.		 AVD-3693

Performance Fixes

Issue Solution ID
The BI query being used for the Customer Services application Customer|Notes page is causing performance issues. This has been corrected in AudienceView 6.3.9.
The BI behind the Customer Services application Customer|Notes page has been updated. The performance issue no longer exists.		 AVD-3075

WebAPI Fixes

Issue Solution ID
The WARNING parameter does not suppress messages in ASP. This has been corrected in AudienceView 6.3.9.
The WARNING parameter has been renamed ACCEPTWARNING, and messages are being surpressed as expected.		 AVD-3977
Backport all of the WebAPI fixes from AVD-1720. The following fixes have been applied to 6.3.9.
  • AVD-1104: Empty strings are returned as an empty array in JSON.
    An empty multi now return as an empty string. The following syntax should be used:
    • Non-multi, has a value: NAME:"VALUE"
    • Non-multi, null/empty: NAME:" "
    • Multi, null/empty: NAME:[ ]
    • Multi, single value: NAME:["VALUE"]
    • Multi, multiple values: NAME:["VALUE_1", "VALUE_2"]
  • AVD-1206: An invalid BO handle will fall through to the default/unknown exception response (WebAPI result code 6). This deserves a dedicated result code and message.
    Status code 33 has been added to identify a business object that does not have a handle in the cache.
  • AVD-1217: The error JSON response is inconsistent between the Java and ASP versions of the WebAPI. For example, the Java version outputs Error level whereas the ASP version outputs error.
    The error JSON response is now consistent between the Java and ASP versions of the WebAPI.
  • AVD-1218: In the ASP WebAPI, it is possible to GET the primitive value, but not its DETAILS.
    The node search method for DETAILS differed from that used for GET.
    DETAILS has been updated to utilize TSbusinessNode::findInTree(context) so that it is consistent with the other WebAPI GET and SET implementations.
  • AVD-1224/AVD-3977: The WARNING parameter does not suppress messages in ASP.
    The WARNING parameter has been renamed ACCEPTWARNING, and messages are being surpressed as expected.
  • AVD-1300: The COM implementation is corrupting the api.asp result because the BSTR constructed and passed to the ASP is relying on a temporary variable that is freed mid-stream.
    The BSTR construction and handover to ASP has been corrected.
  • AVD-1453: Site should be optional.
    Site is no longer required when initializing the site.
  • AVD-1460: When requesting WebAPI/session?DETAILS=Printers, an error occurs even though Printers is a valid node.
    The auditHistory parameter value has been added to toXML and toJSON node method invocations. It is now possible to request WebAPI/session?DETAILS=Printers.
    Caution
    The ticket stock values in the stock list cannot contain any spaces in either the 'Key' or 'Entries' fields. This will be corrected in a future release (AVD-1108).
  • AVD-1461: The work message is in an inconsistent location between the Java and ASP versions. In ASP, the work message is under the data object; however, in Java, the message is not under the data object.
    The JSON WebAPI response incorrectly assumed that a data element always followed the result. It is now conditional.
  • AVD-1462: Exception details are not being returned.
    The exception details are now being returned.
  • AVD-1718: The article 'Page Size' overrides the user entered 'Page Size', and the TScontentBO pagination overrides the user entered 'Page Size' by always resetting to the Registry default when a search is executed.
    If a 'Page Size' has been defined in a WebAPI call, it will override tghe 'Page Size' setting in the article/Registry.
 AVD-4253