Release Date: October 21, 2014
AudienceView 6.3.9 HotFix 3 MD5 Hash
The MD5 hash value can be used to verify that the correct package has been downloaded/installed.
-
AudienceView 6.3.9 HotFix 3 MD5 Hash: 3926c5cf5cc3ac0a73e342fd322fb97b
Desktop Fixes
|
Issue |
Solution |
ID |
|
Rework the UI for extracting customers and assigning correspondence codes that was introduced in AudienceView 6.3.9 HotFix 1 (AVD-3847) |
This has been corrected in AudienceView 6.3.9 HotFix 3.
A change was made to revert a change in AudienceView 6.3.9 HotFix 1 in which users were required to perform a BI extract with correspondence codes via the Correspondence application.
Extracts with correspondence codes can now be performed via Business Intelligence. In addition, users are no longer required to select all of the results members to make a complete correspondence detail record on the customer. Instead, the system will warn users when result members are missing. Users can then choose to continue and create an incomplete correspondence record.
Changes to a BI query must be saved before an extract with correspondence codes is performed.
|
AVD-5158 |
|
When admissions on an order are exchanged, the admission-level charges are removed and not replaced. |
This has been corrected in AudienceView 6.3.9 HotFix 3.
Charges are being applied correctly when admissions are exchanged on an order.
|
AVD-5646 |
Business Intelligence and Reports Fixes
|
Issue |
Solution |
ID |
|
When running the Performance Settlement report, the 'Projected Value' extracts as $0 even though the pricing was been correctly configured on the performance. |
This has been corrected in AudienceView 6.3.9 HotFix 3.
The Performance Settlement report now correctly calculates the 'Projected Value' based on the 'Model' value on the performance. If a model is null or does not exist, the report will display a 0 value in the 'Projected Value' field. |
AVD-4946 |
|
Correspondence codes are only being set on the first 1000 customers extracted through Business Intelligence.
|
This has been corrected in AudienceView 6.3.9 HotFix 3.
The limit has now been removed so that the correspondence code is set on all of the customers returned through a Business Intelligence. |
AVD-5643 |
Payment Fixes
|
Issue |
Solution |
ID |
|
PayPal rollbacks are failing because Void is not supported.
|
This has been corrected in AudienceView 6.3.9 HotFix 3.
When a payment is made using PayPal, whether through Express Checkout or the order checkout, the payment is processed immediately. As a result, in a rollback situation, a Void cannot be used to reverse the payment.
AudienceView will instead use Refund as the method of reversal on PayPal Express Checkout and PayPal payments when a rollback occurs.
|
AVD-5898 |
Database Fixes
|
Issue |
Solution |
ID |
|
The encryptGUI.exe attempts to encrypt ts_payment_so table, but it no longer exists.
|
This has been corrected in AudienceView 6.3.9 HotFix 3.
Deprecated tables are no longer called by the encryptGUI.exe process.
|
AVD-5471 |
Dataloader Fixes
|
Issue |
Solution |
ID |
|
TSTBavailableTerminalRecord is hardcoded to be read-only in the TSpaymentGatewayBO, which prevents the setting of values from a Dataloader control file.
|
This has been corrected in AudienceView 6.3.9 HotFix 3.
Changes were made to support the use of the Dataloader to close terminal batches for gateways and acquirer combinations that do not support auto close.
This permits a scheduled task to run a script that closes the payment gateway batch at the end of the business day. |
AVD-5796 |