DNG Workflow vs Attribute
It seems like in some ways workflows are just glorified enum attributes.
They are more a of a guddle to setup and maintain than a simple enum attribute.
It seems like the main benefit is that you can put state specific access controls on artifacts based on their work flow state.
Would it be fair to say that if you have no need to control edit access to an artifact type based on a workflow state then an enum attribute is better (simpler) than a workflow for simply tracking the 'state' of an artifact - or are their other benefits to workflows?
|
2 answers
Workflow's were designed to control edit access to requirements based on defined "states" of the workflow. If you don't plan on using this feature, then using an enumerated attribute would be the recommendation for sorting, querying, and reporting on requirements.
|
|
^Thanks Amit.
Thinking about it more I guess process control over state transition would be another benefit - where you can control who can change to particular states.
Attribute change control on the other hand would affect all values of the enum.
But I can't think of anything else.
|
Your answer
Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.