Service Development 10.15 | Other Resolved Issues | Release 9.12
 
Release 9.12
*WED-6034
Designer fails to handle the URL redirections while creating Integration Server elements.
In Designer, if the URL has redirection, creation of Integration Server elements, such as web service descriptors, document types, and Integration Server schema from external URL fail.
This issue is now fixed.
*WED-5592
Tooltips remain frozen in Designer.
In Designer, the document or flow editor tooltips remain on the screen even after closing the editor using the keyboard shortcut Crtl+W.
This issue is now fixed.
*WED-5820
Designer fails to display the details of Forms tab for Custom Remedy Adapter.
Forms tab does not display the details of Custom Remedy Adapter service such as the 'Selected Form' details in Designer.
This issue is now fixed.
*WED-5611
Web service descriptor fails to generate xsd:any element and attributes when the 'Allow unspecified fields' property is set to true.
The WSDL document for a web service descriptor does not include the xsd:any element and attributes when the web service descriptor uses a Document variable for which the 'Allow unspecified fields' property is set to true. This issue occurs even if the server configuration parameter watt.core.schema.createSchema.omitXSDAny is set to false.
This issue is now fixed.
*WED-5210
When unresolved package issues are manually resolved in a Java service, Designer does not append the import details correctly to other Java services in the same folder of the package if they are also open in the editor.
While editing Java services, upon doing an Organize Imports operation in a Java service, Designer removes necessary import details of other Java services that are in the same folder in the package if they are currently open in the editor. If the import details that are removed from the other services are manually resolved, the import details of the first service get corrupted, instead of getting appended to the existing import details.
This issue is now fixed.
*WED-6204
The field name abbreviator, as used for XmlData, truncates the field names that start or end with '#'.
When you run a flow service, Designer fails to display the parameter names that start or end with # in the Results window. The Field name abbreviator, as used for XmlData, truncates the field names that start or end with '#'.
This issue is now fixed.