Bug 970786

Summary: Test scenario should support hierarchial object models and collections
Product: [Retired] JBoss BRMS Platform 6 Reporter: Alessandro Lazarotti <alazarot>
Component: Business CentralAssignee: Toni Rikkola <trikkola>
Status: CLOSED EOL QA Contact: Jiri Locker <jlocker>
Severity: low Docs Contact:
Priority: low    
Version: 6.0.0CC: etirelli, lpetrovi, paradhya
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-03-27 20:02:33 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:
Embargoed:

Description Alessandro Lazarotti 2013-06-04 21:33:00 UTC
Description of problem:
Test scenario doesn't support complex objects and collections

Version-Release number of selected component (if applicable):
BRMS-6.0

Steps to Reproduce:
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.


Actual results:
subfact.field must accessible from test scenario

Expected results:
test scenario supporting complex objects

Additional info:
This issue was partially solved by Bug 724639, but test scenario was not fixed.