Bug 1195241 - kcontext usage in Free Form DRL of RHS breaks the Guided Rule
Summary: kcontext usage in Free Form DRL of RHS breaks the Guided Rule
Keywords:
Status: CLOSED EOL
Alias: None
Product: JBoss BPMS Platform 6
Classification: Retired
Component: Business Central
Version: 6.0.3
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ER6
: 6.1.0
Assignee: manstis
QA Contact: Lukáš Petrovický
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-02-23 13:05 UTC by Anton Giertli
Modified: 2020-03-27 20:00 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-03-27 20:00:06 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 1158176 0 high CLOSED Guided Rule Editor: Displays blank screen when I tried to opening the saved rule 2021-02-22 00:41:40 UTC
Red Hat Bugzilla 1209397 0 medium CLOSED Unable to use 'drools' variable in Guided Rules 2021-02-22 00:41:40 UTC

Internal Links: 1158176 1209397

Description Anton Giertli 2015-02-23 13:05:17 UTC
Description of problem:

Specific content of Free form DRL in RHS section of the Guided Rule breaks the specific rule completely.
Version-Release number of selected component (if applicable):
bpm suite 6.0.3 with rp#2 APPLIED

How reproducible:
ALWAYS

Steps to Reproduce:
1. Create guide rule
2. In THEN section add following line:
kcontext.getKnowledgeRuntime().startProcess("liability-rules.ContractCalculationProcess");
3. Save the rule and hit F5
4. Open the rule again - the screen is empty, no error, not possible to edit it anymore

Actual results:
With specific content in RHS the rule can't be opened after refresh.

Expected results:
The rule can be opened after refresh.

Additional info:

Comment 2 manstis 2015-02-25 20:31:42 UTC
I think this has been fixed.. claiming and looking into...

Comment 3 manstis 2015-02-25 20:48:50 UTC
This has been fixed as part of the referenced BZ.


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