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

InvalidReferenceException when opening work objects



An InvalidReferenceException is observed on the screen when attempting to open a WorkObject.

Error Messages The reference 1SomeRd.WSTE1-2 is not valid. Reason: unexpected character '1' at position 0, expected start of name or a dot
at com.pegarules.generated.PropertyHasValue_071001_zdFGLsk9mhp6nBKze5mgRQ.PropertyHasValue07_10_01(
at com.pegarules.generated.PropertyHasValue_071001_zdFGLsk9mhp6nBKze5mgRQ.invoke(

Steps to Reproduce

Open WorkObject.

Root Cause

An issue in the custom application code or rules:

User uses wrong version of the method PropertyHasValue(), which throws an exception when the property value has a dot in it, but is not a valid property reference.


Make sure to use the correct PropertyHasValue() method in the code. 
Following is the description:

1. PropertyHasValue(cp_Prop)
Label:                    Check if a property reference has some value
Returns:               boolean
Description:        Returns true if property has non-blank value.
Note that since this function takes a property reference, the property already exists on the page. If you use this function from a Rule-Obj-Activity, the activity java generation will CREATE the property on the page. In most cases you will want to use the version of this function that takes a string.
cp_Prop               (ClipboardProperty):
2. PropertyHasValue(tools, strReference)
Label:                    Check if a string property reference has some value
Returns:               boolean

Returns true if property has non-blank value. Note that if you need to test for a property existing on the page but not necessarily having a value, use PropertyExists.


Params: tools - context strReference - property reference like ".aString". Ensure  using the other version of this function that takes a clipboard property param because a java generated rule will then CREATE the property on the page when it calls this function.
In the second method, if a string has a dot (‘.’) in it, Pega considers it as a property reference and will throw an exception.

Try to use the first method in most scenarios, if not sure about the string value.


Published September 21, 2016 - 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