Hide Forgot
Help Desk Ticket Reference: https://c.na7.visual.force.com/apex/Case_View?id=500A00000045DJH&sfdc.override=1 Steps to Reproduce: Create a package like: package defaultPackage declare INPUT DATA: String end declare OUTPUT STATUS: String end rule "Case_362267_Rule" dialect "mvel" when INPUT( DATA matches "^$" ) then OUTPUT fact0 = new OUTPUT(); fact0.setSTATUS( "OK" ); insert(fact0 ); end Create a test scenario like the attachment and try to run. securitylevel_name: Public When a empty value is set in the text field of a given fact, the test scenario fails if you would like match a rule by a empty String in the fact. For Guvnor, a empty text field is a NULL value, not a empty String value.
Attachment: Added: Case_362267_Test.JPG
Link: Added: This issue related GUVNOR-1195
GSS prioritizes this 'low'. Work around exists, no immediate need for customer.
Fixed in master and back-ported to 5.3.x.
Hi Michael, for the release notes could you let me know how this issue was resolved? We need to be able to let customers know about any changes in the code that could affect their systems. Thanks Lee
Hi Lee, The solution was to ensure "empty" Test Scenario Fact fields were initialized to an empty String instead of a null that was causing the problem. There remains a BZ (AFAIK) that was unfixed for 5.3 about being able to check for "an empty string" and "null" as two different "values". With kind regards, Mike
Thanks Mike!
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: It was previously not possible to create a test scenario for a rule that matched an empty string. This has been resolved by ensuring the "empty" test scenario fact fields are initialized to an empty String instead of a null.