Workflow

Greetings,

How can I setup workflow in such a way that the "next moderator" in the workflow is determined/evaluated during the workflow based on various conditions?

For example, suppose I have a content type "Service Ticket."

The user (who is an employee) may submit a service request to:

(a.1) Request a new workstation. Since this is an asset request, the employee's manager must approve the request before the request moves to the service desk who will process the request. in this case, when the employee submits the request, the "next moderator" is the employee's manager.

Hi,
I am using the workflow module in one of the projects and I have basically 6 workflow states. In the workflow settings I have set it like this - the author will only be able to view the content beyond a workflow state. However, while testing it, I am able to find that the author is able to edit the content beyond the workflow state. I am guessing that we need to override the role permissions with workflow permissions. How can it be done?

Am I missing something here? If so, kindly let me know as to what else might need to be done.

Thanks!

Mahi

I've got a community site with a strict membership criteria: in order to be a member one must be approved by two existing community members. Hence, the question is - what is the best way to implement such workflow. Your advice would be appreciated a lot.

During registration process new users supply the names of already registered community members who can recommend them.
These 2 members receive notification emails with activate/decline links, and make their choice.
In order to activate new user's profile it must be confirmed by both of the specified community members.

Hello. I'd like to be able to create a report that lists, for example, all content in the "needs attention by manager" state or "needs fact checking" state. I can go to individual pieces of content and get this but I'd like to get a report for the entire site.

Thanks,

• Ben

I originally setup a CCK form for authenticated users who submit a request and identify a supervisor's email address which is then used by workflow and actions to submit it to that address. The supervisor is then asked to visit the node and approve or deny the request. I originally set it up with content permissions to display certain fields accordingly (only supervisors would be able to edit the "manager's email" field), however, in this situation we have no way of separating general authenticated users from supervisors.

Hi all,

I originally posted this over at http://drupal.org/node/723310 but I thought there might be some interested parties here.

Short version:

• Break the workflow module into API, Node UI, Admin UI, Scheduler, Rules, and Actions modules.
• Make workflow "form agnostic", allowing easier use of the APIs programmatically

I've made a start at this and attached an archive of the modules to that post.

Is there a way to "mass update" or "bulk update" more than one item in Workflow to a new status ... on a scheduled date and time?

I have seen View Bulk Operations mentioned as a way to mass update the Workflow status of items; the only problem with that approach is that the change is executed immediately. I need to be able to set the date and time of the change, rather than having the status of the items changed immediately.

Any suggestions?

I'm working on a site that will take certain email traffic and publish it for categorization, FAQing, and commenting. I'd like to have an arriving email trigger an "assignment editor" function, and actually parse the email so the sender, date, etc. show up in fields, and the main content is ready to process. The assignment editor throws it out if it's irrelevant, or assigns it to an editor for further processing and tracking.

Any ideas on how to implement this? Thanks in advance.

Hello,

how can it be that there is no documentation to this module, not even a API documentation? I mean this project is designed to work into a really flexible enviroment, but there is no documentation at all. Is there a particular reason for that or did i even miss it?

This module is 3 years - really bad if there is still no documentation created.

Anybody has updates on this or is earger to help providing a documentation?