Pause a Loop until every Friday

Hi Robert,

i presume you are using a site workflow. These site workflows can be scheduled:

There you can configure the start date of your workflow (choose the next friday 12pm ) and configure it to repeat every 7 days. You could also use a "pause for..." action in a loop and configure it to pause your workflow for 7 days but this also means you have only one workflow instance running forever, which makes it more difficult to maintain it or report on it.

Let us know if this solves your issue.

Regards

Philipp

Is there any (good) reason for you not using a site workflow? This would be more appropriate for your requirement and you will only have one workflow running once per week. I don't see any disadvantages in using a site workflow here.

If you insist on using a list workflow you will first of all need some logic to find out which day is today (don't know if anything else but a web service is possible here) and then wait until the next friday (even more logic to implement: if today is monday wait 4 days, if today is tuesday wait 3 days, ...). This is possible, but imho completely unnecessary because the site workflow schedules take this pain away from you.

Sure it will! The only thing you lose is the possibility to target your "current item" because you just dont have that in a site workflow. But you can always query all lists to get the items you want and treat the item as current item. Which means it maybe a tiny bit more complex to design this workflow, but you can do the same as within a list workflow. Plus you have the scheduling possibilities.

If you need further assistance while creating this site workflow, just let us know. The comm will be glad to help

Cheers

Philipp

I presume you configure your query list action to get the assignee of each task where the status is not completed or cancelled and area field equals pmo. As a result you will get a collection of all the assignees. You need to store this collection in a variable of type collection and use a "for each" action to perform some actions for every item in your collection.

For example if you get back a collection of multiple users (assignees) you need to loop through the collection and put your request data in the for each loop of the collection variable.

Of course you only get one task if you only enter yourself as assignee, this is regular behaviour. Why should nintex create more tasks? (This is why you need the loop)

And for the wf error I would ask you to provide the error message and/or the configuration of your actions.

Regards

Philipp

You're most welcome, this is what the community is here for

You are right, inside the loop the tasks are assigned serially. You would need to use parallel paths instead of a loop if you need your tasks assigned all at once. Another workaround is to create a SharePoint group. Inside your workflow you store all users of your collection inside the group and assign the task to the whole group. You have the option to create individual tasks for all group members. When the workflow is about to end, you delete everybody from the group so you have it cleaned up for the next process running.

For adding a user to a group you can use the call web service action and use the usergroup webservice (AddUserToGroup method) SharePoint offers: https://msdn.microsoft.com/de-de/library/office/websvcusergroup.aspx and you can do this inside your loop.

Your filter configuration doesn't look wrong. However there is a help post about logical operators you can have a look at: http://help.nintex.com/en-US/O365/Default.htm#O365WorkFlow/Getting%20to%20know%20NWO/Boolean%20logic%20operators.htm?Hig…

Can you make sure that you have all different states available as well as items where the area is different than "PMO"?