For the "Call Web Service Smart Service", is there any limitation to t

Hi Mike,
Thanks for the reply. We have a custom webservice (coded in C#) where we call an initial operation to list documents with matching criteria in the client's ECM product.
A second operation will download the document.
The original endpoint name was 17 characters long (upper and lowercase) and would fail on the second operation. Changing the operation name to 6 characters (lowercase) and reconfiguring the webservice nodes seem to have resolved the issue.
We want to be sure we can avoid this problem going forward (if it is even the issue) and give our developers guidelines to work by for naming conventions.

Hi Mike,
Thanks for the reply. We have a custom webservice (coded in C#) where we call an initial operation to list documents with matching criteria in the client's ECM product.
A second operation will download the document.
The original endpoint name was 17 characters long (upper and lowercase) and would fail on the second operation. Changing the operation name to 6 characters (lowercase) and reconfiguring the webservice nodes seem to have resolved the issue.
We want to be sure we can avoid this problem going forward (if it is even the issue) and give our developers guidelines to work by for naming conventions.