Close popover
Jon Garfunkel (JonnyGar)
BNY Mellon
Vice President, BPM CoE
BNY Mellon
JonnyGar Member since 2009 91 posts
BNY Mellon
Posted: February 24, 2015
Last activity: March 10, 2015

Reading non-existent properties on declare page throws ReadOnlyException

To re-word a question from 2013...

In Pega, the common methods for getting properties from a ClipboardPage (getString() or the JSP functionality) will actually create the property if missing (and return the empty string).

This is problematic when working with Declare Pages. Suppose, for example, you expect a Declare Page to have a list of pxResults, but it has none. Defensive coding can sometimes avoid this (i.e., wrap a conditional around an iteration), but this ought to be more automated.

As Declare Pages which are read-only; the ReadOnlyException is thrown.

Was this problem ever fixed in a v6.x hotfix? Was it addressed in v7?

Data Integration
Moderation Team has archived post