pzPersistResults usage in the DF_ProcessOffer

Hi,

I am trying to run a campaign in the v8.7 with the Campaign Edition and not through the NBA Designer. I can see that there are zero records getting processed due to the Persist Results shape in the DF_ProcessOffer where all the results are filtered out. Can anybody please explain what is the use of the Persist Results shape and how does it get set to TRUE.

I tried tracing the agent- ProcessProgramRun, but was unable to do so.

Regards,

Neeraj

Persist Offer Issue.docx (2.14 MB)

Hi @NeerajKr,

You seem to have gotten yourself into internal code while debugging. What was the configuration of your Campaign, Segment, Strategy, etc.? Please share screenshots from an end-user facing functionality of what is not working.

Thanks,
~Jai.

Hi @Jai R.,

I would definitely share more details with you next week as I am away from my workstation for some days. But still I would highly appreciate if Pega starts providing at least the functional overview of technical changes which are introduced in the higher versions.

For e.g. this Persist Results shape. What is the use of this and when does it persist and when not.

My role is not limited as the end user of the application unfortunately.

Thanks,

Neeraj

Hi @Jai R.,

Here is a very simple campaign run which we performed. As requested, please find the screenshots of the artifacts in the document attached.

Hoping to hear back from you soon.

Regards,

Neeraj

Campaign Run Details.docx (3.59 MB)

Hi @NeerajKr,

Did you configure and save the Context Dictionary on your system before running these tests?

Thanks,

@Jai R.

Yes I did that.

Regards,

Neeraj

Hi @Jai R.,

Can you please help me in this topic or else connect with someone who can help me. It would really help me a lot if I get a quick solution to the problem.

Regards,

Neeraj

Hi @Jai R.,

Thanks, I figured out what was wrong. The strategy setup was wrong. I should have created a strategy in the PegaMKT-Data-Customer class which is my Customer class and then should have called this strategy in the wrapper strategy which is Data-Decision-Request-Customer. That solved the problem.

Wrapper Strategy

Actual Strategy

Regards,

Neeraj

Hi @NeerajKr,

For help with your specific situation, please raise a ticket with customer support.

Thanks,