Forum Discussion
terrible_towel - I'm not familiar with the JIRA API response, but if you can capture and share the output of the first response, I can help you create the Has Next and other pagination properties. Feel free to remove the actual ticket data - I just need to see the rest of the response metadata.
Thank you koryknick !
Take a look at the screenshot below please. From my understanding of the Jira API, there are 3 relevant properties here: 'startAt', 'maxResults' and 'total'. The new URI (the second and onwards) is supposed to make the same get request, but with an added suffix:
base_URI & startAt = ('startAt' + 'maxResults').
This way it's pretty easy to loop through the pages by incrementing this expression by 50 each time. Then there's the stop condition. I'm guessing something like:
when 'total' <= ('startAt' + 'maxResults')
My issue is as I've mentioned, how do i configure these expressions inside of this HTTP Client snap? how do I incorporate this arithmetic behavior? Thanks!
Is it possible for you to call a Triggered Task URL at the end of the Mainframe job schedule?
You could take a look at the File Poller snap - maybe you could simply schedule the SnapLogic pipeline on the same schedule as the Mainframe job and the File Poller would wait for the file to become available to begin the actual processing.
Related Content
- 3 years ago
- 2 years ago