Bug 773101 - Expose GroupID as property of User Task in Web Designer
Summary: Expose GroupID as property of User Task in Web Designer
Keywords:
Status: VERIFIED
Alias: None
Product: JBoss Enterprise BRMS Platform 5
Classification: JBoss
Component: jBPM 5
Version: BRMS 5.3.0.GA
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: BRMS 5.3.0.GA
Assignee: Kris Verlaenen
QA Contact: Jiri Locker
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-01-10 22:54 UTC by Jeff DeLong
Modified: 2023-05-31 22:25 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed:
Type: ---
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 813294 0 unspecified VERIFIED Add standard human task properties into designer 2023-05-15 19:53:26 UTC

Internal Links: 813294

Description Jeff DeLong 2012-01-10 22:54:20 UTC
Description of problem:

Currently the groupID property in Eclipse tooling is more convenient than in the Web Designer as this is a two-step process in the Web Designer currently:

1) In the Task properties DataInputSet attribute add a data input called:  GroupId
2) In the Task properties Assignments attribute add a new assignment:   GroupId=XYZ
where XYZ is the name of your group.

It would be great if a GroupID attribute could be added to the task properties in Web Designer.

This same capability should also be in the new Eclipse BPMN2 Visual Modeler. The more the configuration properties are consistent between tools, the easier on our users :) 

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


How reproducible:


Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:

Comment 1 Tihomir Surdilovic 2012-01-13 22:06:47 UTC
This has been added to Designer and available in war on people.redhat.com/tsurdilo/designer/master. I cannot speak for BPMN2 Modeller, but would be best to raise a separate BZ for it.


Note You need to log in before you can comment on or make changes to this bug.