Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1234640 - Guided Rule Editor: String fields with double slashes changes the editor
Guided Rule Editor: String fields with double slashes changes the editor
Status: VERIFIED
Product: JBoss BRMS Platform 6
Classification: Retired
Component: Business Central (Show other bugs)
6.1.0
Unspecified Unspecified
unspecified Severity unspecified
: DR1
: 6.2.0
Assigned To: manstis
Lukáš Petrovický
:
Depends On:
Blocks: 1235013
  Show dependency treegraph
 
Reported: 2015-06-22 18:07 EDT by William Antônio
Modified: 2016-04-22 00:50 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
: 1235013 (view as bug list)
Environment:
Last Closed:
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)
The issue (18.67 KB, image/png)
2015-06-22 18:07 EDT, William Antônio
no flags Details

  None (edit)
Description William Antônio 2015-06-22 18:07:26 EDT
Created attachment 1042034 [details]
The issue

Description of problem:

When using String field in a rdrl and using texts with double slashes ("//") in the literal value, the editor changes, showing a field to manually edit it instead the visual editor.

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


How reproducible:


Steps to Reproduce:
1. Clean BRMS installation, use the new default project;
2. Create a data model with a String attribute;
3. Create a Guided Rule and in the LHS use the object attribute and the equals operation to compare it to a literal value that contains "//";
4. Save the guided rule and reopen it.

Actual results:

The visual part to change the attribute value will be shown in a text way, for example:

attr == "some value //"

Expected results:

It should use the combo box to select a condition (equal to, not equal to, etc) and the field to users enter the literal value.

Additional info:

See an attached screenshot that shows this problem.

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