AnsweredAssumed Answered

Start a workflow web service call not started

Question asked by at01 on Jul 19, 2018
Latest reply on Jul 23, 2018 by jackgelo

Hi, its my first post so sorry if its not detailed enough!

 

I followed this post and this post on starting a workflow using a webservice and it worked a treat in testing. Now i've moved it into a large doc library im getting unusual results. 

 

The first few tries the web service call was just greyed out, but now I can see that the site workflow has ran successfully, looped through and made the webservice calls on each item ID in my item ID variable, but it hasnt actually kicked off the library level workflow on each item...

Ive seen some people mention that the StartWorkflowOnListItem webservice call doesnt work on doc libraries (think thats right), but when i edit the SOAP below and remove the list ID variable for a file ID it runs and initiates the library level workflow fine.

Any ideas as to why this might be?

UPDATE: I re-ran the site workflow with no list-level workflows running and it still produced this result

<?xml version="1.0" encoding="utf-8"?>
<soap:Envelope xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/" xmlns:m="http://nintex.com">
<soap:Header>
</soap:Header>
<soap:Body>
  <m:StartWorkflowOnListItem>
    <m:itemId>{WorkflowVariable:ListItemIDs}</m:itemId>
    <m:listName>Asset</m:listName>
    <m:workflowName>Move files and leave link</m:workflowName>
    <m:associationData>
    </m:associationData>
  </m:StartWorkflowOnListItem>
</soap:Body>
</soap:Envelope>

Outcomes