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

Launch Harness action - Key field not built as documented



The Developer Help for the "Key" field when using a 'Launch Harness' action in an action set states that it should be set to the 'Key' (pxInsName) of the instance to be opened, whereby the "Class Name" property would also be used to uniquely identify the instance to be opened. However, when configured, the UIActionDisplayHarness activity fails because it omits the "Class Name" component from the DB lookup.

Error Messages

A NullPointerException is returned as the instance could not be located in the database, given the omission of the classname portion of the database's unique key.
Relevant stack trace from logs:

2014-10-07 07:25:00,876 [tp-bio-8080-exec-131] [TABTHREAD2] [ ] [uraUnitTest:01.01.01] ( internal.access.DatabaseImpl) ERROR| - Cannot open the requested instance 'ORG10': class or class group "ORG10" does not exist.
2014-10-07 07:25:00,884 [tp-bio-8080-exec-131] [TABTHREAD2] [ ] [uraUnitTest:01.01.01] (splayHarness._baseclass.Action) ERROR| senior1 - Error opening page Class ORG10 does not exist
From: (H2D00CD0F1F734A34E7D180F263B87E52:
at com.pegarules.generated.activity.ra_action_uiactiondisplayharness_8d3bda3fbad18b72e991c8cfb228b822.step5_circum0(
at com.pegarules.generated.activity.ra_action_uiactiondisplayharness_8d3bda3fbad18b72e991c8cfb228b822.perform(

Steps to Reproduce

1. Get the pxInsName of an instance to open in a harness on the clipboard (for example, through a Data Page)
2. Configure an action set on a property or control that uses the Launch Harness action.
3. Use "New Document", configure the Class Name according to the class of the instance in #1, and configure the Key as per the pxInsName (as described specifically in the Developer Help).
4. At runtime, perform the action that launches the harness.

Root Cause

The root cause of this problem is an error in product documentation. Original reported documentation bug is resolved in Pega 7.1.7. 


User is expected to use just the pzInsKey to correct the problem. The relevant documentation is scheduled to be fixed in a future release of Pega 7.
Suggest Edit

Published January 31, 2016 - Updated October 8, 2020

Did you find this content helpful? Yes No

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