Cross-post from Workflow Group - Setting up Round-robin work assignment

Events happening in the community are now at Drupal community events on www.drupal.org.
SiteMaster.ServeLime.com's picture

Hi SA

Anybody familiar with NodeQueue + Actions/Workflow/Workflow_NG that can help with this one?

The original is posted here: http://groups.drupal.org/node/17053

The Scenario:
a. Queue containing current list of target workers (UserNode + NodeQueue ?)

b. On submission of a new Target Node, assign the next worker from the queue (Action / workflow_ng ?)
The worker goes back into the queue (round-robin)
*** This bit seems to require a custom-action using PHP (workflwo_ng?) - this is where I'm stuck ***

c. Allow that worker to view their assigned target nodes ("accept" it on update by them)
View filtering on the AssignedTo CCK field + workflow state ?

Thanks

Comments

Drupal 5 or 6?

Max_Headroom's picture

Just to clarify:
Drupal 5 > Workflog_ng only, but also have actions.
Drupal 6 > triggers and actions only. (last time I checked :) )

Sounds like you will need a small custom module that gets triggered every time a user post a node. Some simple array manipulation of a group of user IDs.
And then storing of assigned node IDs under user names. worker gets email, and worker can also get a notice when he logs in.
Worker can also see and tick of work done on a table. Node gets published after review.

Hmmm, OK, the module is not so small any more :) , but it can be done.

Quentin
www.webnthings.co.za

Quentin

SiteMaster.ServeLime.com's picture

Thanks Quentin.

Oops. Yes Drupal 5.

I'm focusing on using NodeQueue to list the available Target Users (or more precicely, their User Node IDs).

My challenge is thus to pick up the next available entry from this queue on Submit of a new Target Node.
... and then to stick the User Node ID back into the queue.

I see the need of a (custom PHP?) action to do the following on Submit:
1. Fetch the next UserNode ID entry from the queue (from front - oldest)
2. Retrieve the Author ID (USer ID) from the User Node (same as user it belongs to)
3. Save the User Id into a CCK field on the Target Node
4. Put the UserNode ID entry back on the queue (at back - now newest)

A View can then be used to Filter the Target Nodes for a User.

Basic, but should work...

Any suggestions on implementing the above 4 steps anybody?

Emile
Entrepreneurship is a journey to a fulfilled life - make it so.

Emile Botha
Entrepreneurship is a journey to a fulfilled life - make it so.

South Africa

Group notifications

This group offers an RSS feed. Or subscribe to these personalized, sitewide feeds: