Question
Mphasis
IN
Last activity: 23 Apr 2020 5:23 EDT
Pega Marketing: SR class inheritance
Hello,
We recently upgraded to PM 8.3 from 7.22
In the new version I see a new SR class been introduced "Data-CDHCaptureResponse-SR" by Marketing.
In 7.22 version, our SR class was inherited from Data-pxStategyResult class.
Do we need to change this to extend it from Data-CDHCaptureResponse-SR class?
In one of our requirement, we call CaptureResponseAndInitiateOffer OOTB activity.
Post upgrade when we call this activity it is getting failed to update IH
Thanks
Sathish
***Edited by Moderator Marissa to update Platform Capability tags****
Pegasystems Inc.
IN
There is no change required in the inheritance of your SR class. The Data-CDHCaptureResponse-SR is an internal class required for enabling the multilevel response capture support.
What error are you seeing? Have you inspected the logs or the tracer to find the rootcause?
Mphasis
IN
Hi Raghu,
Actual issue is, IH getting updated but only OOTB properties. The SR properties which are defined in our SR class are not getting updated in IH.
When I debug the OOTB data flow D_CaptureInteraction, the "Convert" shape excludes the properties of our SR class, because there is a new SR class (Data-CDHCaptureResponse-SR) being used in this version, and this has no relation with our class.
I temporarily saved as this rule in to our ruleset and used our SR class in the "convert" shape, then it works as expected and all our props getting updated properly IH.
Regards Sathish
Pegasystems Inc.
IN
That is not a correct change to do. What version of Platform and Marketing are you using?
Also, can you please explain your usecase? How are making the recommendations and how is the response being captured and using which channel?
While making the recommendation (make decision) we store the entire proposition(s) record emitted by the strategy in the Cassandra datastore keyed by the pySubjectID ( customerid ) and pxInteractionID. During capture response, we lookup the records fro the Cassandra and use that payload to write to IH. This would ensure the actual SR records is being written to IH.
Please share your usecase details which will help us to understand better and make appropriate recommendation.
Mphasis
IN
We use a DB template based batch campaign to generate offers and send it to various client channels by extracting them in to files.
Later we get a response in the form of files from channels. We process them thru pega file listeners, and map the fields as ootb container api expected (RankedResults paglist) structure and finally call CaptureResposneAndIntiateOffer activity to store them in IH.
Regards
Sathish
Mphasis
IN
We use a DB template based batch campaign to generate offers and send it to various client channels by extracting them in to files.
Later we get a response in the form of files from channels. We process them thru pega file listeners, and map the fields as ootb container api expected (RankedResults paglist) structure and finally call CaptureResposneAndIntiateOffer activity to store them in IH.
We are on Platform 8.3.1 and PM 8.3
Regards
Sathish
Pegasystems Inc.
IN
Can you confirm if you are mapping the Interaction ID along with other properties in the DB template and exporting them in the files and also are the channel apps are sending both the customer ID and Interaction ID back to the system?
The activity that you are calling requires the CustomerID to be set on the .Request page and the InteractionID set on each RankedResults page.As I mentioned in my previous response, we store the original results in Cassandra during make decision. If you are sure that the required properties are properly set then it should be able to pull the data back from Cassandra and write it to IH. You can confirm by opening pxDecisionResults dataset rule and perform an Actions > Run and performa Browse by Keys and provide the values for subjectID and InteractionId and confirm if the record exists.
Mphasis
IN
Yes, Im aware of this delayed leaning concept.
Also we are storing the interaction and subject id in db template and we receive them back while processing the response.
But the problem is we get some additional fields in the response file which are not present in the initial offer, for ex: cartId, OrderId. The requirement is to capture them in IH.
So how can we process and store them in IH?
Thanks
Sathish
Pegasystems Inc.
IN
Ok so I now I understand. You did not mention about the additional fields being sent by the channel apps. To add those you will need to modify the 2nd strategy "CaptureInteractionHistory" used in the data flow and change the "Merge payload" data join shape which highlighted shape in the screenshot and map the additional properties in there.
Please try and see if that resolves your issue.
