Bug 724391 (BRMS-337)

Summary: BRMS JBDS Created BRL with BRMS Fact Model
Product: [JBoss] JBoss Enterprise BRMS Platform 5 Reporter: Gary Lamperillo <glamperi>
Component: Tooling (JBDS)Assignee: John Graham <jgraham>
Status: CLOSED WONTFIX QA Contact: Martin Vecera <mvecera>
Severity: unspecified Docs Contact:
Priority: high    
Version: unspecifiedCC: brms-jira, rrajasek
Target Milestone: ---   
Target Release: future   
Hardware: Unspecified   
OS: Unspecified   
URL: http://jira.jboss.org/jira/browse/BRMS-337
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
BRMS 5.0.1
Last Closed: 2012-11-21 20:14:37 UTC 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:
Attachments:
Description Flags
BRMS_Model_import.png none

Description Gary Lamperillo 2010-06-22 21:53:49 UTC 
securitylevel_name: Public

This issue is related to https://jira.jboss.org/browse/BRMS-318

As a workaround for a Customer wanting to create DRLs in JBDS and then convert to a BRMS BRL, one workaround is to have them create a Guide Rule (BRL) in JBDS and then have them import to BRMS via Guvnor.  This allows a Business Analyst the ability to edit the Rule.  However, The Declarative Model created in BRMS is not usable from JBDS.  The Model can be imported into JBDS, but it is in a <name>.model.drl format that is unusable from the BRL in JBDS.  More thought should be given to resource interchangeability in BRMS and JBDS.  See attached screenshot of a simple model import.
Comment 1 Gary Lamperillo 2010-06-22 21:54:42 UTC 
Attachment: Added: BRMS_Model_import.png