Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1078160

Summary: jBPM Designer does not create the default work item definition if custom one has been created first
Product: [Retired] JBoss BPMS Platform 6 Reporter: Radovan Synek <rsynek>
Component: jBPM DesignerAssignee: Tihomir Surdilovic <tsurdilo>
Status: CLOSED NOTABUG QA Contact: Radovan Synek <rsynek>
Severity: high Docs Contact:
Priority: medium    
Version: 6.0.1CC: kverlaen, rrajasek
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: 2015-12-07 16:50:25 UTC Type: Enhancement
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
screenshot none

Description Radovan Synek 2014-03-19 09:55:54 UTC
Created attachment 876289 [details]
screenshot

Description of problem:
When a user creates custom work item definition before opening jBPM Designer, the Designer does not generate the default work item definition. This default WID contains REST task, Web Service task, etc. and as a result these tasks are not available in jBPM Designer. This applies to every package in a project, because the Designer keeps the default WID for every package separately. 

Version-Release number of selected component (if applicable):
6.0.1.ER2

Steps to Reproduce:
1. login to business-central
2. create a repository & project
3. create a custom work item definition
4. create new BPMN process
5. jBPM Designer opens and there are no service tasks to use.

Of course, there is a "workaround" - to delete the custom WID, create a process to open Designer (it generates the default WID), close it, create the custom WID once more.

Additional info:
could it be possible to keep the default work item definition in ${project_name}/global in order to not duplicate the same data?

See the attached screenshot - no default WID, no service tasks.

Comment 1 Radovan Synek 2015-12-07 16:50:25 UTC
Closing the issue as the current behaviour can be hardly considered as a bug. User's WID should take precedence over the one generated by Designer.