Bug 724571 (BRMS-512) - Support for package level rule attributes in BRMS manager
Summary: Support for package level rule attributes in BRMS manager
Keywords:
Status: NEW
Alias: BRMS-512
Product: JBoss Enterprise BRMS Platform 5
Classification: JBoss
Component: User Interface
Version: 5.0.2,5.1.0.CR1
Hardware: Unspecified
OS: Unspecified
low
unspecified
Target Milestone: ---
: future
Assignee: Nobody
QA Contact: Lukáš Petrovický
URL: http://jira.jboss.org/jira/browse/BRM...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-12-13 21:19 UTC by Matt Davis
Modified: 2021-04-09 12:48 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed:
Type: Feature Request

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker BRMS-512 0 Major Closed Support for package level rule attributes in BRMS manager 2012-07-18 08:32:37 UTC

Description Matt Davis 2010-12-13 21:19:33 UTC 
Help Desk Ticket Reference: https://c.na7.visual.force.com/apex/Case_View?id=500A0000004Seu3&sfdc.override=1
securitylevel_name: Public

Currently, if you edit the package source in guvnor you can add package level rules attributes such as no-loop and lock-on-active.  It would be better if this were integrated into the gui instead of requiring users to edit the package source.

Also, the test scenarios will not pick up the package level attributes, so this will need to be fixed.
Comment 1 Rick Wagner 2011-08-25 19:17:57 UTC 
GSS prioritizes 'low', customer isn't waiting on anything.
Note You need to log in before you can comment on or make changes to this bug.