Bug 114169

Summary: 'Select a Workflow' in item creattion useless
Product: [Retired] Red Hat Enterprise CMS Reporter: Jon Orris <jorris>
Component: otherAssignee: Scott Seago <sseago>
Status: CLOSED RAWHIDE QA Contact: Jon Orris <jorris>
Severity: medium Docs Contact:
Priority: medium    
Version: nightly   
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2004-01-26 21:54:41 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---
Bug Depends On:    
Bug Blocks: 106481    

Description Jon Orris 2004-01-23 16:04:12 UTC
Description of problem:

If the SWA attempts to create an Item, a 'Select a Workflow' label
will show up. If the SWA creates the Item, the sytem will refuse,
saying that the Workflow parameter is required.

The problem is that there is no workflow select widget, just a label,
making it impossible to fulfill the requirements to submit the form.

Comment 1 Scott Seago 2004-01-23 16:09:58 UTC
Actually, it's not useless -- It's just missing the proper "you don't
belong to any workflows" label when there are none to choose from. It
_may_ be that the proper thing to do here is that for users with the
Item Administration function we want to show all workflows. We've got
to be careful with that, though, because once the item is assigned a
workflow, the SWA won't be able to edit anyway (without stopping the
workflow), since you can't edit an item in a workflow without locking
it, and you can't lock it without being assigned it.

Comment 2 Scott Seago 2004-01-23 18:26:54 UTC
ok, so I think I will, in the case where an admin (or anyone with
apply alternate workflow permissions) has no workflows to choose from,
we'll hide the entire widget, and apply the default workflow insead.
So here's the behavior:
1) if user has apply alternate workflow permission and belongs to one
one more workflows, the user gets the form (with >=1 choice) and it's
2) otherwise apply the default.

Comment 3 Scott Seago 2004-01-23 20:33:48 UTC
I've applied the fix as described above. Notice that even with the
fix, the admin in question will be able to create the item, but he
won't be able to edit it unless the admin gets added to the workflow
_or_ the workflow is stopped, since an item in an active workflow
can't be edited without a locked task.