Question
Accenture
DE
Last activity: 19 Feb 2021 13:25 EST
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
Accepted Solution
Updated: 19 Feb 2021 13:25 EST
Accenture
DE
Hi @shanr2 I was expecting the property to be called pxInteractionID, but it was called InteractionID. I forgot mapping this on my Int-PegaCDH-Container Page before passing it to the activity. Now everything works fine. Thank you very much!
Pegasystems Inc.
IN
This is not how it should behave. When you capture the response from the Mashup, are you passing in the same interaction id for actions in the CaptureResponseAndInitiateOffer which you recieved from the Container service execution?
Accepted Solution
Updated: 19 Feb 2021 13:25 EST
Accenture
DE
Hi @shanr2 I was expecting the property to be called pxInteractionID, but it was called InteractionID. I forgot mapping this on my Int-PegaCDH-Container Page before passing it to the activity. Now everything works fine. Thank you very much!