Question
Areteans Technology Solutions
AU
Last activity: 17 Feb 2021 10:12 EST
Why Pega Marketing introduced Data-Decision-Request-Customer class?
1) Why Pega Marketing introduced Data-Decision-Request-Customer class to hold the strategies that are configured to a campaign? What is the value add to this design change?
2) Why does the campaign throws an exception on the strategy (Strategy <Strategy Name> is not configured correctly for use in a Campaign) during campaign validation until the strategy uses an embedded strategy that runs on the customer context?
I have attached screenshots of the final and only strategy configuration that did not throw error during a campaign validation below.
Accepted Solution
Pegasystems Inc.
US
Pegasystems Inc.
US
I have reached out to the SME. Hopefully he will provide his insights on your questions.
Areteans Technology Solutions
AU
2) Why does the campaign throw an exception on the "Campaign" (Strategy <Strategy Name> is not configured correctly for use in a Campaign) during campaign validation until the strategy uses an embedded strategy that runs on the customer context?
Edited the post
Erste Digital
AT
I would like to know the same answer..For the strategies to be configured for campaigns, we always need it to be created as embedded strategy of data-decision-request-customer class only. What is the reason behind this design?
Accepted Solution
Pegasystems Inc.
US
In Pega Marketing 7.4, we introduced support for multi-level decisioning (ie. decision at household or individual customer levels) and the notion of a Context Dictionary where you define your marketing data structure and indicate your primary context. The primary context is the entity that will be receiving the email, SMS, push etc and is typically the Customer class.
In order to support the Context Dictionary and have the flexibility to define an arbitrary primary context we introduced a root decisioning class (Data-Decision-Request-Customer) that has a property for each context defined in the Context Dictionary.
Having this support to decision at the household or customer level requires that the strategy canvas contain the appropriate Context shape and exist in the Data-Decision-Request-Customer class. If you are migrating strategies, you can create what we refer to as a "wrapper" strategy that sits in Data-Decision-Request-Customer with the appropriate context and reference a strategy in your customer class.
After you've defined your context dictionary, on the strategy canvas menu, you will see your context entities under Sub strategy menu
In Pega Marketing 7.4, we introduced support for multi-level decisioning (ie. decision at household or individual customer levels) and the notion of a Context Dictionary where you define your marketing data structure and indicate your primary context. The primary context is the entity that will be receiving the email, SMS, push etc and is typically the Customer class.
In order to support the Context Dictionary and have the flexibility to define an arbitrary primary context we introduced a root decisioning class (Data-Decision-Request-Customer) that has a property for each context defined in the Context Dictionary.
Having this support to decision at the household or customer level requires that the strategy canvas contain the appropriate Context shape and exist in the Data-Decision-Request-Customer class. If you are migrating strategies, you can create what we refer to as a "wrapper" strategy that sits in Data-Decision-Request-Customer with the appropriate context and reference a strategy in your customer class.
After you've defined your context dictionary, on the strategy canvas menu, you will see your context entities under Sub strategy menu
In Pega Marketing 7.4, we introduced support for multi-level decisioning (ie. decision at household or individual customer levels) and the notion of a Context Dictionary where you define your marketing data structure and indicate your primary context. The primary context is the entity that will be receiving the email, SMS, push etc and is typically the Customer class.
In order to support the Context Dictionary and have the flexibility to define an arbitrary primary context we introduced a root decisioning class (Data-Decision-Request-Customer) that has a property for each context defined in the Context Dictionary.
Having this support to decision at the household or customer level requires that the strategy canvas contain the appropriate Context shape and exist in the Data-Decision-Request-Customer class. If you are migrating strategies, you can create what we refer to as a "wrapper" strategy that sits in Data-Decision-Request-Customer with the appropriate context and reference a strategy in your customer class.
After you've defined your context dictionary, on the strategy canvas menu, you will see your context entities under Sub strategy menu
In Pega Marketing 7.4, we introduced support for multi-level decisioning (ie. decision at household or individual customer levels) and the notion of a Context Dictionary where you define your marketing data structure and indicate your primary context. The primary context is the entity that will be receiving the email, SMS, push etc and is typically the Customer class.
In order to support the Context Dictionary and have the flexibility to define an arbitrary primary context we introduced a root decisioning class (Data-Decision-Request-Customer) that has a property for each context defined in the Context Dictionary.
Having this support to decision at the household or customer level requires that the strategy canvas contain the appropriate Context shape and exist in the Data-Decision-Request-Customer class. If you are migrating strategies, you can create what we refer to as a "wrapper" strategy that sits in Data-Decision-Request-Customer with the appropriate context and reference a strategy in your customer class.
After you've defined your context dictionary, on the strategy canvas menu, you will see your context entities under Sub strategy menu