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.

pyApplication and pyApplicationVersion properties are not captured in the interaction history

Suggest edit
Updated on April 5, 2022

When running a data flow run through a service SOAP rule, the pyApplication and pyApplicationVersion properties are not captured in the interaction history. This issue can lead to unexpected data flow results or the interaction history records not being saved.

Cause

This issue is caused by an incorrectly configured strategy rule that is part of the data flow. To resolve the issue, you need to modify the strategy rule that is part of the data flow to copy properties from the clipboard to the interaction history.

Solution

  1. In the navigation pane of Dev Studio, click Records.
  2. Expand the Decision category, and then click Strategy.
  3. Select the strategy rule that you want to edit.
  4. Click the Pages & Classes tab.
  5. Add a page to the strategy rule:
    1. In the Page name field, enter pxThread.
    2. In the Class field, press the Down Arrow key, and then select Code-Pega-Thread.
    3. Click Save.
    Adding the pxThread page in a strategy
    The page name field is set to px thread, the class field is
                                        set to code pega thread.
  6. Open the Strategy tab.
  7. Right-click the strategy canvas, and then click EnrichmentSet Property.
  8. Place the Set Property shape before the Results shape by dragging the Set Property shape and connecting it to other shapes in the strategy.
  9. Double-click the Set Property shape.
  10. In the Set Property Properties window, click Target.
  11. Set the pyApplication property:
    1. Click Add Item.
    2. Add the following expression: Set .pyApplication equal to pxThread.pxCurrentApplicationName
  12. Set the pyApplicationVersion property:
    1. Click Add Item.
    2. Add the following expression: Set .pyApplicationVersion equal to pxThread.pxCurrentApplicationVersion
    Setting the pyApplication and pyApplicationVersion properties in a strategy
    The Set Property shape on the strategy canvas. The
                                        Properties window with the two properties set as
                                        targets.
  13. Click Submit.
  14. Click Save.
  • Previous topic Interaction History component processes data longer than expected
  • Next topic Values of the pxOutcomeTime property are not unique in the Oracle database
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