Forum Discussion

jhagist's avatar
jhagist
New Contributor III
8 years ago
Solved

Rest API Test For Completion

I have a pattern where I run a REST POST api call and then need to run a REST GET to see if the request has completed. I need to somehow loop back to run the REST GET again if it isn’t done. Recom...
  • psathyanarayan's avatar
    psathyanarayan
    7 years ago

    According to my esteemed colleague @akidave, we do allow POST data directly to XML Parser snap through a triggered pipeline which in your case would be the API end point. If your first snap in the pipeline is the XML Parser, you should be able to process it and your pipeline is a triggered pipeline, you should be able to send the XML encoded POST data to this triggered pipeline.

christwr's avatar
christwr
Contributor III
7 years ago

I had that error too…

I was intrigued by the looping logic mentioned in the thread above because I had never seen or thought about doing something like that. But when I put together a simple pipeline to try and test it out (see below) I get the same StackOverflowError when trying to run or validate the pipeline.

As far as the snap it is failing on, I think it just mentions the first snap, but really failed trying to prepare the pipeline, not necessarily with the first snap…

cstewart's avatar
cstewart
Former Employee
7 years ago

The way to address this one is to use the REST GET Snap, and use the HAS NEXT functionality. You can make it iterate until the correct response is received.
(You may not have a loop in a pipeline)

  • jbaldetti's avatar
    jbaldetti
    Former Employee
    9 years ago

    Workday publishes some WSDLs in the Workday Services documentation site without a valid endpoint for the purpose of reference. This can be verified by opening the WSDL file and look at the soap address location at the bottom of the WSDL. A valid endpoint for workday should have a location starting with the “https://” protocol.

    Here is an example of a valid endpoint at the end of the WSDL file:
    …
    <wsdl:service name=“Human_ResourcesService”>
    <wsdl:port name=“Human_Resources” binding=“wd-wsdl:Human_ResourcesBinding”>
    <soapbind:address location=“https://impl-cc.workday.com/ccx/service/osv_fusionio4/Human_Resources/v18”/>
    </wsdl:port>
    </wsdl:service>
    </wsdl:definitions>

    If it does not have the “https://”, then the solution would be to export the Workday WSDL from the Workday tenant.

    The Workday snap is a preferable over the SOAP snap since it is an easier to use and more capable.