Bug 724571 (BRMS-512)

Summary: Support for package level rule attributes in BRMS manager
Product: [JBoss] JBoss Enterprise BRMS Platform 5 Reporter: Matt Davis <mattd>
Component: User InterfaceAssignee: Nobody <nobody>
Status: NEW --- QA Contact: Lukáš Petrovický <lpetrovi>
Severity: unspecified Docs Contact:
Priority: low    
Version: 5.0.2, 5.1.0.CR1CC: rwagner
Target Milestone: ---   
Target Release: future   
Hardware: Unspecified   
OS: Unspecified   
URL: http://jira.jboss.org/jira/browse/BRMS-512
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: Type: Feature Request
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

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.