Bug 724264 (BRMS-209) - Swimlanes available in rules flow interface (Eclipse)
Summary: Swimlanes available in rules flow interface (Eclipse)
Keywords:
Status: CLOSED WONTFIX
Alias: BRMS-209
Product: JBoss Enterprise BRMS Platform 5
Classification: JBoss
Component: Tooling (JBDS)
Version: 5.0.0 GA
Hardware: Unspecified
OS: Unspecified
medium
unspecified
Target Milestone: ---
: ---
Assignee: Kris Verlaenen
QA Contact:
URL: http://jira.jboss.org/jira/browse/BRM...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-07-30 20:16 UTC by Eric D. Schabell
Modified: 2011-04-21 23:24 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
fedora 10, JBoss DevStudio 2.0.0.GA, x86_64
Last Closed: 2011-04-21 23:24:33 UTC
Type: Bug


Attachments (Terms of Use)
Screenshot-Drools-rulesflow-swimlanes.png (124.25 KB, image/png)
2009-07-30 20:17 UTC, Eric D. Schabell
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker BRMS-209 0 None None None Never

Description Eric D. Schabell 2009-07-30 20:16:46 UTC
securitylevel_name: Public

Will attach screenshot, but the rules flow interface for a flow shows Swimlanes in the properties tab of the JBoss DevelStudio, when there is absolutely no way to assign/define a task in a flow. I would expect that this did not get removed when productizing this for JBoss BRMS release?

Comment 1 Eric D. Schabell 2009-07-30 20:17:37 UTC
Screenshot showing the Swimlanes.

Comment 2 Eric D. Schabell 2009-07-30 20:17:37 UTC
Attachment: Added: Screenshot-Drools-rulesflow-swimlanes.png


Comment 3 John Graham 2010-09-10 18:48:05 UTC
Kris: Is this still the case in D5.1? If not please close, otherwise (if valid) set target to "future".

Comment 4 Kris Verlaenen 2010-09-14 00:41:06 UTC
You can assign human tasks to swimlanes simply by specifying which swimlane they should belong to as the value of the swimlane property.  The productization removes a few of the node types from the default palette.  The user however can always customize the editor to select which nodes should be allowed, including the human task node.  This filtering only works on a node level, so it is not possible to remove/filter one specific property only at this point.

Comment 5 Kris Verlaenen 2011-04-21 23:24:33 UTC
Won't fix this as part of this editor, will be supported in the new editor


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