I want to know if we can update customer attribute for a offer flow in CDH framework.
The context of the question is as below:
We are setting some customer attribute (Customer phone number) inside strategy for an outbound campaign. We have applied a Volume constrain in that campaign. But after processing in the SMS table we are getting the actual value of customer phone number from DB, not the updated value set in the strategy.
if we don't use volume constrain everything is working fine.
our understanding is when Pega is applying the VC, it is fetching the actual customer data again from DB , that is overriding the customer phone number set in Strategy.
Out plan is to set the logic in Offer flow itself, so that even after VC, we can have the customer phone number as per out logic.
When we are trying property set the customer attribute, we are getting the exception during checkin of the offer rule.
please let us know if it is a general validation or it is an environmental issue.
***Edited by Moderator Marije to add Capability tags***
@GOURABKETAN It seems that the issue you're facing is related to the volume constraint affecting the customer attribute update. One possible solution is to use the Context Dictionary in legacy mode by creating a Dynamic System Setting (DSS) named 'MKTIsContextDictionaryLegacyMode' with the ruleset 'PegaMKT-Engine' and setting its value to 'true'. This might help in retaining the updated customer attribute value even when using volume constraints.
Regarding the compilation error you're encountering while trying to set the customer attribute in the Offer flow, it might be an environmental issue or a compatibility problem. It is recommended to check your environment settings and ensure that you're using a compatible JVM version with your Pega platform.
This answer came from a Pega gen-AI assistant using the below references. As a Support Center moderator, I reviewed the answer and references for accuracy: