Bug 1318663

Summary: Empty Task Does Not Generate Claim/Complete Form
Product: [Retired] JBoss BPMS Platform 6 Reporter: Justin Holmes <jholmes>
Component: jBPM DesignerAssignee: Tihomir Surdilovic <tsurdilo>
Status: CLOSED EOL QA Contact: Kirill Gaevskii <kgaevski>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 6.3.0CC: lpetrovi
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-03-27 20:04:24 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Justin Holmes 2016-03-17 13:20:37 UTC 
Description of problem:
When creating a process, if I model an empty task (no variable assingments, task name), only a group entry, then the resulting form generated does not have the buttons to complete

Version-Release number of selected component (if applicable):
6.3.0.DR2

How reproducible:
100%

Steps to Reproduce:
1. Create a process with a human task. Only fill out the Groups field, do not make assingments, do not fill out any task name
2. Build and deploy
3. Claim the task

Actual results:
No buttons in form to save/complete/release task

Expected results:
Buttons to save/complete/release the task present

Additional info:
This is a contrived example, but its the type of thing that a beginner just using the product might do (or someone who knows the product but is being lazy). This type of task should either a) fail compilation or b) product a workable form.

From my testing, so long as the task has a name (even if no task name is present), then the form generates properly.

I have a demo env you can use these bugs. Please email me at jholmes for access.