1. For Site workflow I scheduled to run every Friday and the only thing it does is to set a Friday field in the list to "Yes".

2. For the list workflow I added "Wait for item update" to wait for the Friday field to contain "Yes". Than the wf runs and the end it sets back the Friday to "No" and the loop is waiting again until the Friday is set to "Yes" again by the Site wf next Friday.

I guess pros can solve it other way, but I think this is a very easy solution to anybody who would like to use the best of both kind of WF's.

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.

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

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.

Well I tried a lot of things but its just not working the way it was with list WF.

For start the List Query is not filtering the list, its giving me all list items when I run it.

What is wrong with the setup? Just note I had to enter manually "PMO", "Completed", "Cancelled". Had no option to select from a drop down or else.

Secondly if I put the "Request Data" inside the "For each loop" it is waiting me to respond to the task and only than sending me the next one. Shouldn't it work the way that I receive all the tasks belonging to me at once? Or I miss an action to separate the tasks by users, so everybody receive only the tasks belonging to them? It was no difference if I put the create item inside or outside the loop as I noticed, but I guess it should be inside right?

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.

1. For Site workflow I scheduled to run every Friday and the only thing it does is to set a Friday field in the list to "Yes".

2. For the list workflow I added "Wait for item update" to wait for the Friday field to contain "Yes". Than the wf runs and the end it sets back the Friday to "No" and the loop is waiting again until the Friday is set to "Yes" again by the Site wf next Friday.

I guess pros can solve it other way, but I think this is a very easy solution to anybody who would like to use the best of both kind of WF's.