Bug 754813 - DSL View for use in business rules assets does not scroll to the right
Summary: DSL View for use in business rules assets does not scroll to the right
Keywords:
Status: ASSIGNED
Alias: None
Product: JBoss Enterprise BRMS Platform 5
Classification: JBoss
Component: BRM (Guvnor)
Version: BRMS 5.2.0.GA
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: ---
Assignee: manstis
QA Contact: Lukáš Petrovický
URL: https://issues.jboss.org/browse/GUVNO...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-11-17 19:40 UTC by Amana
Modified: 2020-04-27 01:12 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
BRMS 5.2.0.GA
Last Closed:
Type: Bug


Attachments (Terms of Use)
screenshot (86.10 KB, image/png)
2011-11-17 19:41 UTC, Amana
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker GUVNOR-1754 0 Minor Closed DSL View for use in business rules assets does not scroll to the right 2019-03-12 00:21:48 UTC

Description Amana 2011-11-17 19:40:42 UTC
I have created a set of DSL. The words end up being longer than the standard box that comes up when I try to use the DSL in a business rule assets.

See the attached screenshot.

Steps to reproduce (example in mortgages project):
1) In DSL Configurations, edit the file (eg. ApplicantDsl)
2) Increase the text that will be displayed for business rule after the [when] tag ...
e.g :

[when]When the credit rating is shfgjsdgfjhsdgfjsgdfhgsjkdfhsdgfjksdgfsdgfkjsdghfhsdgfhgsfjksdgfshdjsgdfjkgsdjkfgasjkfhsdgfasgkausfsdfyhsukhfusdhfuteste {rating:ENUM:Applicant.creditRating} = applicant:Applicant(creditRating=="{rating}")
[then]Approve the loan = applicant.setApproved(true)

3) Save the changes
4) Go to Business Rule Assets and click on a rule
5) Click on green plus on the right

Comment 1 Amana 2011-11-17 19:41:34 UTC
Created attachment 534298 [details]
screenshot

Comment 2 manstis 2011-12-14 09:20:58 UTC
This is an enhancement not a bug and hence need not be included in 5.3 unless an Engineering Response Documents (ERD) has been produced and it has been agreed to be in scope.


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