pyApplication and pyApplicationVersion properties are not captured in the interaction history
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
- In the navigation pane of Dev Studio, click Records.
- Expand the Decision category, and then click Strategy.
- Select the strategy rule that you want to edit.
- Click the Pages & Classes tab.
- Add a page to the strategy rule:
- In the Page name field, enter pxThread.
- In the Class field, press the Down Arrow key, and then select Code-Pega-Thread.
- Click Save.
Adding the pxThread page in a strategy 
- Open the Strategy tab.
- Right-click the strategy canvas, and then click .
- Place the Set Property shape before the Results shape by dragging the Set Property shape and connecting it to other shapes in the strategy.
- Double-click the Set Property shape.
- In the Set Property Properties window, click Target.
- Set the pyApplication property:
- Click Add Item.
- Add the following expression: Set .pyApplication equal to pxThread.pxCurrentApplicationName
- Set the pyApplicationVersion property:
- Click Add Item.
- Add the following expression: Set .pyApplicationVersion equal to pxThread.pxCurrentApplicationVersion
Setting the pyApplication and pyApplicationVersion properties in a strategy 
- Click Submit.
- 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