Bug 1129686 - Guided Rule Template: DSL sentences corrupt Source tab content
Summary: Guided Rule Template: DSL sentences corrupt Source tab content
Keywords:
Status: CLOSED EOL
Alias: None
Product: JBoss BRMS Platform 6
Classification: Retired
Component: Business Central
Version: 6.1.0
Hardware: Unspecified
OS: Unspecified
medium
low
Target Milestone: DR3
: 6.1.0
Assignee: manstis
QA Contact: Lukáš Petrovický
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-08-13 13:14 UTC by Zuzana Krejčová
Modified: 2020-03-27 19:35 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-03-27 19:35:18 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)
source screenshot (27.20 KB, image/png)
2014-08-13 13:14 UTC, Zuzana Krejčová 		no flags Details
View All


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 993052 0 low CLOSED Guided Rule with DSL should translate DSL into DRL when viewing source 2021-02-22 00:41:40 UTC
Red Hat Bugzilla 1198220 0 high CLOSED GDT: dsl sentences in BRL fragments not expanded/converted in the Source tab 2021-02-22 00:41:40 UTC

Internal Links: 993052 1198220

Description Zuzana Krejčová 2014-08-13 13:14:35 UTC 
Created attachment 926416 [details]
source screenshot

Description of problem:
See bug 993052 as well.

When using DSL sentences in the guided rule template, the Source tab shows unprocessed DSL sentence instead of the relevant source.

For DSL with:
[when]EnumFact with=var2 : EnumFact()
[when]- fieldString1 {$value:ENUM:EnumFact.fieldString1}=fieldString1 == "{$value}"
When these two are used in a guided rule template like this:
1.     EnumFact with
2.     - fieldString1 <someValue>
Source tab shows this:
7.	|	        EnumFact with
8.	|	        - fieldString1 someValue
instead of var2 : EnumFact(fieldString1 == "someValue").
Other condition and action elements are prefixed with ">".

Bug seems to be purely "visual" - validation succeeds, project can be built, rule is fired in test scenario as expected.
Note You need to log in before you can comment on or make changes to this bug.