CloudStreams Server
WST-6281
The lookup details provided in the REST connector descriptor for any resource are not added to node-hints of a Cloud Connector Service.
The resource metadata is not passed in the implementation where node-hints are created for a Cloud Connector Service.
There is currently no workaround for this issue.
WST-6428
While retrieving the custom operation data for a SOAP connector, the header values are not completely populated. This issue does not impact any other API usage for the service.
Workaround: View the header values in the Designer.
WST-6429
While retrieving the custom operation data for a Salesforce SOAP connector, the debugging header value is not populated. This issue does not impact any other API usage for the service.
Workaround: View the debugging header value in the Designer for the same service.
WST-6437
When multiple values are passed as a comma-separated list in a header, the values are sent, however, the input added in the Cloud Connector Service gets directly mapped to the output, leading to incorrect output.
Workaround: Use a single value in the header.
WST-6485
In the Microsoft Azure Storage connector, for the putBlob operation, configuring the blob name with the special character slash ('/') is not allowed.
In the Microsoft Azure Storage connector, for the putBlob operation, configuring the blob name with consecutive slashes (e.g. "ab//cc") or beginning with a slash (e.g. "/testfile") results in a 403 error.
Workaround: There is currently no workaround for this issue.
WST-6533
Even though the connection is already enabled, enabling a listener triggers an unnecessary login call to Salesforce.
This issue is observed for basic connections only.
There is currently no workaround for this issue.
WST-6537
Nested business objects are not handled while creating a custom operation.
While creating a custom operation, details associated with business objects can be provided for Complex type operations.
Currently, the CloudStreams APIs support one-level business object fields only.
Workaround: The custom operation that is created using the API can be updated in the Designer. Choose the related or nested business objects while updating the custom operation.