XMPie uProduce SOAP API: filter Jobs_SSP.GetDataSet by Env Job Name / Job Group, or by a list of Job IDs?

[Scott Snowball]

GDay, 
I'm using XMPie uProduce API 9.2.1 (Build 10766) via the Jobs_SSP.asmx SOAP service. My application submits batches of related production jobs to XMPie —
  each batch consists of N jobs that share a common EnvJobName (set per-ticket via JobTicket_SSP.SetEnvJobName), and the jobs all live under the same XMPie
  campaign and document.

  After submission I need to poll the status of just the jobs in one specific batch every few seconds — across all of Waiting / In Progress / Complete /
  Failed statuses. Once each job hits Complete I download its output file; once they're all terminal  they  can then go onto the next process.

  What I'm trying to avoid: calling Job_SSP.GetStatus(jobId) once per job. For a 250-job batch that's 250 SOAP round-trips per poll tick, which is far too
  slow. I'd like to fetch one DataSet per tick instead.

  I've been looking at Jobs_SSP.GetDataSet:

  This is almost what I want — I can filter to my account / campaign / document / job type / status, but I can't see a way to constrain to:

  1. A specific Env Job Name / Job Group (the string I attached to each ticket via SetEnvJobName), nor
  2. A list of Job IDs (the IDs I got back from the per-ticket Run calls).

  Questions:

  1. Does any of the existing GetDataSet parameters actually filter by Env Job Name? If so, which?
  2. If not — is there another XMPie API call (perhaps on Job_SSP.GetDataSet singular, or another service) that lets me batch-query by a JobID list or by a
  custom property?
  3. Failing those, is the recommended pattern just to call Jobs_SSP.GetDataSet constrained to my account + job type + a Waiting,InProgress status filter
  (if inStatus accepts a comma-separated list), then filter to my batch's Job IDs client-side?

  What I'd like to end up with is one round-trip per poll tick that returns just the rows for the N jobs in one batch. Open to any pointer — API method,  undocumented filter, or "you're holding it wrong" advice.

  Thanks!

[Wayne]

Hi Scott,

Honestly with such an old version of uProduce you are better off either upgrading (obvious) or developing your own RestAPI to interrogate the XMPie Database directly.

Probably would require less effort.

Regards,

Wayne