Workflow Fields

This module extends Workflow by allowing CCK node fields to be made invisible or read-only depending on the current workflow state. The workflow state form is extended to show all node fields with appropriate controls to hide and/or disable each field for that particular state.

This functionality is useful when a workflow moves among users who have different permissions regarding the document flowing through them. Which is the case in most every workflow we've encountered.

WARNING IF YOU USE WORKFLOW 2.0

The current stable release is NOT compatible with Workflow 2.0
Instead, use the development release (or even better, the git one) and give us your feedback.
It is in beta, but it should normally work.
Based on that, we'll issue a new stable release.

WHAT'S NEW ?

Various bug fixes and improvements were done in terms of usability and user-friendliness.

USAGE

When the module is enabled, the "Edit workflow state" page is augmented with a list of fields that correspond to the content types using the workflow. You can specify whether each field should be visible or read-only, per user role, when the node's workflow is in that particular state. The visibility flag applies to both the view and edit pages of the node.

FAQ

How does Workflow Fields interact with other field access control modules?

According to this thread and this article,

Node access modules always GRANT access and never restrict it. (It is a whitelisting rather a blacklisting system.) If you use two node access modules and one grants access while another does not, access is granted.

If you notice something different, please update the thread.

MAINTAINERS FOR D6 ARE WELCOME

Workflow Fields has now 2 new maintainers for the D7 release :

• hbemtec
• mitjasvab

Maintainers for the D6 release are welcome. "We want you !" (pointed finger)