Skip to main content

         This documentation site is for previous versions. Visit our new documentation site for current releases.      

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.

Setting property values with the clipboard

Updated on April 5, 2022

Maintain the best quality of your application by testing it with the Clipboard tool. To test or debug your application, set values for the properties that you need to inspect, and then check whether these elements behave in an expected way.

For example, to test a child case type before you finish creating its parent case type, you can provide data that the child case type normally inherits from its parent. After you conduct your testing, you can debug your application by providing different values, as necessary.
  1. In App Studio, navigate to an element that you want to test.
    For example: To test a child case, in the navigation pane of App Studio, click Case types, click a case type that you want to open, and then click Run.
  2. In the footer of App Studio, click Toggle runtime toolbarClipboard.
    Result: The Pega Clipboard window opens. The Thread panel lists pages in memory associated with the selected thread, such as case types.
  3. In the Thread panel, click the page that stores the values that you want to edit.
  4. In the Clipboard page section, click Edit.
  5. In the Value column, provide a value for the property that you want to test or debug.
  6. Click Save.
  7. Populate the process that you want to test or debug with the new clipboard data.
    For example: Bring the case to a resolution.
  8. Verify that the field values match the test values.

Have a question? Get answers now.

Visit the Support 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. is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us