Question
Coforge
US
Last activity: 22 Oct 2024 8:27 EDT
Sending channel Treatments to multiple devices (split treatments)
We are using Pega Decisioning v8.8.2.
Requirement is, when outbound campaign is running for each customer, customer will have associated mobile devices list (sublist and it it can be more than 1 devices), when an eligible offer's Mobile channel treatment is selected, we need to push treatment to all of the user devices.
So question is how Offer-Treatment strategy result can be split into multiple treatments based on number of devices customer have. Can this be done in Strategy itself ? if yes what is the approach ?
Or this can be done in Offerflow ?
or this needs to be done in separate dataflow after campaign is completed , if yes what the standard way to achieve this ?
please suggest.
Pegasystems Inc.
GB
To achieve the requirement of pushing a mobile channel treatment to all of a customer's devices you can consider the following approaches within Pega Decisioning v8.8.2: 1. Strategy: You can configure the Strategy to handle the splitting of treatments based on the number of devices. This involves creating a sub strategy that iterates over the list of devices and generates a treatment for each device. This approach ensures that the treatment logic is centralized within the decisioning strategy itself. 2. Offer Flow: If the Strategy approach is not feasible you can handle this in the Offer Flow. The Offer Flow can be designed to loop through the list of devices and apply the treatment to each device. This approach leverages the orchestration capabilities of the Offer Flow to manage the distribution of treatments. 3. Separate Data Flow: Another approach is to use a separate Data Flow after the campaign is completed. This Data Flow can process the results of the campaign split the treatments based on the number of devices and push the treatments accordingly. This approach decouples the treatment distribution logic from the main decisioning strategy and offer flow providing flexibility in handling complex scenarios. The standard way to achieve this would depend on your specific requirements and the complexity of your decisioning logic. If the logic is straightforward handling it within the Strategy or Offer Flow might be more efficient. For more complex scenarios a separate Data Flow might be more appropriate.
⚠ This is a GenAI-powered tool. All generated answers require validation against the provided references.
Managing Decision Data rules in Pega Customer Decision Hub
Inbound Channels > Web and Mobile treatment strategies
Coforge
US
@MarijeSchillern Thanks for sharing details.
In Offer flow there is no related shapes available to loop and send output data to DB template. This was my first though, since i didnt see any possible configuration shapes in Offerflow, so I raised this question.
For now we have used DB template wrapup activity dataflow to split outcome to multiple treatments based on devices list.
If this can be configured at Offerflow, I would still prefer that.. please clarify with more details.
Pegasystems Inc.
GB
@PavanKoduri @TomVanDuist @LukaszKarnasiewicz can someone from the Decisioning team help with this question?
Pegasystems Inc.
US
@ravindra007 This is the typical case for multi-level decisioning, where your Context Dictionary has a top level context of Customer (or Account if using our Comms data model) and Subscription or Device as the primary context. The starting strategy should be defined in Data-Decision-Request-Customer class and on the canvas, add the context shapes for Customer and within that context shape add Subscription/Devices. You would then add your appropriate logic to filter, apply prioritization, etc within each context shape. This would result in a strategy result for each Customer and each Subscription/Device depending on your logic.
NBA Designer does that for you so if not using it, I suggest you consider migrating to take advantage of its built-in behavior. You can review the document for the framework for examples https://docs.pega.com/bundle/customer-decision-hub/page/customer-decision-hub/cdh-portal/nba-strategy-overview.html