I have a site that has a complex set of permissions and roles to support a workflow we have defined with Workbench Moderation. This particular workflow has the "normal" three states:

Draft
Needs Review
Published

The workflow is set up to allow both forward progression through the workflow (eg, Draft to Needs Review) and also backwards (eg, Needs Review to Draft). The site also uses the basic features in Workbench, and content creators like the My Content, My Drafts, and Needs Review, etc, pages / views that it provides.

OK, here is my problem. One of the common tasks are editors pushing nodes back to Draft status for original authors to do major work on. The problem is that if you examine node_save, revisions have their $uid set to the used who did the save (ie, $user->uid). In this case, it would be the editor. Therefore, the new draft shows up in the editor's queue and not the original author's (if you examine the view for this page, you can verify this behavior).

I am curious whether others have run into this problem and how they solved it.

Thanks in advance!

Comments

vchen’s picture

vchen commented

I have the same issue. I found I was able to locate the draft on the original author's workbench if I enabled "Use 'Needs review' workbench tab" for the original author. I wish I could filter the views results so that it's tailored to who's logged in. When this permission is enabled, the original author also gets to see everyone else's drafts.

vchen’s picture

vchen commented

Even better than my previous suggestion. This will create a new tab in Workbench that shows the current logged in user what they've created. You can fine tune it if you want to filter it by Drafts only, or whatever Moderation state.

Clone My Drafts view and call it whatever you like (ie My Reviews). Creating a new page view will automatically create a new tab in the workbench interface.

Change Display Name, Title, Path, and Menu: Tab (the menu tab is where you change the tab display name)

In Relationships:
Add Content: Author,
Relationship: Get the actual content from a content revision.
Identifier: author

In Filter Criteria:
Change: (revision user) User:Current(Yes) > (author) User:Current(Yes)

In Fields:
Change the Aggregation settings on: (Get the actual content from a content revision.) Content: Nid (Nid) > Minimum (if left by default, for some reason, the node will repeat for every revision that was done to it. Setting it to a minimum, I found, makes it only appear once...similar to the multiple field display setting)

I hope this helps.