Bug 724639 (BRMS-547)

Link: Added: This issue related GUVNOR-1179

Link: Added: This issue depends BRMS-381

gss_prioritized

    Technical note added. If any revisions are required, please edit the "Technical Notes" field
    accordingly. All revisions will be proofread by the Engineering Content Services team.
    
    New Contents:
When writing rules in the BRMS user interface it is not possible to define sub facts with statements that use multiple field constraints.

    Technical note updated. If any revisions are required, please edit the "Technical Notes" field
    accordingly. All revisions will be proofread by the Engineering Content Services team.
    
    Diffed Contents:
@@ -1 +1 @@
-When writing rules in the BRMS user interface it is not possible to define sub facts with statements that use multiple field constraints.+When writing rules in the BRMS user interface it was not possible to define sub facts with statements that use multiple field constraints.

It's still not really working, especially not the way the technical note would let the customer believe.

I'm using this model: 
declare SubFact
	field: Integer
end

declare Fact
	subfact: SubFact
end


With a rule:
1) Add Fact, click on the Fact, choose "Multiple field constraint" : "Any of (Or)", click on "any of the following:" in the editor, choose subfact. 
Then try clicking on that subfact to choose its field or bind a variable - it's not possible, not clickable.

2) Click the green plus sign to add a condition and choose "Any of the following are true", similarly to the above case, choose Fact, click it in the editor, but then choose "Add a restriction on a field" : subfact. Click on subfact in the editor.
You can either bind a variable to that fact or choose its field. BUT once you choose some field, subfact isn't clickable anymore. If you choose and insert a field before that, you can bind that to a variable too and once you bind it, it becomes unclickable too.

3) Save the rule, validate and verify - everything seems ok. Create a test scenario - you can't set the subfact.field inside a Fact.

Using BRMS 5.2.0 ER4

This really is a can of worms. I am making progress on resolving all items however the problems that have been reported are what is the effect of the problem rather than the cause.

Clicking an existing field constraint to add further sub-field constraints really is broken something terrible (and indeed probably not the preferred approach anymore - in fact I am in good mind to remove it). I have made a change to allow use of the "Expression Editor" in composite field constraints that solves all you report in 1) and 2). I hope to look at 3) this evening....  The change for 1) and 2) has been committed to .org (project) master branch on github - https://github.com/droolsjbpm/guvnor/commit/5d27a7b88b17d7a94ebe1b64d174f1268557aa73

hi, Michael, we would need it back port to 5.2.x branch.

Could you back port it for us and mark it as modified if it has been resolved.

OK, 1) and 2) have been completed and back-ported. 3) remains incomplete. I would suggest 3) is created as a separate issue for post BRMS 5.2 - there is no code in the Test Scenario code-base to support adding sub-field values and hence arguably 3) is an enhancement.

JIRA https://issues.jboss.org/browse/GUVNOR-1416 already exists for 3)

(In reply to comment #12)
> JIRA https://issues.jboss.org/browse/GUVNOR-1416 already exists for 3)

Let's wait for 5.3 with that one.

This product has been discontinued or is no longer tracked in Red Hat Bugzilla.