Bug 724802 (BRMS-642) - The 'advanced enums' doesn't work on test scenario
Summary: The 'advanced enums' doesn't work on test scenario
Keywords:
Status: VERIFIED
Alias: BRMS-642
Product: JBoss Enterprise BRMS Platform 5
Classification: JBoss
Component: BRM (Guvnor)
Version: 5.1.0 GA
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: BRMS 5.2.0.GA
Assignee: manstis
QA Contact: Jiri Locker
URL: http://jira.jboss.org/jira/browse/BRM...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-07-19 13:06 UTC by Amana
Modified: 2023-05-15 19:53 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Classes with two fields that used advanced enumeration failed in test scenarios. An overloaded method was created to handle advanced enumerations and prevent test scenarios from failing.
Clone Of:
Environment:
BRMS 5.1
Last Closed: 2011-07-19 18:07:23 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
brms.png (231.73 KB, image/png)
2011-07-19 13:07 UTC, Amana
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker BRMS-642 0 Major Closed The 'advanced enums' doesn't work on test scenario 2013-12-18 09:07:20 UTC
Red Hat Issue Tracker GUVNOR-1554 0 Major Resolved The 'advanced enums' doesn't work on test scenario 2013-12-18 09:06:51 UTC

Internal Links: 745443

Description Amana 2011-07-19 13:06:07 UTC
Help Desk Ticket Reference: https://c.na7.visual.force.com/apex/Case_View?id=500A0000007pSZ8&srPos=0&srKp=500&sfdc.override=1
Steps to Reproduce: In BRMS tool:

1) Create a model with two fields, e.g. :

A class called Vehicle, which has 2 fields: "engineType" and "fuelType".


2) Create a enumeration, e.g. :

 'Vehicle.engineType' : ['Petrol', 'Diesel']
 'Vehicle.fuelType[engineType=Petrol]' : ['ULP', 'PULP' ]
 'Vehicle.fuelType[engineType=Diesel]' : ['BIO', 'NORMAL' ] 

3) Try to use it on a Business Rule -> it works

4) Try to use it into a test scenario -> it doesn't work

Note: The engineType field will display the choices into a test scenario but the fuelType won't display them (see the attached file). 
securitylevel_name: Public

The "advanced enums" works on a business rule, however inside a test scenario it doesn't work.

Comment 1 Amana 2011-07-19 13:07:25 UTC
Attachment: Added: brms.png


Comment 2 Rick Wagner 2011-07-19 18:02:27 UTC
Help Desk Ticket Reference: Added: https://c.na7.visual.force.com/apex/Case_View?id=500A0000007pSZ8&srPos=0&srKp=500&sfdc.override=1


Comment 3 Rick Wagner 2011-07-19 18:08:00 UTC
Accidently closed while investigating 'clone'.

Comment 4 Amana 2011-07-19 18:32:11 UTC
Link: Added: This issue Cloned to BRMS-643


Comment 5 Amana 2011-07-19 18:49:08 UTC
SourceForge Reference: Added: https://issues.jboss.org/browse/GUVNOR-1554


Comment 6 Amana 2011-07-19 18:50:18 UTC
SourceForge Reference: Removed: https://issues.jboss.org/browse/GUVNOR-1554 


Comment 7 Rick Wagner 2011-07-19 18:57:33 UTC
Link: Added: This issue depends GUVNOR-1554


Comment 8 Geoffrey De Smet 2011-08-23 13:26:45 UTC
Fixed, see GUVNOR-1554.

Comment 9 lcarlon 2011-08-25 04:50:11 UTC
    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:
https://bugzilla.redhat.com/show_bug.cgi?id=724802

Classes with two fields that used advanced enumeration failed in test scenarios. An overloaded method was created to handle advanced enumerations and prevent test scenarios from failing.

Comment 10 Jiri Locker 2011-08-31 18:40:55 UTC
Fix verified in ER3.

Comment 11 lcarlon 2011-09-14 04:27:55 UTC
    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,3 +1 @@
-https://bugzilla.redhat.com/show_bug.cgi?id=724802
-
 Classes with two fields that used advanced enumeration failed in test scenarios. An overloaded method was created to handle advanced enumerations and prevent test scenarios from failing.


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