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

NullPointerException in SafeURL.put(key,value) {inStandardsMode}

SA-12242

Summary



When a user checks a checkbox, the following error is thrown:

NullPointerException in SafeURL.put(key,value) {inStandardsMode}, {undefined}. 



Error Messages



NullPointerException in SafeURL.put(key,value) {inStandardsMode}, {undefined}

Steps to Reproduce



1. Create a flow
2. Create a Section
3. Add a repeat gird
4. Set the repeat gird source to property
5. Set the list/group to something.pxResults
6. Configure a field with a checkbox with ONCHANGE/Post Value.
7. Observe runtime behavior when you click the checkbox.


Root Cause



When the ajax request in the postValue() function is being formed the value of the pega.u.d.inStandardsMode is undefined instead of true.
 
In a working scenario, this variable is supposed to be initialized to true when a harness is loaded.
 
When the harness in question is loading, it runs into the below exception(logs) that stops it from executing any further hence skips the initialization of the variable.
2015-07-09 14:55:46,538 [   WebContainer : 59] [TABTHREAD2] [                    ] [      RRPFW:01.01.01] (ternal.mgmt.StreamBuilderTools) ERROR xyz.net| xx60057 - Problem appending stream null
com.pega.pegarules.pub.PRRuntimeException: Section 'Harness-ConfigureExpressions' execution error on page 'pyWorkPage' of  class 'PQR-FW-RRPFW-Work-Rating-DirectRating'. : An expression can only have at most one target
                at com.pegarules.generated.html_fragment.ra_stream_harness_configureexpressions_aa2e4d5df0dc5c428c1b16c1b8067e3c.execute(ra_stream_harness_configureexpressions_aa2e4d5df0dc5c428c1b16c1b8067e3c.java:182)

Corrective action needs to be taken on one or more declare expressions that are invoked when the harness is loaded.


Resolution



The explanation for this behavior is as follows: 

Identify the problematic declare expression(s) and correct it. In this case, changed it to be "Whenever used".
Suggest Edit

Published July 16, 2015 - Updated October 8, 2020

Did you find this content helpful? Yes No

100% found this useful

Have a question? Get answers now.

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

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