| |
Results |
|
SBM Web Service response is using two namespaces
|
In some cases the SOAP message returned from an SBM Web Service can use two different namespaces for its elements, where only a single namespace would be expected. The code does not correctly handle the case where the call is in one namespace and the elements type is defined in another namespace.
|
|
|
|
Specific description fields no longer translated in ZMF Connector 6.0 web service responses
|
A customer has reported that a number of fields are no longer being interpreted via the ZMF Connector 6.0 web services . For example, running the query (ZMF package search) service, the response for several *Desc fields used to be returned in the following manner:
|
|
|
|
Error occurred during web service invocation:Response failed
|
When running an orchestration, the user sees an error such as: Error occured during web service invocation: Response failed...
|
|
|
|
Handling Large Web Service Responses in Service Steps
|
To handle the fault, you should place the Service step within a Scope step and catch the fault in the Catch All branch of the FaultHandler. In addition, you should consider reducing the size of the response SOAP message's payload by redesigning the way you invoke the Service step. For example, you could add filtering if the Web service supports it.
|
|
|
|
charset specification missing from HTTP header in WS responses
|
charset specification missing from HTTP header in WS responses
|
|
|
|
If a non-privileged user tries to use WS getitemsbyquery, XML response message should not include item id reference
|
If a non-privileged user tries to use WS getitemsbyquery, XML response message should not include item id reference
|
|
|
|
Web Services XJRJESTYPE needs additional fields defined
|
Users cannot connect to ZMF from the ZMF4ECL plug-in, because Web Services rejects the ENVIRONMENT LIST response because XJRJESTYPE is D in their environment. The Web Services definition only permits '2' or '3'. Any Character should be permitted in this field
|
|
|
|
GetUsers web service call does not return a value for the "timezone" parameter
|
GetUsers web service call does not return a value for <ae:timezone/> parameter in the XML response . It does, however, return the correct GMT offset expressed in milliseconds.
|
|
|
|
Web services don't support non ASCII strings.
|
RM Web Services don't support non ASCII strings and return corrupted soap response . Steps to reproduce. 0. Run WebServices.
|
|
|
|
Using TransitionItem web service with transition of type subtask doesn't do anything.
|
Using the TransitionItem web service method on a transition of type SubTask in soapui gives all indications that the web service runs without a problem and gives a normal response but the item doesn't transition and the subtask items don't get created.
|
|
|
