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

Withdrawn Function creating issue



If you copy an out of the box (OOTB) Rule-Utility-Function in your custom library without changing its signature and then withdraw it, then Pega 7.1 acts like the function still exists and gives an error.

Error Messages

"** Invalid expression or reference: Multiple suitable instances found [seeking] @(null:null).callWhen(PublicAPI,String,ClipboardPage) [possible candidate functions are] @(Test_Ruleset:Test_Library).callWhen(PublicAPI,String,ClipboardPage) @(Pega-RULES:Utilities).callWhen(PublicAPI,String,ClipboardPage) SUGGESTION: Use full syntax for calling a function, Example- @(RuleSet:libraryname).functionname(arg1, arg2... argn) Rule-Utility-Function "

Steps to Reproduce

  1. Create an Activity and use any OOTB function 
  2. save that OOTB function to your custom library without changing the signature 
  3. save as your activity in higher ruleset version and use your custom function with fully qualified path 
  4. save as that function in higher ruleset version and make it withdrawn 
  5. use that function without fully qualified path so that Pega 7.1 should call the OOTB one. 

Root Cause

The root cause of this problem is a defect in Pegasystems’ code/rules.


This issue is resolved in Pega 7.1.8.

Published June 12, 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