AudienceView Connect
AudienceView Documentation

AudienceView 6.3.0 HotFix 2 Release Notes

Release Date: August 22, 2012

Online 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.0 HotFix 2.
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

Business Intelligence and Reporting Fixes

Issue Solution ID
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.0 HotFix 2.
Scheduled reports are being sent at the designated times only.
AVT-3621
AVT-7121
You cannot generate a list of customers with invalid 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.0 HotFix 2.
Email Response String and Email Response 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.0 HotFix 2.
All of the address-related fields have been exposed in the Registry application Registry::EN::Collection Object::TSvenueCO::Field node.
AVT-7317

Payment Processing Fixes

Issue Solution ID
Two-stage RedCard transactions require a unique POSID. This has been corrected in AudienceView 6.3.0 HotFix 2.
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

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.0 HotFix 2.
Failed record responses are being truncated to 255 character.
AVT-7266

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.0 HotFix 2.
The tampering error does not display when accepting an AVTiki reservation through Facebook's mobile application.
AVT-7298