cancel
Showing results for 
Search instead for 
Did you mean: 

Issue for invoking exposed blueprism process which accepts variables of type "Number"

AmitMane
Level 3
Hello team,

I have created blueprism process which accepts parameters of type "Number". I exposed this process from settings. WSDL for this process shows type for these input variables as "s:decimal". Now I am trying to invoke this exposed process from Java code as SOAP call. In java code, I used data type for blueprism process's input variable as "BigDecimal". When I run my code I get strange exception with message as below:
"Couldn't process soap inputs - Can only deal with a single request"
When I run my code there were no running process in blueprism.

When blueprism process exposes variables of type "Text" and Java code uses variable of type "String" then same code works fine. I am facing issue for "Number" type.

Any idea, how can I fix this issue? 
Thanks in advance.

------------------------------
Amit Mane
------------------------------
13 REPLIES 13

Hi Eric,

For parsing wsdl runtime we are using "predic8" library. And to invoke soap call we are using "apache axis" library. And java version is 11.

------------------------------
Amit Mane
------------------------------

Hmm, well I was able to replicate part of the error response you saw by sending non-numerical data in a request to an exposed process that expects a Number as input. In this case the error I received was:

<soap:faultstring>Couldn't process soap inputs - BluePrism.Server.Domain.Models.InvalidFormatException: Invalid value 'i' for a new number
   at BluePrism.AutomateProcessCore.clsProcessValue..ctor(DataType dtype, String val, Boolean allowInvalid)
   at BluePrism.AutomateProcessCore.clsWSDLProcess.XSDToAutomateValue(DataType dtDataType, XmlNode xml, clsCollectionInfo def)
   at BluePrism.AutomateProcessCore.clsProcessWSDL.ProcessSOAPInputs(String sInputs, clsProcess proc, String&amp; sMethod, String&amp; sSession, String&amp; sErr)</soap:faultstring>
      </soap:Fault>
​


You mentioned you're calling an exposed process. Is that process using VBOs? If so, do you know what the run-mode is on all of the VBOs? I'm wondering is perhaps you're running into a situation where one or more VBOs are set to Foreground or Exclusive?

Cheers,
 



------------------------------
Eric Wilson
Director, Integrations and Enablement
Blue Prism Digital Exchange
------------------------------

Hi Eric,

We are using FileUtility VBO to write input parameters to file. So as per your comment on safe side I removed that VBO. Still I got the same error.

------------------------------
Amit Mane
------------------------------

Hi Amit,

I'm about out of options. I think you're going to need to open a ticket on this one. 😞

Cheers,

------------------------------
Eric Wilson
Director, Integrations and Enablement
Blue Prism Digital Exchange
------------------------------