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

pxCheckStartsWithSpecialChar does not work correctly.



pxCheckStartsWithSpecialChar does not work correctly.

Error Messages

Not Applicable

Steps to Reproduce

In any report, use the pxCheckStartsWithSpecialChar function with input value as below:

When the .pyStatusWork input value starts with Resolved, it returns Resolved or Pending status.

The case status is returned as Pending even if the case status starts with Resolved.

Root Cause

The pxCheckStartsWithSpecialChar function is implemented only for Pega internal purpose.


Here's the explanation for the reported behavior:

The function is implemented for one an internal requirement that is specific to the '\' character in the URL.

As a local-change, write a custom function as per user requirement.

Published December 2, 2021

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