AudienceView Unlimited 7 Release Notes

Issue

Solution

ID

Loading a miscellaneous item with a 'Category' generates a not in list validation error on the 'Category', even though the value is in the list. This issue does not affect the use of the item except in the case of a Data Monkey script attempting to load the item.

This has been corrected in AudienceView 7.2.0.

The issue has been resolved and the validation error no longer appears. A Data Monkey script can now successfully load the item.

AVD-10582

When a compressed multi list's value is set as a default on a field, the 'Key' is being mismatched, and returns the incorrect value.

This has been corrected in AudienceView 7.2.0.

Compressed multi list values can now be default on fields.

AVD-10786

When a link to a performance is included in an email, the correspondence_detail_id looks like a variable.

This has been corrected in AudienceView 7.2.0.

Emails correctly include the correspondence_detail_id if it is specified (for example, as part of a URL).

AVD-10815

Issue

Solution

ID

When the venue 'Detailed Image' is larger than the 'Overview Image', section images on the mapSelect.asp page display over top of the 'Overview Image'.

This has been corrected in AudienceView 7.2.0.

The height of the 'Overview Image' (or 'Alternate Overview Image') now determines the size of the SVG map.

AVD-7584

Cancelling an order does not clear the promotion code from the session.

This has been corrected in AudienceView 7.2.0.

Promotion codes are cleared when promoted items are removed from the shopping cart.

AVD-10670

The 'Secondary Feature' and 'Tertiary Feature' articles configured on the Content Management application Site|Branding page are not being displayed in 'Rank' order.

This has been corrected in AudienceView 7.2.0.

The 'Secondary Feature' and 'Tertiary Feature' articles configured on the Content Management application Site|Branding page being displayed in the ascending 'Rank' order.

AVD-10823

Upcoming Events and My Events in My Account are displaying all of the future events.

This has been corrected in AudienceView 7.2.0.

The exisiting field 'Upcoming Events Limiter' field (Registry application Registry::EN::Online::Accounts node) determines how many days into the future upcoming events will be displayed on the maintainAccount.asp page. The default is 30 days, so it displays all upcoming events with a start date between now and 30 days in the future.

To display all of the upcoming events on the maintainAccount.asp page, the 'Upcoming Events Limiter' field can now be left empty so that it has no value. If you enter 0 in the field, no event will be displayed.

AVD-10824

Issue

Solution

ID

Editing the 'End Date/Time' for an existing event viathe Event Owner Portal causes the 'Start Date/Time', 'End Date/Time' and the 'Doors Open Date/Time' to default to the current date.

This has been corrected in AudienceView 7.2.0.

Editing the 'End Date/Time' no longer effects the other date settings.

AVD-10675

The venue's 'Marketing Multi-Data' fields do not display in the Event Owner Portal.

This has been corrected in AudienceView 7.2.0.

Venue 'Marketing Multi-Data' fields are now available in the Add Location pop-up in the Event Owner Portal. The fields are disabled by default for the WebSales group via the Application Security applicatin Groups|Attributes page.

Removing these attributes or changing the specific field values in the 'Readable' and 'Writeable' dropdowns to Yes will make the fields available the pop-up.

AVD-10816

The 'Ticket Name' and the 'Price' are not correctly matched when viewing an event with multiple prices.

The 'Ticket Name' and the 'Price' are stored and displayed correctly correctly in the Online and Desktop.

This has been corrected in AudienceView 7.2.0.

The 'Ticket Name' and the 'Price' are now correctly aligned.

AVD-10856

Issue

Solution

ID

Local payment failure causes an insertUnpaid error in Online.

This has been corrected in AudienceView 7.2.0.

Rolled back payments are now excluded in the online and auto-balance amount calculation. Previously, the amounts were not distinguished from payments, which led to an unpaid error when saving the order.

AVD-5913

The PayPal payment processor in combination with the PayFlow Pro gateway does not support voids, which could cause ghost payments in the payment gateway.

This has been corrected in AudienceView 7.2.0.

A new 'Payment Processor' dropdown has een added to the Registry application System::Configuration::Payment Gateways::PayPal node. It determines whether the PayFlow Pro gateway will trigger a refund where a void would normally take place:

•Other: Voided payments are voided.

•PayPal: Voided payments are refunded.

AVD-10537

Voiding a payment made with a PayPal gateway could cause allocation errors on the order because Void is not supported (PayPal gateways do an immediate settlement).

This has been corrected in AudienceView 7.2.0.

Clicking the 'Void' button on an order will no longer break the order.

AVD-11009

Issue

Solution

ID

Sounds and calendar are not working on supported scanners.

This has been corrected in AudienceView 7.2.0.

Audio files now play for success and failure indications on legacy (i.e. non-HTML5) devices.

AVD-8067

Issue

Solution

ID

When the NCOA Customer Update script is used to update customers with separate 'Street 1', 'Street 2' and 'Street 3' address lines, any subsequent BI extracts of the customers fails to separate the street lines into distinct results/columns.

This has been corrected in AudienceView 7.2.0.

Customers updated using the NCOA Customer Update script will now have the street lines separated in BI extracts.

AVD-10893