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.

Troubleshooting: OpenURLinWindow not working after upgrade to PRPC 6.3 SP1

Updated on March 23, 2020

After you upgrade your environment from PRPC 6.2 SP2 to PRPC 6.3 SP1, you notice that the auto-generated control pxLink (Link) does not work as expected. You see the problem wherever the pxLink control is used in Perform harnesses of your applications when the Control Mode is set to Action. When you click the URL in an open window of your application's harnesses, nothing happens: No URL is passed. The pxLink control works correctly in Review harnesses.

This problem was reported for the pxLink control in Perform harnesses. However, the problem can occur with any control rule that requires parameters based on run-time property values for its successful operation. The case that was reported exposed a regression defect in the GenerateHarnessHTML rule utility function.

HFix-7559 corrects this regression defect in PRPC 6.3 SP1.

Pega 7.1.4 corrects the GenerateHarnessHTML rule utility function.


When designing the CPMPerform harness, drag a section into the harness that contains the pxLink control. Specify the behavior of the pxLink control as follows and as shown in the example screen:

  1. In the Event list, click Click.
  2. In theAction list, click OpenURLinWindow.
  3. Select the Alternative Domain check box.
  4. In the Alternate Domain URL field, enter .DocURL.
  5. In the Window Name field, enter .DocType.

Both .DocURL and .DocType are properties whose values are determined from the clipboard at run time.

pxLink Behavior, Click event, Open URL in Window, Alternate Domain URL, and Window Name

Link control behavior for Click event OpenURLinWindow with .DocURL and .DocType parameters


Every harness that contains the substitutions required at run time to pass parameters to controls that require them generates an AJAX Change Tracker (AJAXCT) division <div>, as shown in this example:

. . . if ( !pega. ui. onlyOnce ) pega .ui . onlyOnce - new pega. ui. OnlyOnceSingleton () ; if ( oNewOOm

<div style= ' display:none;' id= 'AJAXCT ' data-json • .. ID "' :1,"p"' :1, " Initial"' :..pxThread • "true.. ,"DocumentLinks (1) '': "1..f.J§i i§••:•origination Document "' ,"DocURL '' : http: <your_URL> . . .

In the example scenario, the pxLink control calls OpenURLinWindow and is expected to pass the values of the properties .DocType and .DocURL. However, in the Perform harness, the AJAXCT <div> is missing in the HarnessHTML because the harness contains embedded Frame Source. This is a defect in the GenerateHarnessHTML rule utility function. The AJAXCT <div> should contain the run-time values required for the control to operate.

Here is the HTML tab of the Pega-provided CPMPerform harness. Notice that the harness HTML contains embedded Frame Source:

Harness HTML Frame Source with HTML Source for AJAXTracker

CPMPerform harness with embedded Frame Source omits AJAXCT div needed for the pxLink control

​​This is the defect in the GenerateHarnessHTML rule utility function. Because this harness contains embedded Frame Source, the AJAXCT <div> is omitted, resulting in failure of the pxLink control at run time.

The regression defect is corrected in Pega 7.1.4 and in CPM 7.1.2.

HFix-7559 is available for PRPC 6.3 SP1.

Suggested approaches

Choose to upgrade to Pega 7 or patch your PRPC 6.3 SP1 environment.

Pega 7 upgrade (best practice)

Adopt the best practice and upgrade to Pega 7.1.4 or the latest release. Upgrading to the latest release of Pega 7 gives you the best capabilities available for your enterprise applications.

PRPC 6.3 SP1, HFix-7559

If you are running PRPC 6.3 SP1 and choose not to upgrade, take these actions:

  1. Go to My Support Portal > Support Requests > Create Support Request.
  2. In your Support Request, ask for HFix-7559.
  3. Install HFix-7559 from the DL file you receive from GCS.
  4. After installing HFix-7559, complete the following steps:
    1. Resave every harness rule that has embedded Frame Source to ensure that the corrected GenerateHarnessHTML rule utility function runs and generates correct HTML.

    2. Recompile the Rule-Utility-Function library for the hotfix to take effect.

    3. Use the System Management Application (SMA) to extract the library.

    4. Resave the rule.

    5. Stop the application server.

    6. Delete the PegaRULES_Extract_Marker.txt file in the PRPC temporary directory.

    7. Restart the application server.

  5. Verify HFix-7559 by using the example that follows:

    1. Review this example of the Pega-provided CPMPerform harness.

      This example contains some links to work items.

      Clicking the link opens the work item in another tab.​

      The ID column in the CPMPerform harness
      CPMPerform harness after HFix-7559 is installed with links to work items
    2. View the output of this harness by clicking View Source.
      This harness was built correctly after you installed the hotfix.

    3. Notice that the AJAXCT <div> contains the required parameters to open each of the work items shown in Step 5a:

      AJAXCT div linking to work items
      CPMPerform harness with correct AJAXCT div linking to work items

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