| Summary: | Swimlanes available in rules flow interface (Eclipse) | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [JBoss] JBoss Enterprise BRMS Platform 5 | Reporter: | Eric D. Schabell <erics> | ||||
| Component: | Tooling (JBDS) | Assignee: | Kris Verlaenen <kris.verlaenen> | ||||
| Status: | CLOSED WONTFIX | QA Contact: | |||||
| Severity: | unspecified | Docs Contact: | |||||
| Priority: | medium | ||||||
| Version: | 5.0.0 GA | ||||||
| Target Milestone: | --- | ||||||
| Target Release: | --- | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| URL: | http://jira.jboss.org/jira/browse/BRMS-209 | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: |
fedora 10, JBoss DevStudio 2.0.0.GA, x86_64
|
|||||
| Last Closed: | 2011-04-21 23:24:33 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: | |||||
| Attachments: |
|
||||||
|
Description
Eric D. Schabell
2009-07-30 20:16:46 UTC
Screenshot showing the Swimlanes. Attachment: Added: Screenshot-Drools-rulesflow-swimlanes.png Kris: Is this still the case in D5.1? If not please close, otherwise (if valid) set target to "future". 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. Won't fix this as part of this editor, will be supported in the new editor |