IBM Support

JR43934: "RULE PARSER ERROR AT LINE 31:EXPECTED TEXT AFTER // CONDITION_CLAUSE" THROWN IF INPUT "" TO DECISION TABLE

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as fixed if next.

Error description

  • If you input "" into a decision table as value of a variable,
    there will be no warning message prompted, but after saving it
    and reopen it, you will get errro as below, and can not open the
    decision table at all.
    java.lang.IllegalArgumentException: Rule parser error at line
    31:expected text after // CONDITION_CLAUSE
     at
    com.lombardisoftware.client.ae.forms.rules.model.Rule$Javascript
    Persiste
    r.parseError(Rule.java:333)
     at
    com.lombardisoftware.client.ae.forms.rules.model.Rule$Javascript
    Persiste
    r.getString(Rule.java:294)
     at
    com.lombardisoftware.client.ae.forms.rules.model.Rule$Javascript
    Persiste
    r.fromScript(Rule.java:262)
     at
    com.lombardisoftware.client.ae.forms.rules.model.Rule.parseFromJ
    avascrip
    t(Rule.java:111)
     at
    com.lombardisoftware.client.ae.forms.rules.model.RuleScriptRuleD
    ata.<ini
    t>(RuleScriptRuleData.java:41)
     at
    com.lombardisoftware.client.ae.forms.rules.RulesModel.createRule
    (RulesMo
    del.java:262)
    ...
    

Local fix

  • N/A
    

Problem summary

  • Fix planned for next release of BPM V8, targetting 4Q2012.
    
    USER AFFECTED: Users creating a Decision Table with an "" empty
    string as a condition value.
    
    PROBLEM SUMMARY: Once the user inputs Empty string ("") as a
    condition value in a Decision Table, after saving and closing
    the decision table. the user is not longer able to reopen it
    successfully.
    
    PROBLEM DETAILED DESCRIPTION: The editor does not allow either
    blank input or input comprised of just spaces.. All this gets
    reverted to the default input of "-". But looks like a user can
    get around this problem by entering empty quotations "" which
    get saved and when quotes are stripped, the value becomes blank
    input (empty string). This is something that is not allowed as
    per the existing code and catches this explicitly.
    
    It seems this issue has been there from the start and probably
    that empty quoted strings were never tested as an input during
    the test phase.
    
    
    PROBLEM CONCLUSION: The changes will allow the code, when
    opening the editor, to handle the empty string and treat it as a
    the default input, which is essentially what was happening
    before the user closed the editor.
    

Problem conclusion

Temporary fix

  • User should not enter "". This is the same as entering nothing
    in the condition value field which when committed gets converted
    to the default "-" value.
    

Comments

APAR Information

  • APAR number

    JR43934

  • Reported component name

    BPM ADVANCED

  • Reported component ID

    5725C9400

  • Reported release

    800

  • Status

    CLOSED FIN

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2012-08-30

  • Closed date

    2012-09-25

  • Last modified date

    2012-09-25

  • APAR is sysrouted FROM one or more of the following:

  • APAR is sysrouted TO one or more of the following:

Fix information

Applicable component levels

  • R800 PSY

       UP

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSFTN5","label":"IBM Business Process Manager Advanced"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"8.0","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
12 October 2021