Volume Constraint Issue: Unable to determine the primary contact for this Offer
Hi,
I am trying to run Campaigns using the LegacyMode on. I am able to run the Batch campaigns without any error without the Volume Constraint rule. But as soon as I apply the Volume Constraint rule, the Action Flows go into an error state.
The Pega CDH version is 8.6. While the propositions are selected after the strategy run but the initiation of the Action Flows fail with the below error
| Unable to determine the primary contact for this Offer |
I have tried setting the below properties in the strategy as well
ERROR:
What am I missing?
Please note: Without the VC, the campaign run is successful.
Regards,
Neeraj
Accepted Solution
Updated: 24 May 2022 22:56 EDT
Vodafone
IN
Hi, I was able to resolve the issue by using the Context Dictionary in legacy mode.
To do that we have to create a DSS MKTIsContextDictionaryLegacyMode setting with the ruleset PegaMKT-Engine and set the value to true. That resolves the issue.
What is still not clear to me is what is difference b/w Legacy Context Dictionary and Standard Context Dictionary. The only difference which I noticed was that when the MKTIsContextDictionaryLegacyMode is set to true, the CDH portal was selecting the strategies which were on the Customer Class defined in the context dictionary rule and not the Data-Decision-Request-Customer.
Regards,
Neeraj
Pegasystems Inc.
GB
In the past these errors have been known to occur if in your Outbound design you are calculating the campaign dynamically on underlying sub-strategies . During calculation of the top level, the context wrapper may be missing, so on the BatchoutXXX_VC table, no ID attribute got recorded for the action.
You appear to need a fast response: Please can you confirm that you have logged a support incident for this?
I can see that last year Vodafone had a similar issue logged with support, and the analysis at the time was that this is behaving as expected.
"Using Volume constraints in combination with the Primary Contact strategy capability is not supported currently in the product.
The Primary Contact strategy is required when a Multi Channel Campaign yields Actions for contexts above primary.
In a future release, we can consider adding improved validation to prevent this unsupported combination.
Thus to sum it up,
User can run a multi channel campaign on a context other than the Primary. This is when a Primary Contact Strategy is required.
A multi-channel campaign defined on a context "above" primary cannot use volume constraints. For context below primary, VC will continue to work - because it doesn't require a primary contact selection strategy."
In the past these errors have been known to occur if in your Outbound design you are calculating the campaign dynamically on underlying sub-strategies . During calculation of the top level, the context wrapper may be missing, so on the BatchoutXXX_VC table, no ID attribute got recorded for the action.
You appear to need a fast response: Please can you confirm that you have logged a support incident for this?
I can see that last year Vodafone had a similar issue logged with support, and the analysis at the time was that this is behaving as expected.
"Using Volume constraints in combination with the Primary Contact strategy capability is not supported currently in the product.
The Primary Contact strategy is required when a Multi Channel Campaign yields Actions for contexts above primary.
In a future release, we can consider adding improved validation to prevent this unsupported combination.
Thus to sum it up,
User can run a multi channel campaign on a context other than the Primary. This is when a Primary Contact Strategy is required.
A multi-channel campaign defined on a context "above" primary cannot use volume constraints. For context below primary, VC will continue to work - because it doesn't require a primary contact selection strategy."
Please check available documentation:
Frequently asked questions about volume constraints
Suggestion:
If there is no further input on this forum question I would suggest that you log a support incident in order to have the support team check your particular scenario.
Vodafone
IN
Hi @MarijeSchillern,
Thanks a lot for explaining it in detail. I did not get it completely though especially the below sentence
During calculation of the top level, the context wrapper may be missing, so on the BatchoutXXX_VC table, no ID attribute got recorded for the action.
I can see that pyName, pxIdentifier, ActionContext etc. are populated for the VC table. When comparing the VC table of a failed campaign with a non-VC table of successful campaign, I figured out the below columns which are missing.
Hi @MarijeSchillern,
Thanks a lot for explaining it in detail. I did not get it completely though especially the below sentence
During calculation of the top level, the context wrapper may be missing, so on the BatchoutXXX_VC table, no ID attribute got recorded for the action.
I can see that pyName, pxIdentifier, ActionContext etc. are populated for the VC table. When comparing the VC table of a failed campaign with a non-VC table of successful campaign, I figured out the below columns which are missing.
|
BundleType
|
|
CampaignDriverClass
|
|
CampaignID
|
|
CommunicateTo
|
|
FlowStatus
|
|
LastFlowStep
|
|
pyCategory
|
|
pyDivision
|
|
pyOperator
|
|
pyOrganization
|
|
pyUnit
|
|
StatusWork
|
|
TreatmentKeyCode
|
The missing CampaignDriverClass seems to be an issue as that determines what is the Primary/Customer class for the campaign run.
Please note that I am using a Pega Lab instance for understanding the issues which we can face with LegacyCampaigns and the version is 8.6. The campaign is not using any strategy which is supported by the NBAD FW.
I don't think I can raise an SR for something which is not working on Pega Labs. Please correct me if I am wrong. In that case, I would need your help to get connected with an SME who can look at the problem and suggest the next steps, may be over a WebEx session.
Regards,
Neeraj
Accepted Solution
Updated: 24 May 2022 22:56 EDT
Vodafone
IN
Hi, I was able to resolve the issue by using the Context Dictionary in legacy mode.
To do that we have to create a DSS MKTIsContextDictionaryLegacyMode setting with the ruleset PegaMKT-Engine and set the value to true. That resolves the issue.
What is still not clear to me is what is difference b/w Legacy Context Dictionary and Standard Context Dictionary. The only difference which I noticed was that when the MKTIsContextDictionaryLegacyMode is set to true, the CDH portal was selecting the strategies which were on the Customer Class defined in the context dictionary rule and not the Data-Decision-Request-Customer.
Regards,
Neeraj