Bug 813309

Summary: NPE when generating task forms and there is a human task, whose TaskName is not set
Product: [JBoss] JBoss Enterprise BRMS Platform 5 Reporter: Jiri Locker <jlocker>
Component: BRM (Guvnor)Assignee: manstis
Status: VERIFIED --- QA Contact: Jiri Locker <jlocker>
Severity: high Docs Contact:
Priority: unspecified    
Version: BRMS 5.3.0.GACC: rzhang
Target Milestone: ER7   
Target Release: BRMS 5.3.0.GA   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 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:
Attachments:
Description Flags
server.log none

Description Jiri Locker 2012-04-17 13:11:49 UTC
Created attachment 578026 [details]
server.log

Description of problem:
NullPointerException is really not what user wants to see.

Version-Release number of selected component (if applicable):
ER5

How reproducible:
always

Steps to Reproduce:
1. create a process with a User task node
2. click Generate Task Form Templates
  
Actual results:
HTTP Status 500 (uncaught NPE)

Expected results:
Error message reporting which User task node is missing the TaskName value.

Additional info:

Comment 1 Zuzana Krejčová 2012-04-18 08:53:56 UTC
This is a bit crazy, but.. If you assign some group ID to the task, it does not throw that NPE, it will only generate a form for the process and won't generate it for the task. Assigning to a user doesn't have this effect.

Comment 2 Tihomir Surdilovic 2012-04-20 19:25:16 UTC
Designer will only generate the task form it the User Task defines a TaskName attribute value. Otherwise it does not know what to call the task form.

Comment 3 Maciej Swiderski 2012-04-20 21:17:32 UTC
issue was caused by missing io specification and additional check was introduced in designer to ensure proper handling.

Comment 4 Ryan Zhang 2012-04-23 07:36:02 UTC
Update status to ON_QA. Please verify them against ER6.

Comment 5 Ryan Zhang 2012-04-23 08:17:15 UTC
Confirmed that it is not picked in ER6. Change the status back

Comment 7 Ryan Zhang 2012-05-14 08:16:09 UTC
The fixed for this issue should be included in ER7. Please do verification on it.

Comment 9 Jiri Locker 2012-05-21 12:46:57 UTC
Fix verified in ER7.