Question
Capgemini
IN
Last activity: 30 Aug 2021 14:44 EDT
OOTB Realtime Container REST api not working in Prospect Context
OOTB Realtime Container REST api not working in Prospect Context. Context is one of the inputs to this GET method.
This api returns relevant data when executed in Customer context. However, it throws exception when executed in prospect context.
PFA the detailed screenshots.
Any solution to this problem?
Thanks,
Suman.
Pegasystems Inc.
US
Hi @sumansinha, the recommended way to handle Prospects in CDH is through a flag/indicator on the customer class which designates this individual as a prospect instead of a full customer. What is your use-case that you are trying to use Propects?
Capgemini
IN
Thanks @SethRobinson for your reply!
As per our usecase, some Offers would be displayed to the Anonymous user (who would provide some very basic details like name, mobile number , mail id ,age ) in the React based portal. This React based UI would call Pega OOTB REST api to display relevant offers (configured inside NBA) to the prospect. We will capture the impression also when prospect will click on the offer using OOTB REST api.
Since Prospect could be configured inside Context Dictionary along with Customer, so we are thinking to store Prospect data into a separate table. Our assumption was that since SAVING of Context Dictionary will create many CDH specific rules in the backend , so it will create some Prospect related rules as well in Prospect data class which we could leverage later on.
However if Pega is recommending to handle Prospects in CDH through a flag/indicator on the customer class, we should be fine for this approach.
Pegasystems Inc.
US
@sumansinha If an anonymous user could also be a customer which hasn't been identified then treating them as a customer will also allow you to take advantage of a merged history of their behavior from anonymous to identified.
Capgemini
IN
Thanks @SethRobinson for your reply.
Now once the prospect fills up more information, then how could we convert that prospect into customer?
Can we update the same prospect record with more information and switch the flag from "Prospect" to "Customer" in Customer table?