In workflows with large number of states and user roles, when you add a new field or a taxonomy, you have to edit every state, even if the settings for that field or taxonomy are the same across every state. It would be a very handy alternative if you had a field page, where you could edit all the states for that field at once.

Comments

infojunkie’s picture

infojunkie
Location Vancouver
CreditAttribution: infojunkie commented

Thanks for the suggestion. Would you be interested in coding this? I can help.

Encarte’s picture

Encarte CreditAttribution: Encarte commented

Sorry, but I have no coding skills. For now, all I can do is give improvement ideas and help testing.

I have no idea if this suggestion is something simple or impossible. I came up with it while studding other access modules and understanding that there are lots of problems that can be solve with workflow/workflowfields with no need for any other access module. Problem is that changing a node type structure (adding fields or terms to node types) is very hard (not complicated but click consuming) when it belongs to a 10+ states workflow (you have to configure that field in each one of the 10+ states). That's when you start thinking in other access modules. And it's just a UI problem.

For instances, I have a case-study where workflow/workflowfields could be used instead of TAC or TAC Lite with the advantage that all users can see that the node is there (workflow view permission) but only some users can actually see what's in the node besides the title (workflow fields). Its simple to set up a workflow with states matching the terms you need to work with (rules will soon detect taxonomy and select the correct state for the node). But having to edit every 10+ states every time a field is added to that node type: that's a big problem. That's when you think that you should stop being creative and stick with TAC or TAC Lite. But it's just a UI problem. But... where are all other access modules when a lonely field or term needs them and needs them now and not in other situation?

techypaul’s picture

techypaul CreditAttribution: techypaul commented

+1 (sorry, no coding skills either).

We have 15 states and 30 cck fields (engineer job reporting). This is the perfect module for what I need but its a bit of an issue if we decide to move things around...!