Link: Added: This issue depends GUVNOR-365

The guvnor-365 is completed and will be in Drools 5.3.

This was fixed for GUVNOR-365

One more thing to be fixed -- displaying the sentence in the Condition (LHS) dialog in Guided editor. Consider this DSL entry:

> [when][]When a person exists with social security number {chooseSSN:\d{3}-\d{2}-\d{4}} = Person(ssn == "{chooseSSN}")

Label for this sentence looks as following:

> When a person exists with social security number chooseSSN-\d2-\d4

Obviously the first right brace '}' in the regex is incorrectly recongnized as a closing brace of the variable definition and the rest of the regex is displayed.

OK, fixed and back-ported to 5.3.x branch. 

I did take the liberty of making the text appear as below, so DSL parameters are more clear (especially in DSL sentences with multiple parameters). Let me know if you want the braces removed - it seemed a good idea to me:-

> [when][]When a person exists with social security number {chooseSSN:\d{3}-\d{2}-\d{4}} who is {gender} = Person(ssn == "{chooseSSN}", gender == "{gender})

Label for this sentence looks as following:

> When a person exists with social security number {chooseSSN} who is {gender}

Verified in BRMS 5.3.0.DEV6.

    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:
When using the guided editor to enter a regular expression that included curly braces in a DSL sentence, the expression was incorrectly parsed with the first closing curly brace in the regular expression was incorrectly recognized as the closing brace for the variable definition.

    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 +1 @@
-When using the guided editor to enter a regular expression that included curly braces in a DSL sentence, the expression was incorrectly parsed with the first closing curly brace in the regular expression was incorrectly recognized as the closing brace for the variable definition.+When using the guided editor to enter a regular expression that included curly braces in a DSL sentence, the expression was incorrectly parsed with the first closing curly brace in the regular expression was incorrectly recognized as the closing brace for the variable definition. The issue has been resolved and the curly braces used in regular expressions are recognized correctly.

    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 +1 @@
-When using the guided editor to enter a regular expression that included curly braces in a DSL sentence, the expression was incorrectly parsed with the first closing curly brace in the regular expression was incorrectly recognized as the closing brace for the variable definition. The issue has been resolved and the curly braces used in regular expressions are recognized correctly.+When using the guided editor to enter a regular expression that included curly braces in a DSL sentence, the expression was incorrectly parsed with the first closing curly brace in the regular expression incorrectly recognized as the closing brace for the variable definition. The issue has been resolved and the curly braces used in regular expressions are recognized correctly.