Receiving error when sending outbound soap message from workflow

akillius
Kilo Expert

I am working on an outbound soap call to a different application.  The SOAP message was built with the correct WSDLs and the corresponding SOAP Functions are setup.  When I do a test in from the SOAP Message itself, it is successful.  Once I proved that, I attempted to add this SOAP Message to a workflow.  When the workflow tries to execute the SOAP Message it consistently fails.  When I look at the workflow activity, I am seeing the following message:

"This object does not support the auth profile of this SOAP message function, please  use SOAPMessageV2"

I struggling to understand why this is working in the SOAP Message directly but not in the workflow.  Anyone have any ideas of why I am hitting this?

Thanks!

Andy

1 ACCEPTED SOLUTION

Thanks everyone for their responses but I ended up finding an even simpler solution.   By removing the Basic Authentication value in the SOAP Message and supply the login values as part of the workflow, I get the expected result.   When you have a value in the Basic Authentication value it forces the SOAPMessageV2 script.   By leaving it blank, it uses the SOAPMessage which is more compatible when calling the SOAP Message activity in a workflow.


View solution in original post

11 REPLIES 11

Alikutty A
Tera Sage

Hi Andrew,



Please use SOAPMessageV2 API instead of SOAPMessage API. I don't think you can test the API from the SOAP message, SOAPMessage does not support authentication through basic profiles and since you have created a profile SOAPMessageV2 can be used.



Sample Code



var sm = new sn_ws.SOAPMessageV2("SOAP Message","insert");


sm.setStringParameter("short_description","Test");


sm.setStringParameter("","");


sm.setStringParameter("","");


var response = sm.executeAsync();



SOAPMessageV2



Thanks


Please Hit like, Helpful or Correct depending on the impact of the response


giriraj
Giga Contributor

Hi Andrew,



As Alikutty said please use SOAPMessageV2.



For using a specific profile, you can directly configure this where you have setup the Outbound SOAP message. This way you can avoid programmatic change and make it a configurable thing.



However, if you are going to call the same service with different profiles, using in the code is the better option.



Thanks


Please Hit like, Helpful or Correct depending on the impact of the response


Thanks for the response.   My problem is that I am using SOAPMessageV2.   When I preview the script from SOAP message, I see the following:


find_real_file.png


But when I attempt to the call this from the SOAP Message option in the workflow, I am seeing the following:


find_real_file.png



Is there a setting within the workflow SOAP Message that I am missing?   We do not currently own orchestration but I have attempted this is Eureka and it worked as expected.  



Thanks


Andy


Hi Andy,



I just looked at the activity definition, seems like it is currently using SOAP Message class instead of SOAP Message V2,



https://yourinstance.service-now.com/wf_activity_definition.do?sys_id=9359a22ac0a801975710cd9e7daa8b...



So, you could create a copy of the same activity by replacing SOAPMessage to SOAPMessagev2 at line 54, or populate your Soap message basic auth user and basic user password fields instead of basic auth profile.