|
Issue |
Solution |
ID |
|
Empty strings are returned as an empty array in JSON. |
This has been corrected in AudienceView 6.5.2 HotFix 1.
An empty multi now return as an empty string. The following syntax should be used:
-
Non-multi, has a value: NAME:"VALUE"
-
Non-multi, null/empty: NAME:" "
-
Multi, null/empty: NAME:[ ]
-
Multi, single value: NAME:["VALUE"]
-
Multi, multiple values: NAME:["VALUE_1", "VALUE_2"]
|
AVD-1104 |
|
An invalid BO handle will fall through to the default/unknown exception response (WebAPI result code 6). This deserves a dedicated result code and message. |
This has been corrected in AudienceView 6.5.2 HotFix 1.
Status code 33 has been added to identify a business object that does not have a handle in the cache. |
AVD-1206 |
|
The error JSON response is inconsistent between the Java and ASP versions of the WebAPI. For example, the Java version outputs Error level whereas the ASP version outputs error. |
This has been corrected in AudienceView 6.5.2 HotFix 1.
The error JSON response is now consistent between the Java and ASP versions of the WebAPI. |
AVD-1217 |
|
In the ASP WebAPI, it is possible to GET the primitive value, but not its DETAILS. |
This has been corrected in AudienceView 6.5.2 HotFix 1.
The node search method for DETAILS differed from that used for GET.
DETAILS has been updated to utilize TSbusinessNode::findInTree(context) so that it is consistent with the other WebAPI GET and SET implementations. |
AVD-1218 |
|
The WARNING parameter does not suppress messages in ASP. |
This has been corrected in AudienceView 6.5.2 HotFix 1.
The WARNING parameter has been renamed ACCEPTWARNING, and messages are being surpressed as expected. |
AVD-1224 |
|
The COM implementation is corrupting the api.asp result because the BSTR constructed and passed to the ASP is relying on a temporary variable that is freed mid-stream. |
This has been corrected in AudienceView 6.5.2 HotFix 1.
The BSTR construction and handover to ASP has been corrected. |
AVD-1300 |
|
Site should be optional. |
This has been corrected in AudienceView 6.5.2 HotFix 1.
Site is no longer required when initializing the site. |
AVD-1453 |
|
When requesting WebAPI/session?DETAILS=Printers, an error occurs even though Printers is a valid node. |
This has been corrected in AudienceView 6.5.2 HotFix 1.
The auditHistory parameter value has been added to toXML and toJSON node method invocations. It is now possible to request WebAPI/session?DETAILS=Printers.
 |
Caution
The ticket stock values in the stock list cannot contain any spaces in either the 'Key' or 'Entries' fields. This will be corrected in a future release (AVD-1108). |
|
AVD-1460 |
|
The work message is in an inconsistent location between the Java and ASP versions. In ASP, the work message is under the data object; however, in Java, the message is not under the data object. |
This has been corrected in AudienceView 6.5.2 HotFix 1.
The JSON WebAPI response incorrectly assumed that a data element always followed the result. It is now conditional. |
AVD-1461 |
|
Exception details are not being returned. |
This has been corrected in AudienceView 6.5.2 HotFix 1.
The exception details are now being returned. |
AVD-1462 |
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.5.2 HotFix 1.
The correct error object is being displayed. |
AVD-1717 |
|
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.5.2 HotFix 1.
If a 'Page Size' has been defined in a WebAPI call, it will override tghe 'Page Size' setting in the article/Registry. |
AVD-1718 |
|
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.5.2 HotFix 1.
The hard-coded limit has been removed and is now determined by the IIS/Tomcat configuration to restrict the response size. |
AVD-1719 |