Hi
@JiriHlucil,
**Replying in the thread as DM's don't seem to work for me.**
Thank you for sharing the WSDL with me. Unfortunately, I cannot test with this as there are several referenced WSDL's within it. I would have to have all of the associated WSDL's.
As I mentioned in my previous post I'd suggest opening a ticket with support on this one. I have a feeling this is simply the way the logic for handling WSDLs works in Blue Prism.
As an alternative, you could look at generating the C# class(es) to handle this WSDL using the .NET tools like
wsdl.exe or
svcutil.exe. You could then copy those class definitions into a VBO definition in Blue Prism. There's more to it than what I've described, but it's an option if support comes back with "works as designed".
Cheers,
------------------------------
Eric Wilson
Director, Integrations and Enablement
Blue Prism Digital Exchange
------------------------------