Skip to main content

Setting property values with the Clipboard tool

Suggest edit Updated on November 15, 2021

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 your application logic uses, and then check whether the application logic behaves as expected.

For example, to test the logic of a child case type, before you finish creating its parent case type, you can provide a sample of the data that the child case type normally inherits from its parent.

For relevant training materials, see the Clipboard data module on Pega Academy.

  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 Save and run.
  2. In the footer of App Studio, click Toggle runtime toolbarClipboard.Result: The Clipboard Viewer window opens. The navigation pane lists pages in the memory that are associated with the thread that you select in the Thread list.
  3. In the navigation pane, 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.For example: Set the value of a property to false, as shown in the following figure:
    Editing property values in the Clipboard tool
    A page in the Clipboard tool with three read-only fields and four editable fields
                marked.
  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.
Did you find this content helpful? YesNo

Have a question? Get answers now.

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

We'd prefer it if you saw us at our best.

Pega.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us