In my quest to integrate queues (workload management package) without API's I encounter some problems/questions.

1) is it possible to loop through each queueitem with status 'New'? I only see the option Onhold, data error, failed. This parameter is not optional, so i can not leave it blank.
2) is it possible to use the action 'Workload: update work item' outside of the "loop for each queueitem" but inside a task bot that uses a workload template? When yes, how can i get the workItemID of the currently picked up workItem? Is there a default attribute i can address to collect this data from the workitem itself?
3) when non of the above is possible: is there a way to process queueitems without needing to re-do overhead steps again and again and a again for each picked up workitem without the usage of the WLM API's? It is a waste of time to login to UI applications, get accesstokens, get credentials, check environments each time again. By doing this a lot of valuable time is lost!

4) Is it possible to insert/create a new workitem with a delay for processing? I see that this is possible through the update work item action, but i do not see how i can achieve this with the insert work item. I want to diversify in the waiting time for re-processing an item depending an its status. for example: when a work item is still being processed in an other application, i expect it to be ready within seconds and try again right away. When the status is In progress, some one needs to take manual action before necessary additional information will be available. employees do this only twice a day! so keep on polling continuously is not an option.
5) are changes relating WLM scheduled in the upcoming releases. v35 or v36?
6) Is there any transparent exhaustive uptodate documentation on working with workload package without API's?

Kind regards,

Jan