| Issue |
Solution |
ID |
| When you change the 'Default Value' for the Registry application Registry::EN::Collection Objects::TSCorrespondenceCO::Fields::Status node error Message # 4004: %n validation error(s) occurred. appears. |
This has been corrected in AudienceView 6.3.1 HotFix 1.
The error message no longer appears, and the 'Default Value' of the Registry application Registry::EN::Collection Objects::TSCorrespondenceCO::Fields::Status node can be altered. |
AVT-7650 |
| The Utilities application Customer|Merge UI is not very intuitive, and multiple 'Create User' and 'Update User' options should be selectable. |
This has been corrected in AudienceView 6.3.1 HotFix 1.
The Utilities application Customer|Merge UI has been improved so that the field names are more descriptive and the workflow is more direct. Queries can also be created using multiple 'Create User' and 'Update User' options. |
AVT-8004
AVT-8012 |
| When seats are removed from an order that contains both 'Ship to' and 'Billing' customers (with or without refunding the purchase price) a database error occurs. |
This has been corrected in AudienceView 6.3.1 HotFix 1.
The database error no longer occurs and seats can be removed/refunded as expected. |
AVT-8006 |
Removing delivery methods from price types causes database blocking.
When 'Allowed Delivery Methods' are removed from the Legends application Price Types|Details page, a database error occurs. |
This has been corrected in AudienceView 6.3.1 HotFix 1.
'Allowed Delivery Methods' can be removed the Legends application Price Types|Details page without any issues. |
AVT-8046 |
| The Utilities application Customer Merge tool causes a significant memory spike. Memory usage is normal for a couple of minutes followed by a rapid consumption of all of the available memory after which the server becomes unresponsive. |
This has been corrected in AudienceView 6.3.1 HotFix 1.
The memory spike no longer occurs when the Utilities application Customer Merge tool is run. |
AVT-8063 |
| Several of the reports are consuming the servers CPU, causing performance issues. |
This has been corrected in AudienceView 6.3.1 HotFix 1.
The performance of the reports has been optimized, and the server CPUs are no longer being consumed. |
AVT-8073 |
| Add logging for BI execution, add session ID to report execution logging. |
This has been corrected in AudienceView 6.3.1 HotFix 1.
Visibility to which BIs have been executed via the Application Security application Audit pages has been removed. The auditing is now recorded in application log on the server and in greater detail. |
AVT-8139 |
| Events with $0.00 pricing models can not be updated. |
This has been corrected in AudienceView 6.3.1 HotFix 1.
Pricing models can now contain $0.00 pricing models. The default pricing amount has been changed from 0.01 to 0.00 in the Registry::EN::Business Objects::TSperformanceBO::Model Pricing node 'Amount' field and the Registry::EN::Business Objects::TSmapBO::Model Pricing node 'Amount' field. |
AVT-8158 |
| AudienceView incorrectly identifies itself in the HELO/EHLO command using the local machine name when communicating with the remote SMTP server. |
This has been corrected in AudienceView 6.3.1 HotFix 1.
The Registry application System::Configuration node 'FQDN' (fully qualified domain name) field has been added. This field must contain a value if you are using the Remote SMTP server option. This value will appear in the email header. |
AVT-8320 |