Question

2
Replies
62
Views
Christian Tepel (Christian-Tepel)
Accenture

Accenture
DE
Christian-Tepel Member since 2020 1 post
Accenture
Posted: February 19, 2021
Last activity: February 19, 2021
Posted: 19 Feb 2021 4:49 EST
Last activity: 19 Feb 2021 13:25 EST
Solved

Interaction History: 2 pxInteractionIDs for one interaction

Hi, 

we have implemented a Pega mashup in a telephony system. This of course uses a real-time container which captures impressions on retrieval. We display different actions on the mashup and after selecting an action and reacting to it via the click of a button, we are using the OOTB activity CaptureResponseAndInitiateOffer and parameterize it with a page of the class Int-PegaCDH-Container.

What happens, is that the real-time container writes into the Interaction History (IH) first to capture the impression. After this the above-named activity captures the response on click and generates a new pxInteractionID. We do not want this to happen. Instead we want the same pxInteractionID for both IH entries since both happen in the same interaction.

 

Did anyone of you face a similar problem yet and knows how to solve this?

Thank you in advance!

Regards,

Christian

***Edited by Moderator: Pooja Gadige to add platform capability tags***
Pega Customer Decision Hub 8.1 Decision Management User Experience Insurance System Architect