Release Date: October 23, 2013
AudienceView 6.3.0 HotFix 13 MD5 Hash
The MD5 hash value can be used to verify that the correct package has been downloaded/installed.
-
AudienceView 6.3.0 HotFix 13 MD5 Hash: c3b0a43fea029236c48a27d3d689cd28
Desktop Fixes
|
Issue |
Solution |
ID |
|
When series changes are pushed down to performances, unchanged data is updated. There needs to be a way to specify the information that is pushed down to avoid performances issues. |
This has been implemented in AudienceView 6.3.0 HotFix 13
Check boxes have been added to the Select Performances dialog box that appears when the 'Update Performances' button is clicked on the Venue Configuration application Series|Basic page.
The following categories can be selected and pushed down to the selected performance(s):
-
Associations: Information defined in the Series|Basic page's 'Association' dropdown.
-
Calendar: Information defined on the Series|Calendar page.
-
Delivery: Information defined in the Series|Basic page's 'Allowed Delivery Methods' field.
-
Limits: Information defined in the limits section of the Series|Limits page.
-
Passes: Information defined in the Series|Basic page's 'Passes' field.
-
Payment: Information defined in the Series|Basic page's 'Accepted Payment Methods' field.
-
Performance Details: Information defined following areas of the Series|Basic page's:
-
details section: 'Merchant Description' and 'Sales Type' fields and 'Producer' and 'Ticket Template' dropdowns.
-
performance data section: 'Options' field.
-
series URLs section: 'Additional Info', 'Logo 1', 'Logo 2', 'Upsell Article' and 'Add-on Article' fields.
|
AVD-1545 |
Business Intelligence and Reports Fixes
|
Issue |
Solution |
ID |
|
Allow BI queries to be run against the reports database (if one exists). |
This has been implemented in AudienceView 6.3.0 HotFix 13
The 'Default Reporting Database' field has been added to the Registry application System::Application node to allow BI queries to be run against the reports database.
The value entered in this field should match the 'Node Name' of the database configured in the Registry application System::Databases section.
When this value is set, all BI queries will be created with the configured value by default.
 |
Hint
This field only defines the database for BI queries. If you want to run reports against the same database, you must define it in the Registry application Registry::Business Objects::TSreportBO::Reports::Database node's 'Default Value' field. |
|
AVD-1556 |
Performance Fixes
|
Issue |
Solution |
ID |
|
The AudienceView Online viewOrder.asp page updates customer fields ('Associations') that are not directly related to the order being created. |
This has been corrected in AudienceView 6.3.0 HotFix 13.
Records are no longer being updated if there has been no change to the 'Associations' when the order is created. |
AVD-1644 |
WebAPI Fixes
|
Issue |
Solution |
ID |
|
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. |
This has been corrected in AudienceView 6.3.0 HotFix 13.
If a 'Page Size' has been defined in a WebAPI call, it will override tghe 'Page Size' setting in the article/Registry. |
AVD-1449 |
|
If branding has not been loaded then TScontentBO::search will not work and will throw branding related exceptions such as The site branding does not exist. TScontentBO::search should be able to run if branding is not loaded. The exception is thrown when TScontentBO::search tries to load the default search article. This problem prevents the WebAPI from running TScontentBO::search since WebAPI does not initialize branding. |
This has been corrected in AudienceView 6.3.0 HotFix 13.
If no branding has been specified, use the default branding will be used/loaded. |
AVD-1454 |
|
The WebAPI has a hard-coded return data limit. If limit is reached, return message is Response was too large. Request Failed. Request a smaller collection of data. |
This has been corrected in AudienceView 6.3.0 HotFix 13.
The hard-coded limit has been removed and is now determined by the IIS/Tomcat configuration to restrict the response size. |
AVD-1465 |
In api.asp page, the exception object is being printed rather than the object properties. For example: <message>WepAPI call ended due to uncaught exception:[object Error]</message>.
Instead of displaying exception e, should be exception e.ErrorNumber + e.Description. This occurs in multipul try/catch blocks in api.asp. |
This has been corrected in AudienceView 6.3.0 HotFix 13.
The correct error object is being displayed. |
AVD-1477 |