DNG Default Workflow end state 'complete'
Why does the default workflow end in the state 'complete' regardless of whether a requirement is accepted or rejected?
Is there any reason why workflows should have a single end state?
If 'rejected' requirements had a final state of 'rejected' then would that not make them easier to identify?
Are workflows equally easy to report on as attributes? I know the simpler enumerated 'status' attribute approach makes reporting simple. Using a workflow instead is nicer but are there any penalties in terms of simplicity of reporting filtering etc. on requirements using a workflow instead of a simple 'status' attributes?
Comments
Softacus AG
Aug 21 '18, 2:36 p.m.After you reject the state is Rejected. You can change and add own workflows
Sean F
Aug 22 '18, 11:11 a.m.