topic Re: NP17 Jobs ? vs NP16 in Qlik NPrinting

NP17 Jobs ? vs NP16

Anonymous — Tue, 07 Nov 2017 08:11:12 GMT

Hello

With NP16 version : {Tasks} can be use by one job, and this Job is schedule

With NP17 Version : one task = one schedule, where I can do the same thing than NP16 version

thanks

Re: NP17 Jobs ? vs NP16

Ruggero_Piccoli — Tue, 07 Nov 2017 11:55:02 GMT

In Qlik NPrinting 17.* there is nothing similar to the Qlik NPrinting 16.* jobs.

A Qlik NPrinting 17.* task can be scheduled many times by creating a trigger for each time you want that it will be executed.

Best Regards,

Ruggero

---------------------------------------------

When applicable please mark the appropriate replies as CORRECT. This will help community members and Qlik Employees know which discussions have already been addressed and have a possible known solution. Please mark threads as HELPFUL if the provided solution is helpful to the problem, but does not necessarily solve the indicated problem. You can mark multiple threads as HELPFUL if you feel additional info is useful to others.

Re: NP17 Jobs ? vs NP16

Anonymous — Tue, 07 Nov 2017 14:25:42 GMT

Thanks Ruggero

But in my NP16 I have one job with more one Tasks (18), at each execution time is not the same for one task, and it's very important that one tasks doesn't began before previous ended. In this NP17 how i can do it ?

Thanks

Re: NP17 Jobs ? vs NP16

Ruggero_Piccoli — Wed, 08 Nov 2017 14:44:47 GMT

Hi,

You could evaluate two possible solutions:

1 - You estimate the duration of each task and trigger the next one after that duration plus a safety margin. Of course, you are not 100% sure that tasks do not overlap.

2 - You could use the Task Executions APIs https://help.qlik.com/en-US/nprinting/September2017/APIs/NP%20API/#TaskExecutions

2A - retrieve the task IDs by using the API GET /task https://help.qlik.com/en-US/nprinting/September2017/APIs/NP%20API/#tasksGet

2B - run the first task with the API POST /tasks/{taskId}/executions https://help.qlik.com/en-US/nprinting/September2017/APIs/NP%20API/#tasksTaskIdExecutionsPost

2C - retrive the status of the task by using GET /tasks/{taskId}/executions/{id}. You can jump to next step when the status is one of Completed, Aborted, Failed, Timeout or CompletedWithWarning

2D - repeat for next task

Best Regards,

Ruggero

---------------------------------------------