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

Incorrect JSON object with speciality component use



I have created a specialty component that accepts input parameters. Two of the input parameters are of type page list. The JSON object that I get to use in JavaScript is incorrect.There is no identifier for the page lists provided.

So I have to get my data with the following key: "".

Also the second page list is not available for use.

There is no service involved and we do not use any transform rules to get our clipboard data into a valid JSON object.
We use the specialty components, which themselves transform the clipboard data into a JSON object.

After some additional digging I found a solution for our problem, but I don’t believe it is the correct way because I don’t want to reference pyWorkPage, since I am already on the work layer. Also, using Primary as the page doesn’t result in the correct behavior. And if I ever have another named Top Level Page of the work class, I cannot use a specialty component.

I think it is a bug, but can you verify, or is this intended design?

- doc with screens and code used

Error Messages

No specific error, just an wrongly defined JSON object

Steps to Reproduce

Create a specialty component, add a parameter of type page list and add one or two embedded scalar properties. Include the section in another section and provide the parameters. Add console.log(JSON.stringify(data)); after the data is fetched from the clipboard and check firebug to see the output.

Root Cause

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

When we use a section which is a specialty component, we found page list parameter name are not passed as Json object.
So if you use several page list parameter name in a section which is a specialty component, you don't know how to reference each of them.


This will be fixed in PRPC 7.1 ML7.

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