Bug 1072043 - Cannot access fact fields in test scenario until it is saved and reopened
Summary: Cannot access fact fields in test scenario until it is saved and reopened
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: JBoss BRMS Platform 6
Classification: Retired
Component: Business Central
Version: 6.0.1
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: CR1
: 6.0.1
Assignee: Toni Rikkola
QA Contact: Jiri Locker
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-03-03 18:27 UTC by Jiri Locker
Modified: 2014-08-06 19:57 UTC (History)
5 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2014-08-06 19:57:35 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 1073379 0 high CLOSED Cannot access subfields in guided editor 2021-02-22 00:41:40 UTC

Internal Links: 1073379

Description Jiri Locker 2014-03-03 18:27:06 UTC
Description of problem:
After adding a given fact to test scenario the fact appears to have no fields (only 'this' is available). When I save the test at this point and reopen it the fields are available.

Version-Release number of selected component (if applicable):
6.0.1.ER2

How reproducible:
-

Steps to Reproduce:
1. Create new test scenario in any project with data model (e.g. mortgages)
2. Add a fact (Applicant), click 'Add a field'

Actual results:
Only 'this' is available.

Expected results:
All fact fields should be available.

Additional info:

Comment 2 Marek Winkler 2014-03-05 09:38:34 UTC
This is a regression and a test blocker, so we would expect this to be fixed in CR1.

Comment 3 Marek Winkler 2014-03-05 10:01:37 UTC
We have revisited this issue and it seems there is already a fix; as this is a test blocker, could you please consider including this fix into 6.0.1 (probably CR1 build)?

Comment 5 Michael 2014-03-17 17:08:15 UTC
Ticket cherry-picked into 6.0.1.CR1. 
Commits: 94237a4b1386d1621261372639289c93aca761eb
         d7a3a3c188e4fb1f4d78a9054d5359f989fd6a8e
         03d0faffe40339137c93236bef554e84d913c575


Note You need to log in before you can comment on or make changes to this bug.