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.

Solution

Modify the strategy rule that is part of the data flow to copy properties from the clipboard to the interaction history.

1. In the Records Explorer, click Decision > Strategy.
2. Select the strategy rule that you want to edit.
3. Open the Pages & Classes tab.
4. 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 select Code-Pega-Thread.
   3. Click Save.

      

      Adding the pxThread page in a strategy

5. Open the Strategy tab.
6. Right-click the strategy canvas, and then click Enrichment > Set Property.
7. Place the Set Property shape before the Results shape by dragging the Set Property shape and connecting it to other shapes in the strategy.
8. Double-click the Set Property shape to open the Set Property Properties panel.
9. Open the Target tab.
10. Set the pyApplication property:
    1. Click Add Item.
    2. Add the following expression: Set .pyApplication equal to pxThread.pxCurrentApplicationName
11. Set the pyApplicationVersion property:
    1. Click Add Item.
    2. Add the following expression: Set .pyApplicationVersion equal to pxThread.pxCurrentApplicationVersion
12. Click Submit.
13. Click Save.

Setting the pyApplication and pyApplicationVersion properties in a strategy