Skip to main content

This content has been archived and is no longer being updated. Links may not function; however, this content may be relevant to outdated versions of the product.

Support Article

Issue with <CURRENT> in Expression after upgrade to 718



A decision table using the regular expression function contains the <current> keyword saved and worked in Pega 7.1.7 is no longer saving without error in Pega 7.1.8.

Error Messages

Test compilation failed: 
1. ERROR in / (at line 306)
boolean pz_1 = pega.<java.lang.Boolean>resolveMethodCall("pxContainsViaRegex--(String,String,boolean)", "pxContainsViaRegex", "Pega-RulesEngine", "String", new Object[]{myStepPage.getString(pega, ".CorrBody"), currentProperty.getStringValue(), true});
currentProperty cannot be resolved
1 problem (1 error)
Compile failed.

Steps to Reproduce

  1. Login to the application.
  2. Open a decision table.
  3. Open the top cell associated to the Conditions column.
  4. Open the expression builder.
  5. Try to validate the expression containing the key word <current>, passes.
  6. Try to validate the expression containing the key word <current-value>, fails.
  7. Try saving with the condition containing <current>, observe error as mentioned above.
  8. Try saving with the condition containing <current-value>, saves

Root Cause

A defect in Pegasystems’ code or rules. The correct keyword to use in a decision table is <current-value>, but the expression builder does not view this keyword as acceptable.


This issue is scheduled to be resolved in update release Pega 7.1.10


Published August 31, 2015 - Updated October 8, 2020

Was this useful?

0% found this useful

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best.

Pega Community has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice
Contact us