id
stringlengths 14
14
| text
stringlengths 2
2.42k
| source
stringclasses 1
value |
|---|---|---|
b85ada602223-0 | 427
OPTI KT Second Line Private Pricing
Configuration of Second Line Private Pricing Offer:
Offers - created via PM Tool Offer screen.
AddTablet
Offer “AddTablet” is Configured.
Map applicable channels.
Map applicable execution mode.
OfferVariation Screen
Configure OfferVariations | VODKB-200723-160306.pdf |
7f2faa0afa0a-0 | 428
OfferToOfferVariation Screen
Map OfferVariations to Second Line Offers
Treatment Screen
Configure WEB Treatments for Second Line Offers | VODKB-200723-160306.pdf |
91105e7a6e32-0 | 429
In Strategy: PopulateOutputPropertiesForApp and PopulateOutputPropertiesForGetNBA the content to be displayed in My Vodafone App is
populated from two Decision Data - T2TVAttributes and T2TVActions.
Decision data: T2TVAttributes - provides content of the page.
Decision data: T2TVActions - defines actions for buttons on the page.
Data for above decision data is configured in PM Tool (explained in the next section ‘PM Tool Screens’).
T2TVAttributes (Treatment To Treatment Variations Attributes)
This decisio data holds Content of page
T2TVActions (Treatment To Treatment Variations Actions)
This decision data holds information of the Button actions i.e. what needs to be done for a button click
PM Tool Screens | VODKB-200723-160306.pdf |
6f624f2be0b6-0 | 430
There are no separate screens for the two main decision data: T2TVAttributes and T2TVActions. Instead data from a combination of
screens in PM Tool is sent to the above mentioned decision data.
Screen: Channel
Below is a screenshot of Channel screen.
1. New channel “WEB” is created.
2. Possible outcomes are added e.g. “Clicked”
3. Tick, if templates are required for the channel.
4. Tick, if Actions are needed on the template e.g. buttons.
Screen: Template Attributes
1. Used to create new template attribute, example - “ImageURL” attribute
Short Text (Single-Line Datatype) 256
Long Text (Multi-Line Datatype) 4000Attribute Max Length | VODKB-200723-160306.pdf |
02a169a14cd6-0 | 431
Screen: Template
1. New templates “WebUpgradesAndOffers” and “WebPurchase“ are created.
2. Add Attributes to new template
Later data is added to the template from Treatment To Treatment Variations screen.
Screen: Action Attributes
Allows to create action attributes, new attribute is created “URL” | VODKB-200723-160306.pdf |
3ebb26dce3ac-0 | 432
Screen: Actions
A new action is created from ‘Actions’ screen.
1. New Action “WebClickedAction” is created.
a. Add Attributes to new template
2. Data is added to the action from Treatment To Treatment Variations screen.
Screen: TreatmentToTreatmentVariations
For a specific Treatment Variant, Configure Templates and Outcomes created in other screens | VODKB-200723-160306.pdf |
e5ea9772cdea-0 | 433
Templates section:
Outcomes section: | VODKB-200723-160306.pdf |
1603d682e72b-0 | 434
Request Body:
{
"Identifier": {
"Account": {
"AccountNumber": "78101117",
"Status": "Existing",
"Type": "Consumer"
},
"ServiceNumber": "447077101123"
},
"RequestorDetail": {
"Channel": "WEB",
"SubChannel": "UpgradesAndOffers"
},
"Context": {
"PrimaryContext": "Upgrades_And_Offers",
"NoOfActions": 0,
"Detail": []
}
}
Response:
{
"InteractionId": 2110594958894618725,
"ActionList": [ {
"Propensity": 0.25,
"Priority": 2,
"OfferVariant": "OfferVariantDefault",
"Channel": "WEB",
"SubChannel": "UpgradesAndOffers",
"OfferId": "XSL021",
"OfferName": "AddMifi", | VODKB-200723-160306.pdf |
f07d6044ef34-0 | 435
"TreatmentId": "XSL025-01",
"OfferDescription": "",
"TreatmentVariant": "TreatmentVariantDefault",
"Detail": [
{
"Value": "SIMO",
"Name": "journey"
},
{
"Value": "15.0 discount just for you",
"Name": "sash"
},
{
"Value": "Up to 15.0 on an additional selected SIM only plan with Vodafone. Just a little thank you from us.",
"Name": "body"
},
{
"Value": "Keep your phone and get Extra Discounts on a SIMO plan just for you",
"Name": "title"
}
],
"TreatmentName": "AddMifi_WEB"
}],
"CustomerId": "PP2L-SUB-101123-STF"
} | VODKB-200723-160306.pdf |
2337f8fe7e7b-0 | 436
OPTI KT: Test Cell Management in 2nd Line Private Pricing
TestGroups can be mapped to Second Line Offers in Offer Screen.
Note: Only one TestGroup can be mapped to Offer.
In Test Cell Management Screen , TestGroups, TestGroupExpiry, TestGroup enable / disable is configured.
Cell Code is generated in sequential order with test group name. Initial value of a test cell should be equal to Final value of previous test cell
plus(+) one.
TestGroup Split is dependent on business need.
Once Test Group value is entered, two default test cells are populated as below and test cells range should be from 1-100.
Initial value for the first test cell and Final value for the last test cell are disabled
Note: This Screen pushes data into two seperate decision datas TestGroups and TestCells | VODKB-200723-160306.pdf |
08b023e8804f-0 | 437
TestGroups Decision Data:
TestCells Decision Data:
AdditionalLineDiscount Matrix: There is no seperate screen in PM tool for conffiguring discount codes. Note: This should be manually
uploaded in system.
Decision Data Example: | VODKB-200723-160306.pdf |
3d4ba4b87258-0 | 438
OPTI KT: GetNBA Logic
Strategy: IdentifyEligibleOffers
As part of re-design, TestCellManagement is invoked at Offer Level
Note: This change ensures that Test Cell Management is available for all offers for all execution modes with the caveat that ineligible offers
may be allocated a test cell but not used.
TestGroups and TestCells Decision data is used in TestCellManagement Strategy
Strategy: IdentifyTestCell
As part of re-design IdentifyTestCell Strategy is modified.
Note: Same Cell Code must be allocated for offers belonging to same test group irrespective of their business purpose
In the existing GetNBA logic, 2nd line private pricing functionality is called in the below strategy when
@String.contains(.OfferCategory,"Additional Line")&&@String.contains(.ProductGroup,"Mobile")
Strategy: PopulateOutputPropertiesForWeb
The strategy is called from PopulateOutputPropertiesForWeb when Execution Mode is GetNBA
Strategy: AssignDiscountToAdditionalLineOffers Strategy | VODKB-200723-160306.pdf |
39b2e647a370-0 | 439
ManageAdditionalLineDiscount Strategy:
Strategy input is Discount Treatments with tariff details. In this strategy, Discount Identifiers are set from DiscountMatrix if
TariffType,TariffTier,CellCode and Duration Conditions are met otherwise default discount identifier is set from OffertoOfferVariation.
Note: AdditionalLineDiscountMatrix decision data is invoked in this strategy
DiscountCompatibilityCheck Strategy:
Compatible of tariffs to discount is calculated in this strategy and return both compatible and non compatible tariffs. Non Compatible tariffs
discount codes are overridden to null.
GetDiscountProductDetails Strategy:
Both Compatible and Non Compatible tariffs are an input to this strategy. Discount Amount is calculated only for compatible tariffs. This
strategy returns both compatible and non compatible discount tariffs.
GetHeadlineDiscount Strategy:
Finding max discount only for Legally Compliance records
Note: LegalRequirement is configured in AOMBusiness Config. Only Decimals should be configured
Strategy: PopulateOutputPropetiesForGetNBA
GetNBA outputs are inf the form of offers/propositions e.g. parent could be the Tariff offer and discount offer is child.
In the logic flow, screenshot below, Parent Offer for Tariff flows throught the top path.
Below that is the Child offer route for Discount. In API response discounts are present in the Detail section. | VODKB-200723-160306.pdf |
8317c110e2a6-0 | 440
Finally Disounts are joined with Tariffs. | VODKB-200723-160306.pdf |
027ead67c3bf-0 | 441
OPTI KT: Get Product List Logic
Strategy: GetProductList is the main strategy.
It calls sub-strategy GetProductListForUpgrade and GetProductListForAdditionalLine that contains the existing GetProductList logic for
Upgrades and the 2nd Line Pricing logic respectively.
Switch component chooses the relevant route based on the .OrderType from API request context.
Call Strategy: GetProductListForUpgrade if .OrderType is "Upgrade" or “Flexi Upgrade"
Call Strategy: GetProductListForAdditionalLine of .OrderType is "In Life Sales"
Set .ErrorMessage = “Invalid Order Type” otherwise
Strategy: GetProductListForAdditionalLine
Note: As part of re-design TestCellManagement is invoked at Offer level.
GetAllTariffs Strategy: | VODKB-200723-160306.pdf |
9f30234bbb59-0 | 442
Notes: With new logic changes:
AddMobileWithHandset - Include tariffs where tariff type is Handset
AddSIMO - Include all tariffs where tariff type is either Handset or SIMO
GPL Second Line PP Request Body:
{
"SubscriptionId": "PP2L-SUB-100766-STF",
"ServiceNumber": "447077100766",
"OwnerAccountNumber": "78100766",
"AgentId": "SuperSave",
"RecommendationId":"RecommendationId",
"Division": "*",
"ParentDivision":"False",
"Channel": "Web",
"SubChannel": "UpgradesAndOffers",
"OrderType": "In Life Sales",
"CaseId" : "123456",
"ProductType": "Tariff",
"SubscriptionType": "Mobile Broadband Service",
"LoanEligibilityStatus": "Eligible",
"Detail": [
{
"Name":"SIMO",
"Value":"False"
},
{
"Name":"UPGRADE_TYPE",
"Value":"FLEXUPGRADE"
},
{
"Name":"NO_RECOMMENDATIONS",
"Value":"5"
}
],
"LineItems": [
{
"ProductId": "211010",
"ProductType": "Handset"
} | VODKB-200723-160306.pdf |
f947e82656bc-0 | 443
]
}
Response Body:
{"LineItems": [
{
"ProductName": "36mth Band 0A Tablet Unlimited Business Plan",
"ProductId": "114190",
"Tenure": 36,
"IncludesCombiBundleOffer": false,
"DisplayName": "36mth Band 0A Tablet Unlimited Business Plan",
"Propensity": 0,
"Position": 1,
"Priority": 0,
"ProductType": "Tariff",
"Data": "9437184",
"ChildLineItems": [ {
"ProductName": "37 mth discount: 10% off line rental",
"ProductId": "114436",
"DisplayName": "37 mth discount: 10% off line rental",
"Propensity": 0,
"Position": 6,
"Priority": 0,
"ProductType": "Discount",
"DiscountAmount": 10,
"DiscountType": "Percentage",
"PriceType": "DISCOUNT"
}],
"DiscountType": "Percentage"
},
{
"ProductName": "36mth Band 0A Tablet Business Plan 12GB",
"ProductId": "114187",
"Tenure": 36,
"IncludesCombiBundleOffer": false,
"DisplayName": "36mth Band 0A Tablet Business Plan 12GB",
"Propensity": 0,
"Position": 5,
"Priority": 0,
"ProductType": "Tariff",
"Data": "12288",
"ChildLineItems": [ {
"ProductName": "37 mth discount: 10% off line rental",
"ProductId": "114436",
"DisplayName": "37 mth discount: 10% off line rental", | VODKB-200723-160306.pdf |
f947e82656bc-1 | "DisplayName": "37 mth discount: 10% off line rental",
"Propensity": 0,
"Position": 3,
"Priority": 0,
"ProductType": "Discount",
"DiscountAmount": 10, | VODKB-200723-160306.pdf |
0c656cf2f032-0 | 444
"DiscountType": "Percentage",
"PriceType": "DISCOUNT"
}],
"DiscountType": "Percentage"
},
{
"ProductName": "36mth Band 0A Tablet Business Plan 6GB",
"ProductId": "114186",
"Tenure": 36,
"IncludesCombiBundleOffer": false,
"DisplayName": "36mth Band 0A Tablet Business Plan 6GB",
"Propensity": 0,
"Position": 4,
"Priority": 0,
"ProductType": "Tariff",
"Data": "6144",
"ChildLineItems": [ {
"ProductName": "37 mth discount: 10% off line rental",
"ProductId": "114436",
"DisplayName": "37 mth discount: 10% off line rental",
"Propensity": 0,
"Position": 2,
"Priority": 0,
"ProductType": "Discount",
"DiscountAmount": 10,
"DiscountType": "Percentage",
"PriceType": "DISCOUNT"
}],
"DiscountType": "Percentage"
},
{
"ProductName": "36mth Band 0A Tablet Business Plan 2GB",
"ProductId": "114185",
"Tenure": 36,
"IncludesCombiBundleOffer": false,
"DisplayName": "36mth Band 0A Tablet Business Plan 2GB",
"Propensity": 0,
"Position": 3,
"Priority": 0,
"ProductType": "Tariff",
"Data": "2048",
"ChildLineItems": [ {
"ProductName": "37 mth discount: 10% off line rental",
"ProductId": "114436", | VODKB-200723-160306.pdf |
0c656cf2f032-1 | "ProductId": "114436",
"DisplayName": "37 mth discount: 10% off line rental",
"Propensity": 0,
"Position": 1,
"Priority": 0,
"ProductType": "Discount",
"DiscountAmount": 10,
"DiscountType": "Percentage", | VODKB-200723-160306.pdf |
723167adae28-0 | 445
"PriceType": "DISCOUNT"
}],
"DiscountType": "Percentage"
},
{
"ProductName": "36mth Band 0A Tablet Unlimited Max Business Plan",
"ProductId": "114191",
"Tenure": 36,
"IncludesCombiBundleOffer": false,
"DisplayName": "36mth Band 0A Tablet Unlimited Max Business Plan",
"Propensity": 0,
"Position": 2,
"Priority": 0,
"ProductType": "Tariff",
"Data": "9437184",
"ChildLineItems": [ {
"ProductName": "37 mth discount: 10% off line rental",
"ProductId": "114436",
"DisplayName": "37 mth discount: 10% off line rental",
"Propensity": 0,
"Position": 7,
"Priority": 0,
"ProductType": "Discount",
"DiscountAmount": 10,
"DiscountType": "Percentage",
"PriceType": "DISCOUNT"
}],
"DiscountType": "Percentage"
}
]} | VODKB-200723-160306.pdf |
9b50b5b965ef-0 | 446
OPTI KT MVA- Full Screen Promo
Objective
When app is launched, My Vodafone App shoud support a full screen pop-up window, containing a single-offer promotion. This window will
appear once. To support this new sub channel called FullScreenTakeover is introduced
This functionality is a part of existing API: GetNBA
Notes:
AOM will control which offers have full-screen promotions and whether they are returned to the App. Full screen offers will be provided in
addition to the Discover offers.
Only 1 full screen promotion will be returned per call. If multiple offers have full screen promotions then AOM will pick the best, based on
standard arbitration logic.
Whenever a full screen promotions is returned the call must also contain a corresponding Discover offer, which should have position #1
in the Discover carousel.
We will pick the full screen promotion from the top N discover offers. If none have an FSP then no FSP will be returned.
Configuration of MVA FullScreen Offer:
Offers - created via PM Tool Offer screen.
AddBroadbandProExtra
New Offer “AddBroadbandProExtra” is created.
Map applicable channels.
Map applicable execution mode. | VODKB-200723-160306.pdf |
af4ee6a077c6-0 | 447
OfferVariation Screen
Configure OfferVariations
OfferToOfferVariation Screen
Map OfferVariations to MVA FullScreenPromo Offers | VODKB-200723-160306.pdf |
e5c5eef37bd1-0 | 448
Screen: SubChannel
Configure new subchannel 'FullScreenTakeover' to an existing App channel
Treatment Screen
Configure App Treatments for App Offers
Enable Subchannels for treatments | VODKB-200723-160306.pdf |
4d55d76f6284-0 | 449
TreatmentToSubchannels:
T2TVAttributes (Treatment To Treatment Variations Attributes)
This decision data holds Content of page
T2TVActions (Treatment To Treatment Variations Actions)
This decision data holds information of the Button actions i.e. what needs to be done for a button click
PM Tool Screens
There are no separate screens for the two main decision data: T2TVAttributes and T2TVActions. Instead data from a combination of
screens in PM Tool is sent to the above mentioned decision data.
Screen: Channel
Below is a screenshot of Channel screen.
1. New channel “App” is created.
2. Possible outcomes are added e.g. “Clicked”
3. Tick, if templates are required for the channel.
4. Tick, if Actions are needed on the template e.g. buttons.
TreatmentToSubChannel
sNonPropositions TrackYourOrder_App App FullScreenTakeover
TreatmentToSubChannel
sNonPropositions AddBroadbandProExtra_
AppApp FullScreenTakeover
TreatmentToSubChannel
sNonPropositions AddSmartwatch_App App FullScreenTakeoverpyGroup pyIssue TreatmentName Channel TargetSubChannel | VODKB-200723-160306.pdf |
c6d60223a9f3-0 | 450
Screen: Template Attributes
1. Used to create new template attribute, example - “ImageURL” attribute
Screen: Template
1. New template “AppFSPDefault” is created.
2. Add Attributes to new template
Later data is added to the template from Treatment To Treatment Variations screen. | VODKB-200723-160306.pdf |
b7dceb62375e-0 | 451
Screen: Action Attributes
1. Allows to create action attributes, new attribute is created “URL”
Screen: Actions
1. A new action is created from ‘Actions’ screen.
2. New templates “AppFSPClickAction” and “AppFSPDismissAction“ are created.
a. Add Attributes to new template
3. Data is added to the action from Treatment To Treatment Variations screen. | VODKB-200723-160306.pdf |
922461ac5d94-0 | 452
Screen: TreatmentToTreatmentVariations
For a specific Treatment Variant, Configure Templates and Outcomes created in other screens
Templates section: | VODKB-200723-160306.pdf |
2cb57b8e6a94-0 | 453
Outcomes section:
Request Body:
"{
"Identifier": {
"Account": {
"AccountNumber": "89289",
"Status": "Existing",
"Type": "Consumer"
},
"ServiceNumber": "447920770018"
},
"RequestorDetail": {
"Channel": "App",
"SubChannel": "Discover"
}, | VODKB-200723-160306.pdf |
edf71da4a99f-0 | 454
"Context": {
"PrimaryContext": "",
"NoOfActions":10,
"Detail": [
]
}}"
Response Body:
"{
"InteractionId": -7492870612923041121,
"ActionList": [
{
"Propensity": 0.25,
"Actions": [
{
"Type": "Button",
"Outcome": "Dismissed",
"Id": "AppFSPDismissAction",
"Detail": [
{
"Value": "Vodafone logo
"Name": "url"
},
{
"Value": "Shop now",
"Name": "label"
},
{
"Value": "Dismissed",
"Name": "action"
},
{
"Value": "1",
"Name": "index"
}
]
},
{
"Type": "Button",
"Outcome": "Clicked",
"Id": "AppFSPClickAction",
"Detail": [
{
"Value": "Vodafone logo
"Name": "url"
},
{
"Value": "Shop now",
"Name": "label"
},
{ | VODKB-200723-160306.pdf |
5f0e0641ab83-0 | 455
"Value": "ReDirect",
"Name": "action"
},
{
"Value": "1",
"Name": "index"
}
]
}
],
"OfferVariant": "Apple",
"Priority": 1,
"Channel": "App",
"SubChannel": "FullScreenTakeover",
"OfferId": "XSL011",
"OfferName": "AddSmartwatch",
"TreatmentId": "XSL011-T0004",
"OfferDescription": "",
"TreatmentVariant": "AppleSmartWatch",
"Detail": [
{
"Value": "Vodafone – Our Best Ever Network | Now With 5G
"Name": "imageURL"
},
{
"Value": "Treat yourself to a new watch ",
"Name": "title"
},
{
"Value": "Get the Apple Watch Series 6 ",
"Name": "body"
}
],
"TreatmentName": "AddSmartwatch_App"
},
{
"Propensity": 0.25,
"Actions": [
{
"Type": "Button",
"Outcome": "Clicked",
"Id": "AppDirectToURLAction",
"Detail": [
{
"Value": "Vodafone logo
"Name": "url"
},
{
"Value": "Shop now",
"Name": "label"
}, | VODKB-200723-160306.pdf |
25d444ba07a5-0 | 456
{
"Value": "ReDirect",
"Name": "action"
},
{
"Value": "1",
"Name": "index"
}
]
},
{
"Type": "Button",
"Outcome": "Clicked",
"Id": "AppDirectToDismissed",
"Detail": [
{
"Value": "Vodafone logo
"Name": "url"
},
{
"Value": "DiscoverDismissed",
"Name": "label"
},
{
"Value": "ReDirect",
"Name": "action"
},
{
"Value": "1",
"Name": "index"
}
]
}
],
"OfferVariant": "Apple",
"Priority": 1,
"Channel": "App",
"SubChannel": "Discover",
"OfferId": "XSL011",
"OfferName": "AddSmartwatch",
"TreatmentId": "XSL011-T0004",
"OfferDescription": "",
"TreatmentVariant": "AppleSmartWatch",
"Detail": [
{
"Value": "Vodafone – Our Best Ever Network | Now With 5G
"Name": "imageURL"
},
{
"Value": "Get the Apple Watch Series 6 ",
"Name": "body" | VODKB-200723-160306.pdf |
d266c93738e5-0 | 457
},
{
"Value": "Treat yourself to a new watch Discover ",
"Name": "title"
}
],
"TreatmentName": "AddSmartwatch_App"
}
],
"CustomerId": "2-FSP_Crosssell"
}"
FSP Request a …
26 Sep 2022, 08:19 AMrs.json
FSP Request a …
26 Sep 2022, 08:16 AMer.json | VODKB-200723-160306.pdf |
5001d4aa9b24-0 | 458
Scenario Based Templating
Templates will include a new dimension called “Scenario” in addition to “TreatmentVariation” and “SubChannel”
Use of Templates will remain optional
If a TreatmentVariation does not use SubChannel functionality, “Default” SubChannel will be used
The main template returned by decisioning funnel will be configured as “Default” scenario
Additional “alternate” scenarios will be configured to manage different templates by scenarios - such as Inactive, Expired, Ineligible,
OrderConfirmed, OrderFailed etc.
Use of “alternate” scenarios will be bespoke to channel and as per use cases
“Scenario” used will be written to IH
“Actions” will be updated to be based on Templates
The above changes will be applied for existing IVR template management (GetNBA), 2nd Line Pricing (GetNBA), Assisted Upgrade and
new Landing Pages functionality but will be available to any modes that use Template functionality
Note:
From now T2TVAttributes DD under All Squads contain Scenario column
From now T2TVActions DD under All Squads contain Scenario and TargetSubChannel column
I. Changes for IVR Channel (GetNBA)
Updated below Strategies to add extra join Conditions to include new Scenario SR property while joining Actions and Attributes Data
1)PopulateOutputPropertiesForGetNBA
2)IdentifyT2TVariationActions
II. Changes for 2nd Line Pricing (GetNBA)
Updated below Strategies to add extra join Conditions to include new Scenario SR property while joining Actions and Attributes Data
1)PopulateOutputPropetiesForGetNBAPrivatePricing
III. Changes for InboundCC Channel (VADR)
Updated below Strategies to add extra join Conditions to include new Scenario SR property while joining Actions and Attributes Data
1) PopulateOutputPropertiesForNBAA | VODKB-200723-160306.pdf |
5001d4aa9b24-1 | 1) PopulateOutputPropertiesForNBAA
IV. Changes for LandingPages (Microsite)
Updated below Strategies to add extra join Conditions to include new Scenario SR property while joining Actions and Attributes Data
1)GetInactiveMicrositeTreatment
2)GetExpiredMicrositeTreatment
3)GetIneligibleMicrositeTreatment | VODKB-200723-160306.pdf |
5a61728d9e89-0 | 459 | VODKB-200723-160306.pdf |
6331ba9b16f5-0 | 460
Extras Landing Page KT
Introduction
Objective of Extras Landing Page is to display a web page (developed in Microsite), when customer clicks a link inside a SMS. The web
page presents the customer with some offers e.g. 1GB or 2GB of extra data.
Pre-requisite: NBA Batch or T2S has sent SMS to customers. The SMS body contains a link for Microsite, which customer needs to click.
When customer clicks on the link, below Microsite pages are displayed.
Below screenshot shows a Parent offer with 2 child offers, for 1GB and 2GB. The concept of Parent-Child offers or ‘Bundling’ in Pega terms
is explained in later part of this document.
The microsite page displayed for a scenario e.g. success, failure etc. is customizable via template and contents configured in PM Tool.
Parent-Child relationship is configured in a decision data via PM Tool, explained in the ‘Propositions’ section, later in this document.
“Buy Now” button click displays below page i.e. the offer acceptance is being processed. | VODKB-200723-160306.pdf |
e75382b01ac6-0 | 461
Now, if the customer clicks on the same link, Microsite will not display the accepted offer. Only the remaining eligible offer(s) will be
displayed.
An example of a Parent offer without any child offer is:
This functionality is dev-tested/ST-tested and can be used in all squads. | VODKB-200723-160306.pdf |
ccae5624fa4e-0 | 462
One of the squad example is:
BusinessPurpose = Retain
OfferExecutionMode / ExecutionMode = LandingPages
Channel = Microsite
Sequence of Events
1. NBA Batch Process or T2S sends SMS to customer that has the Microsite link.
2. Customer clicks on the link.
3. App layer will land the customer on Microsite landing page. Microsite is just a Pega Case.
4. Logic layer does re-validation to check if the offer is still available and the customer is eligible for the offer.
5. For re-validation sucess scenario, eligible offer (single Parent OR Parent + Child offers) are displayed.
6. Along with success scenario, that writes Shown outcome in IH, Revalidation process also writes to IH for Inactive, Expired and Ineligible
scenarios. Relevant templates are sent to App layer to display the appropriate Microsite page.
7. If interested in the offer, customer clicks “Buy now” button.
8. CSO (Create Sales Order) logic gets invoked by the App layer.
9. The CSO process, if successful, writes Accepted response in Interaction History. Logic notifies the app layer to display a success
Microsite page.
10. CSO process, if not successful, writes a Failure response in Interaction History. Logic notifies the app layer to display a failure Microsite
page. | VODKB-200723-160306.pdf |
6ea6d0740f82-0 | 463
XLP Propositions and PM Tool Screens
Offers - created via PM Tool Offer screen.
TestOffer3 = Parent Offer
TestOffer4 = Child offer for the Parent offer - representing 1GB
TestOffer5 = Child offer for the Parent offer - representing 2GB
1. New Offer “TestOffer3” is created.
2. Map applicable channels.
3. Map applicable execution mode. | VODKB-200723-160306.pdf |
abae6fe34ce2-0 | 464
ParentChildTreatments decision data
This decision data contains the parent child offer mappings. E.g.
BundleParentTreatment BundleChildTreatment
TestOffer3_Microsite TestOffer4_Microsite
TestOffer3_Microsite TestOffer5_Microsite
Offer Bundling set up for Landing pages
Bundling logic for landing pages is done in Strategy: ApplyBundlingForMicrositeTreatments.
Offer bundling logic and set up for Landing pages is same as done for other functionalities. Bundling is needed when there is a requirement
of having Parent and Child offer(s) e.g. Parent offer is Extra Data and child offers could be, 1GB data, 2GB data etc.
Step1: Below two fields (1,2) in Treatment screen needs to be configured for a Parent treatment. | VODKB-200723-160306.pdf |
a23aa7094b28-0 | 465
In Strategy: PopulateOutputPropertiesForMicrosite (described in ‘XLP Logic Components’ section of this document), the content to be
displayed in Offers Landing Page is populated from two Decision Data - T2TVAttributes and T2TVActions.
Decision data: T2TVAttributes - provides content of the page.
Decision data: T2TVActions - defines actions for buttons on the page.
Data for above decision data is configured in PM Tool (explained in the next section ‘PM Tool Screens’).
T2TVAttributes (Treatment To Treatment Variations Attributes)
Each Microsite screen displayed is based on a scenario e.g. Default, Success, Failure etc. For an offer/treatment, this decision data holds
information of the template details that needs to be used for a relevant scenario.
The value set in SectionName determines which of the Offers screens to display.
It also holds info of the template to be displayed when there is a single offer or offers with parent child relationship. E.g. if there is a single
parent offer, SectionName = "SingleActionInformationPage".
Possible scenarios are: Default, SuccessScenario, FailureScenario, Ineligible, Expired, Inactive.
T2TVActions (Treatment To Treatment Variations Actions)
This decision data holds information of the Button actions i.e. what needs to be done for a button click based on a scenario.
Possible scenarios are: Default, SuccessScenario, FailureScenario, Ineligible, Expired, Inactive.
PM Tool Screens
There are no separate screens for the two main decision data: T2TVAttributes and T2TVActions. Instead data from a combination of
screens in PM Tool is sent to the above mentioned decision data.
Screen: Channel | VODKB-200723-160306.pdf |
e80fefda2093-0 | 466
Below is a screenshot of Channel screen.
1. New channel “Microsite” is created.
2. Possible outcomes are added e.g. “Accepted”.
3. If no subchannel, “Default” value is assigned to the sub channel.
4. Tick, if templates are required for the channel.
5. Tick, if Actions are needed on the template e.g. buttons.
6. Tick, if scenario based templating is needed e.g. change screen templates and content based on scenarios.
7. If Step 6 is checked, scenarios are added e.g. “SuccessScenario”.
Screen: Template Attributes
1. Used to create new template attribute, example - “ExtraLargeImageURL” attribute
Screen: Template
1. New template “Clickid” is created. | VODKB-200723-160306.pdf |
520c5891c213-0 | 467
2. Add Attributes to new template
Later data is added to the template from Treatment To Treatment Variations screen.
Screen: Action Attributes
1. Allows to create action attributes, new attribute is created “RedirectURL”
Screen: Actions
A new action is created from ‘Actions’ screen.
1. New template “ButtonToURLSameWindow” is created.
2. Add Attributes to new template
Data is added to the action from Treatment To Treatment Variations screen. | VODKB-200723-160306.pdf |
d440c78ee279-0 | 468
Screen: TreatmentToTreatmentVariations
For a specific scenario e.g. “Default”, attributes and actions for the template can be configured in PM Tool.
DefaultScenario > Templates section: | VODKB-200723-160306.pdf |
b3d4ef06a8b1-0 | 469
DefaultScenario > Outcomes section:
Default Scenarios page > | VODKB-200723-160306.pdf |
e5f9596bbab8-0 | 470
Default Scenario > Attributes and Actions definition | VODKB-200723-160306.pdf |
3bc88d76cae7-0 | 471
ExtraLargeImageURL (Banner) 343 KB
LargeImageURL (1GB/2GB) 418 KBImageURL Attribute Size
FooterSectionRule App
Header Business/Opti
MediumImageURL Business/Opti
HeaderSectionRule App
BodyHeader Business/Opti
Body Business/Opti
SectionName App
LargeImageURL Business/Opti
ExtraLargeImageURL Business/OptiTemplateAttribute Editable
Button Text Business/OptiTemplateAction Editable | VODKB-200723-160306.pdf |
79e82fd99520-0 | 472
Success Scenario > Attributes definition
Failure Scenario > Attribute definition
RedirectURL Business/Opti
Short Text (Single-Line Datatype) 256
Long Text (Multi-Line Datatype) 4000Attribute Max Length | VODKB-200723-160306.pdf |
f092595f6b54-0 | 473
XLP Logic Components
How the Microsite url, that is sent in the SMS, is formed?
A sample Microsite URL is shown below. It has two parts.
Strategy: SetLandingPageCTA forms the URL and it can be included as a sub-strategy in the main logic while populating the ouput. This
can be done for any functionality, e.g. for Batch, Strategy: PopulateOutputPropertiesForSMSByBatch calls this strategy.
In ‘Treatment to Treatment Variation’ decision data for SMS, configured in PM Tool; property ‘TreatmentDynamicVariable1’ contains the
SMS body text along with a tag [LandingPageCTA], that is replaced in the above strategy with the Mircrosite URL.
Strategy: SetLandingPageCTA: (How the URL is formed and replaces the tag).
1: The first part of the URL configured in AOMConfig is retrieved and saved to attribute MicrositeURL.
.MicrositeURL = D_VFUKFWAOMFWDataAOMConfig[ConfigType:Microsite,ConfigName:OffersURL].ConfigValue
Below screenshot shows where the URL is configured in AOMConfig. | VODKB-200723-160306.pdf |
4f9b274d4762-0 | 474
2: Below function is called and property .Metadatacode is set. It forms the second part of the url.
Function SaveOffersMetadata takes Subscription Id, comma-separated list of clipboard page SR properties, and Page (ClipboardPage) as
input. It then invokes the activity SaveOffersMetadata to store the properties in data set OffersMetadata and returns MetadataId as String
type. E.g.
.Metadatacode = SaveOffersMetadata(.CustomerID,
"pxInteractionID,Channel,OfferName,OfferVariant,TreatmentName,TreatmentVariant,AOMInteractionId", ClipboardPage)
Above underlined, is a comma-separated list of properties that is stored by the function in the data set: OffersMetadata (see next topic).
Then the function returns a code that is set to .Metadatacode. E.g. "71b8ce9403724458bd3ffd03d75e7cd".
Above code is the second part of the URL. When customer clicks on the URL in SMS, this code comes back to Pega and is used to look up
information for the customer + offers from the data set.
3: First and second part of the URL is set to property .LandingPageCTA.
.LandingPageCTA = .MicrositeURL + .Metadatacode
4: Tag [LandingPageCTA] in .TreatmentDynamicVariable1 is replaced with the above property .LandingPageCTA
Now the SMS will have the body text along with the formed URL.
Data set: OffersMetadata
SaveOffersMetadata function/activity saves to this Data set (Decision Data Store) in below format.
Pega Case (for information only for Optimisation team)
Microsite is just a Pega Case. This document mainly concentrates on Fetch Offers and Next Best Content which are the new logic
components for this functionality.
Fetch Offers flow calls: | VODKB-200723-160306.pdf |
4f9b274d4762-1 | components for this functionality.
Fetch Offers flow calls:
Data Flow: IdentifyBestMicrositeTreatments and Strategy: IdentifyBestMicrositeTreatments
Next Best Content flow calls:
Data Flow: GetNextBestContent and Strategy: GetNextBestContent | VODKB-200723-160306.pdf |
7cc81f2707cc-0 | 475
Fetch Offers step in Pega case calls Data flow: IdentifyBestMicrositeTreatments that in turn calls Strategy:
IdentifyBestMicrositeTreatments. The strategy struncture is as below. Strategies mainly for this functionality are highlighted and described in
the list below:
1. IdentifyEligibleTreatmentsforMicrosite: This strategy is common for all execution modes. For Microsite functionality, it gets treatments
specifically for Microsite. During this logic, while getting the offers, offer expiry is checked. How offer expiry works is explained in a
section below.
2. IdentifyBestTreatmentforSubscription: This strategy is common for all execution modes. For Microsite functionality, it does the logic of
parent child offer bundling.
3. IdentifyTreatmentVariations: This strategy is common for all execution modes. For Microsite functionality, it gets only the treatment
variations for microsite treatments.
4. PopulateOutputPropertiesForMicrosite - Explained below:
5. SetIHPropertiesForAllChannels: This strategy is common for all execution modes. For Microsite functionality, it set the common +
microsite specific Interaction History properties.
6. GetInactiveMicrositeTreatment - Call decision data: T2TVAttributes and T2TVActions and get records for Scenario = Inactive. Set
property .ErrorMessage with the value from AOMBusinessConfig (screenshot below) | VODKB-200723-160306.pdf |
307b85cbc650-0 | 476
7. GetExpiredMicrositeTreatment - Call decision data: T2TVAttributes and T2TVActions and get records for Scenario = Expired. Also check
offer expiry. Set property .ErrorMessage with the value from AOMBusinessConfig. How offer expiry works is explained in a section
below.
8. GetIneligibleMicrositeTreatment - Call decision data: T2TVAttributes and T2TVActions and get records for Scenario = Ineligible. Set
property .ErrorMessage with the value from AOMBusinessConfig.
Strategy: PopulateOutputPropertiesForMicrosite
1. Route for Offers with Parent Child combination.
2. 2a and 2b: Route for Offers as Parent only without any children.
3. Set .ResponseType = Action for this route and get data from T2TVAttributes decision data. ResponseType property is used by the App
layer to recognize the relevant data.
4. Set .ResponseType = Action for this route and get data from T2TVActions decision data.
5. Import data from decision data: T2TVAttributes.
6. Import data from decision data: T2TVActions.
7. Join with the primary route and get “TemplateDetails”.
8. Join with the primary route and get “ActionTemplateId”, “ActionType”, “ActionDetail”, “Outcome”. | VODKB-200723-160306.pdf |
00f124d6bbfe-0 | 477
Next Best Content
Data flow and Strategy: Next Best Content
From Microsite landing page, where offers are dispalyed, if customer clicks on ‘Buy Now’, CSO (Create Sales Order) call is made.
Depending on the success of failure of CSO call, the next best content/screen is displayed to customer.
For the Offer in context, strategy gets all the relevant offer variations, treatment and treatment variations assigns attributes and actions from
decision data: T2TVAttributes and T2TVActions.
Similar kind of logic, described above in Strategy: PopulateOutputPropertiesForMicrosite.
How offer expiry works?
Offer expiry logic is present in below two strategy.
Strategy 1: SetExpiryPeriod
This check is done for all execution modes and all channels. While getting eligible offers from proposition data, this strategy is called as a
sub-strategy inside IdentifyEligibleOffers.
Fallow Period
It introduces the concept of Fallow period for offer expiry date. Fallow period for expired offers can be configured against offers in the PM
tool. If the number of days since an expiry date is less than the fallow period then an offer should be unavailable. Expired error status for
microsite should be based on the fallow period status.
Two attributes present in PM Tool Offers screen for this functionality are:
FallowPeriodForOfferExpiry - values e.g. 0, 3, 4 etc. | VODKB-200723-160306.pdf |
0ceacb61cf16-0 | 478
FallowPeriodForOfferExpiryInterval - values e.g. Years, Months, Days.
Fallow period logic is applied against the latest expiry date for the offer from Interaction History.
In PM Tool it is configured in Offers screen, as in the screenshot below.
1. Offer Expiry Interval in Days, Months or Years or a specific date.
2. If the offer has expired, make the offer unavailable for specified number of days.
3. Fallow period interval in Days, Months or Years or a specific date or Indefinite.
4. Number of days for the fallow period.
Strategy 2: OfferExpiry
This check is done for Microsite channel and is called as a sub-strategy inside strategy: IdentifyBestMicrositeTreatments.
For the offer in the request context, get latest expiry date from Interaction History and check against current date.
If offer expiry date is in future, let the logic flow to the next step.
If offer expiry date is in past, set error message configured in AOMBusinessConfig.
Capture Response in Interaction History
At various points during the user journey, customer interactions are captured in Interaction History.
Some scenarios are mentioned below: | VODKB-200723-160306.pdf |
80e2785207f9-0 | 479
SMS sent to customer after Batch process Pending - if sent via Pega Marketing
Selected - if sent via TIL service
Customer clicks on the Microsite link in the SMS Clicked
Microsite is displayed with Offers Shown - for each offer
Customer clicks “Buy Now” button for an offer Accepted
CSO - Create Sales Order failure FailureScenario Outcome in IH | VODKB-200723-160306.pdf |
9ce4dfe4bedb-0 | 480
XLP Error Scenarios
Currently, all error scenarios display the page as below. Content in the page is served by AOMConfig and not from PM Tool at the moment.
Error is written to aom_error database table.
Content shown in the above error page is configured in AOMConfig and is managed at the App layer.
ConfigType: ExceptionTemplateAttributes
ConfigName: OffersMicrosite
The ConfigValue in the above screenshot is like below. (Original image links are removed for the purpose of documentation).
{
"PageTitle": "Oops",
"Header": "Sorry, that didn't work",
"Body": "We're sorry, we weren't able to process your request. Please click below to check out your options.",There is a scope in future releases to have customized templates/screens for each error scenario. | VODKB-200723-160306.pdf |
67d2584f1e04-0 | 481
"ExtraLargeImageURL": "ImageUrl1Path/image1.jpg"
"LargeImageURL": "ImageUrl2Path/image2.jpg"
"MediumImageURL": "ImageUrl3Path/image3.jpg"
"ButtonText": "Explore My Options",
"ButtonURL": "Url to which button click should take the user"
}
Error Scenario 1
Once customer clicks on the URL in SMS, AOM tries to look up customer and offer information by using the Metadatacode present in the
URL. If found, pass to the next stage. However, if customer details cannot be found against the URL details, error screen is displayed.
Error Scenario 2
If Metadatacode look up is successful, there are additional validations for GPSL. If call to GPSL fails, error screen is displayed.
GPSL = Get Processed Service List, is a SOAP service exposed by Vodafone TIL (Tibco Interface Layer) which returns the Offers and
Product details for a given Service Number/MSISDN.
Error Scenario 3
On the URL click and other customer activities on the Microsite, Pega needs to write reponses to Interaction History as part of Capture
Response process. If the process fails, error screen is displayed. One possible scenario could be Interaction id mismatch for a sms sent
response and sms clicked response.
Error Scenario 4
Customer clicks on the URL, but the customer data is not present in Subscription table, it corresponds to a failure and error screen is
displayed.
Error Scenario 5
On ‘Buy Now’ button click on Microsite, if CSO = Create Sales Order process fails, error screen is displayed.
Error Scenario 6
Display error screen if the offer has expired. | VODKB-200723-160306.pdf |
81e7ca5b504d-0 | 482
XLP App layer
This page describes the Landing Pages displayed in the Offers Case and how the pages are populated with content. The attributes used to
display the pages are detailed.
In the event of Landing Pages not displaying as expected, please check the relevant attribute(s) on the page and the value(s) returned in
Decision Data.
A. Exception Handling Error Page
This page displays for all flow exceptions and errors in the Offers Case. This page is not offer specific but the content of this page can be
configured as described below.
This page is displayed in case of landing page offer is either Inactive, Expired or Ineligible.
All attributes are set from the following record in AOMConfig (shown here with example ConfigValue):
ConfigType: ExceptionTemplateAttributes
ConfigName: OffersMicrosite
ConfigValue:
{
"PageTitle": "Oops",
"Header": "Sorry, that didn't work",
"Body": "We're sorry, we weren't able to process your request. Please click below to check out your options",
"ExtraLargeImageURL": "url",
"LargeImageURL": "url",
"MediumImageURL": "url",
"ButtonText": "Explore My Options",
"ButtonURL": "url"
}
Troubleshooting
Text content not displaying as expected
(Header or Body)Check AOMConfig entry for individual
attributes - Header & Body
Button text not displaying as expected Check AOMConfig entry - ButtonText
attribute
Button does not redirect to expected url Check AOMConfig entry - ButtonURL
attribute Problem Check Notes | VODKB-200723-160306.pdf |
212b7c6f69df-0 | 483
B. Offers pages
The Offers Landing Pages content is populated from attributes that are set in Decision Data - T2TVAttributes and T2TVActions. These are
returned from logic data flows in the Offers Case.
The attributes used to display each screen are detailed below. If any screens do not display as expected, the attribute values should be
checked first.
The value set in T2TVAttributes - TreatmentAttributes.SectionName determines which of the Offers screens to display.
The pages below are used to display the offers on Landing page - as Default scenario (when the offer is loaded on Landing Page)
as well as CSO Success/Failure Scenarios.
B1. Parent Single Action page
TreatmentAttributes.SectionName = "SingleActionInformationPage" (set in T2TVAttributes)
Page content is populated from the following name/value properties in TreatmentAttributes set in T2TVAttributes.Background image not displaying as
expectedCheck AOMConfig entries -
ExtraLargeImageURL, LargeImageURL,
MediumImageURLThe different size images are used
depending on the screen size.
HeaderSectionRule Header shown with Vodafone logo. This should be a valid Section rule name.
Existing Section name with VF logo should
be H e a d e r A l i g n R i g h t
Header Hello Emma. Here’s a data offer just for you. Text
Body It’s great to see you’ve been making the most of your data
allowance…………..Text
ExtraLargeImageURL Background image shown URL of image.
LargeImageURL Background image when screen size is reduced to large URL of image.
MediumImageURL Background image when screen size is reduced to medium URL of image.
FooterSectionRule Footer shown with ‘Terms & Conditions’ | ‘Privacy policy’ links | VODKB-200723-160306.pdf |
212b7c6f69df-1 | FooterSectionRule Footer shown with ‘Terms & Conditions’ | ‘Privacy policy’ links
and @ 2022 Vodafone text.This should be a valid Section rule name.
Existing Section name should be TreatmentAttributes
attributeExample in screen above Notes | VODKB-200723-160306.pdf |
d89fbc4b96f0-0 | 484
Action buttons are populated from T2TVActions Decision Data attributes - ActionTemplateType & ActionTemplateDetail.
There are currently 2 types of Action button - Product Add On button and Redirect button.
The above pattern of template is used for Default scenario (single offer) as well as CSO Failure scenario.
B2. Parent with Child page
TreatmentAttributes.SectionName = "ParentWithCardChildren" (set in T2TVAttributes)
Page content is populated from the following name/value properties in TreatmentAttributes set in T2TVAttributes.F o o t e r D e f a u l t .
Product Add
OnProductAddOn "[{"Name": "ButtonText", "Value": "<<Set to
button label>>"}]"eg. "[{"Name": "ButtonText", "Value": "Buy Now"}]"
Redirect RedirectURL "[{"Name": "ButtonText", "Value": "<<Set to
button label>>"}, {"Name": "RedirectURL",
"Value": "<<Set to url to redirect to>>"}]"eg. "[{"Name": "ButtonText", "Value": "Explore My
Options"}, {"Name": "RedirectURL", "Value": "url"}]"Button type ActionTemplate
TypeActionTemplateDetail attributes Notes
HeaderSectionRule Header shown with Vodafone logo. This should be a valid Section rule name.
Existing Section name with VF logo should
be H e a d e r A l i g n R i g h t
Header Hello Emma. Here’s a data offer just for you. Text
Body It’s great to see you’ve been making the most of your data
allowance…………..TextTreatmentAttributes
attributeExample in screen above Notes | VODKB-200723-160306.pdf |
f214d67fb435-0 | 485
For each Child, the card sections on the page are populated from the following name/value properties in the Child’s TreatmentAttributes :
For this page, there are no Action buttons for the Parent section. Action buttons can be defined for the Child card sections.
Action buttons are populated from T2TVActions Decision Data attributes - ActionTemplateType & ActionTemplateDetail.
There are currently 2 types of Action button - Product Add On button and Redirect button.
The above pattern of template is used for Default scenario (Multiple offers - Parent & Child).ExtraLargeImageURL Background image shown URL of image.
LargeImageURL Background image when screen size is reduced to large URL of image.
MediumImageURL Background image when screen size is reduced to medium URL of image.
BodyHeader Get your extra Text
FooterSectionRule Footer shown with ‘Terms & Conditions’ | ‘Privacy policy’ links
and @ 2022 Vodafone text.This should be a valid Section rule name.
Existing Section name should be
F o o t e r D e f a u l t .
ImageSashText 50% discount Text
Header 1GB of data for only £XX a month Text
Body Your Data Extra will automatically renew each month…… Text
LargeImageURL Child card image - For 1GB and For 2GB URL of image.
MediumImageURL Child card image for medium screen size - For 1GB and For
2GBURL of image.
Footer This Data Extra will be added to mobile number…………… TextTreatmentAttributes
attributeExample in screen above Notes
Product Add
OnProductAddOn "[{"Name": "ButtonText", "Value": "<<Set to
button label>>"}]"eg. "[{"Name": "ButtonText", "Value": "Buy Now"}]"
Redirect RedirectURL "[{"Name": "ButtonText", "Value": "<<Set to | VODKB-200723-160306.pdf |
f214d67fb435-1 | Redirect RedirectURL "[{"Name": "ButtonText", "Value": "<<Set to
button label>>"}, {"Name": "RedirectURL",
"Value": "<<Set to url to redirect to>>"}]"eg. "[{"Name": "ButtonText", "Value": "Explore My
Options"}, {"Name": "RedirectURL", "Value": "url"}]"Button type ActionTemplate
TypeActionTemplateDetail attributes Notes | VODKB-200723-160306.pdf |
b2cf56f2b442-0 | 486 | VODKB-200723-160306.pdf |
922fdd3fc3f7-0 | 487
B3. No Action Information Page | VODKB-200723-160306.pdf |
1f3a3615498f-0 | 488
TreatmentAttributes.SectionName = "NoActionInformationPage" (set in T2TVAttributes)
Page content is populated from the following name/value properties in TreatmentAttributes set in T2TVAttributes.
There are no Action buttons for this page.
The above pattern of template is used for Default scenario (Single offer with no CTA) as well as CSO Success scenario.
HeaderSectionRule Header shown with Vodafone logo. This should be a valid Section rule name.
Existing Section name with VF logo should
be H e a d e r A l i g n R i g h t
Header Hello Emma. Here’s a data offer just for you. Text
Body It’s great to see you’ve been making the most of your data
allowance…………..Text
ExtraLargeImageURL Background image shown URL of image.
LargeImageURL Background image when screen size is reduced to large URL of image.
MediumImageURL Background image when screen size is reduced to medium URL of image.
FooterSectionRule Footer shown with ‘Terms & Conditions’ | ‘Privacy policy’ links
and @ 2022 Vodafone text.This should be a valid Section rule name.
Existing Section name should be
F o o t e r D e f a u l t .TreatmentAttributes
attributeExample in screen above Notes | VODKB-200723-160306.pdf |
d10a0bea58a1-0 | 489
2nd Line Private Pricing
Objective
Digital platform calls AOM’s 2nd line private pricing functionality via API calls, to get a list of prioritised tariff plans, associated percentage
discounts along with associated offers for a customer with an existing primary line product.
This functionality is a part of existing APIs: GetNBA and GetProductList.
Business Purpose = CrossSell
Currently implemented only for CrossSell but has the scope to be extended to other business purposes.
Channel in the API request = Web
OrderType in the API request = In Life Sales
This is passed in Get Product List API request to identify that the request is related to a 2nd line journey.
For GetNBA, it is hard coded as ‘In Life Sales’ in the logic.
Test Cell Management is new in 2nd Line PP, that is described in a separate section in the later part of this documentation.
GetNBA API:
2nd Line PP is called in the GetNBA logic flow when the customer's intent is: Buy-Second-Line.
GetNBA request can either come from the 'Upgrades & Offers' page or the 'Options to Buy (OTB)' popup on the Digital platform.
Logic distinguishes between these two sub-channels and determines which offers, treatment and templates to use.
So SubChannel under the Web channel are:
'Purchase' - for 'Options to Buy (OTB)' popup
'UpgradesAndOffers' - for 'Upgrades & Offers' page
As per current business requirement, only the Discounts (for tariff) need to be assigned template attributes and actions.
Sample GetNBA API request with SubChannel = Purchase and PrimaryContext = Options_to_Buy
{
Identifier: {
Account: {
AccountNumber: "31521130702",
Status: "Existing",
Type: "Consumer" | VODKB-200723-160306.pdf |
d10a0bea58a1-1 | AccountNumber: "31521130702",
Status: "Existing",
Type: "Consumer"
},
ServiceNumber: "447920130702"
},
RequestorDetail: {
Channel: "Web",
SubChannel: "Purchase"
},
Context: {
PrimaryContext: "Options_to_Buy",
NoOfActions: 5, | VODKB-200723-160306.pdf |
8a3262c5cba6-0 | 490
Detail: []
}
}
Sample GetNBA API request with SubChannel = UpgradesAndOffers and PrimaryContext = Upgrades_and_Offers
{
Identifier: {
Account: {
AccountNumber: "31521130702",
Status: "Existing",
Type: "Consumer"
},
ServiceNumber: "447920130702"
},
RequestorDetail: {
Channel: "Web",
SubChannel: "UpgradesAndOffers"
},
Context: {
PrimaryContext: "Upgrades_and_Offers",
NoOfActions: 5,
Detail: []
}
}
GetProductList API:
Get Product List gets a list of available tariffs and discounts. There is no Business requirement for templates here.
Sample GetProductList API request with Tariff in Line item (basket)
{
"OwnerAccountNumber": "169806809",
"SubscriptionId": "-127975494",
"AgentId": "53243463",
"Division": "Webchat Saves",
"Channel": "Web",
"SubChannel": "UpgradesAndOffers",
"OrderType": "In Life Sales",
"CaseId": "CaseId",
"RecommendationId": "RecommendationId",
"ProductType": "Tariff",
"LoanEligibilityStatus": "Eligible",
"LineItems": [
{
"ProductId": "112168",
"ProductType": "Tariff"
}
]
}
Sample GetProductList API request with Handset in Line item (basket) | VODKB-200723-160306.pdf |
970923ca95e4-0 | 491
{
"OwnerAccountNumber": "169806809",
"SubscriptionId": "-127975494",
"AgentId": "53243463",
"Division": "Webchat Saves",
"Channel": "Web",
"SubChannel": "UpgradesAndOffers",
"OrderType": "In Life Sales",
"CaseId": "CaseId",
"RecommendationId": "RecommendationId",
"ProductType": "Tariff",
"LoanEligibilityStatus": "Eligible",
"LineItems": [
{
"ProductId": "204523",
"ProductType": "Handset"
}
For both the APIs, response is sent to Digital, and Pega writes records to Interaction History and Interaction History reporting.
Error Scenarios
When the APIs are called, if the MSISDN is not recognised by AOM then an error should be returned.
Likewise, if the supplied SKU is not recognised against any non-SIMO plan, then an error should be returned. | VODKB-200723-160306.pdf |
bc9e2c94508e-0 | 492
Propositions and PM Tool screens for 2nd Line PP
At the time of preparing this document, below offers were given by Business as part of 2nd Line private pricing functionality.
PM Tool Offer screen to configure offers
All offers have CustomerSegment = ConsumerPostpay and BusinessSegment = Consumer.
Two new fields are added to the offer screen: TariffType and TestGroup (described later in Test Cell Management section of this document).
PM tool O f f e r screen screenshot.AddMobileWithHand
setCrossSell Batch,GetNBA Loan Handset Tariff
AddSIMO CrossSell Batch,GetNBA CBU SIMOnly Tariff
AddTablet CrossSell Batch,GetNBA Loan Tablet Tariff
AddDataSIMO CrossSell GetNBA CBU DataSIMOnly Tariff
AddDiscount CrossSell GetNBA DiscountOffer Name Business Purpose OfferExecutionMod
eTariff Segment TariffType ProductRecommen
dation Type | VODKB-200723-160306.pdf |
8fc22f95901e-0 | 493
All offers have offer Variant = OfferVariantDefault.
PM Tool Treatment screen to configure treatments
All treatments have treatment variant = TreatmentVariantDefault.
PM Tool Parent Child Treatments screen to configure Parent Child offer relationship.
PM Tool SubChannel screen to configure two new sub channels
There are two subchannels ‘Upgrades and Offers' and ‘Purchase’
These are from the 'Upgrades & Offers' page or the 'Options to Buy (OTB)' popup.
There is a screen for Test Cell Management described in the Test Cell Management section in later part of this document.AddMobileWithHandset_Web AddMobileWithHandset Web
AddSIMO_Web AddSIMO Web
AddTablet_Web AddTablet Web
AddDataSIMO_Web AddDataSIMO Web
AddDiscount_Web AddDiscount WebTreatment Name Associated Offer Name Applicable Channel
AddMobileWithHandset_Web AddDiscount_Web
AddSIMO_Web AddDiscount_Web
AddTablet_Web AddDiscount_Web
AddDataSIMO_Web AddDiscount_Web
AddMifi_Web AddDiscount_WebBundleParentTreatment BundleChildTreatment | VODKB-200723-160306.pdf |
8add3b006463-0 | 494
Get Product List Logic
Strategy: GetProductList is the main strategy.
It calls Sub Strategy GetProductListForUpgrade and GetProductListForAdditionalLine that contains the existing GetProductList logic for
Upgrades and the 2nd Line Pricing logic respectively.
The switch component chooses the relevant route based on the .OrderType from API request context.
Call Strategy: GetProductListForUpgrade if .OrderType is "Upgrade" or "Flexi Upgrade"
Call Strategy: GetProductListForAdditionalLine of .OrderType is "In Life Sales" or "New Acquisition"
Set .ErrorMessage = "Invalid Order Type" otherwise
Logic relevant to 2nd line private pricing functionality
Strategy: GetProductListForAdditionalLine
Brief description of the logic
1] GetAllTariffs : All the available tariffs are called here. | VODKB-200723-160306.pdf |
6be8bf38b4c8-0 | 495
2] ManageHaloServiceType & EvaluateInterestedServiceType: To find the service type suitable for a customer.
3] GetEligibleTariffsForSKU : Gets tariffs which are compatible with the product the customer holds.
4] Check Additional Line Context:
Switch based on the context data from EvaluateInterestedServiceType as shown below:
5] Invalid Additional Line Context: "Invalid Additional Line Context" error message set.
6] Ineligible plans are filtered out and the TestCellManagement properties are joined with the eligible plans.
7] TestCellManagement : Unique propositions are input and TestGroup eligibility is checked so the correct TestGroup and TestCells is
assigned to each positions for a customer.
8] IdentifyDiscountPerTariff: Identify discount per tariffs by Map Test Group Details.
9] SecondLineDiscountCompatibility: To check if the discount is compatible with the tariff by using data page: D_DiscountsForTariff.
10] PrioritizePlans: To decide which plan should be given priority.
11] ApplyBundlingForAdditionalLine: It Matches the Parent & child Treatments and sets the Parent.
12] PrioritiseDiscounts: To decide which Discount should be given priority.
13] PopulateOutputPropertiesForAdditionalLine: To create relevant properties to be sent in the API response.
14] SetIHPropertiesForAllChannels: To populate required IH fields for all channels while writing them to Interaction History - maps
properties for Interaction History and for any properties with no value are set to default. | VODKB-200723-160306.pdf |
6be8bf38b4c8-1 | properties for Interaction History and for any properties with no value are set to default.
15] Make Decision: Confirms if error message is chosen before providing results based on CheckAdditionalLineContext as shown below. GetEligibleTariffsForSKU EvaluateInterestedServiceType.HasSKU
ManageHaloServiceType !EvaluateInterestedServiceType.HasSKU
Invalid Additional Line Context Otherwise Select Component Condition | VODKB-200723-160306.pdf |
890a3832edf0-0 | 496
Invalid Additional Line Context CheckAdditionalLineContext.ErrorMessage!=""
SetIHPropertiesForAllChannels OtherwiswStrategy Component Condition | VODKB-200723-160306.pdf |
0c493e9be8ae-0 | 497
GetNBA Logic
In the existing GetNBA logic, 2nd line private pricing functionality is called in the below strategy for Intent = "Buy-Second-Line".
Strategy: PopulateOutputPropertiesForGetNBA
The strategy is called from PopulateOutputPropertiesForWeb when Execution Mode is GetNBA
There are two paths, Additional Line and Not Additional Line
2nd Line Pricing follows the Additional Line path:
Additional Line Filter
Get Max Discount - calls IdentifyMaxDiscountForTariffType
PopulateOutputPropetiesForGetNBAPrivatePricing
Results
Strategy - IdentifyMaxDiscountForTariffType
From external input, Discounts and Tariffs come into the strategy.
Strategy splits into Tariff and Discount
For tariff path, call Strategy: GetAllTariffs, to get the duration of the tariff.
Discount path
Discounts are mapped to relevant tariffs to get the duration and then are split into 12 or 24 months plans. Other duration tariff + discount
plans flow directly to the results component.
From here, logic is similar to Get Product List logic, described in the previous part of this document.
Refer to section: Get Product List Logic, then point [7] Strategy: IdentifyDiscountPerTariff. | VODKB-200723-160306.pdf |
c7d6d05bcf70-0 | 498
Test cell management is used here as well.
The only part that is different in GetNBA 2nd line private pricing logic is Legal Compliance, described below.
Strategy: GetLegalComplianceTariffs
There is a legal requirement by Business to ensure that when it is communicated "up to X% off", at least 15% of the eligible tariffs
compatible with an offer will receive the advertised X% discount level.
The discount matrix will be configured so the high/medium/low bandings will always be set so that the "high" discount level will always be
compliant. GetLegalComplianceTariffs ensures this and mitigates the risk of human error.
Tariffs Compliance with Legal Requirement: .Count of Tariffs >= LegalRequirement.LegalCompliance
LegalCompliance value is configured via PM Tool screen: Business Config and is stored in the data type: AOMBusinessConfig as follows:
To populate output properties and template attributes and actions, below strategy is called.
Strategy: PopulateOutputPropetiesForGetNBAPrivatePricing
GetNBA outputs are inf the form of offers/propositions e.g. parent could be the Tariff offer and discount offer is child.
In the logic flow, screenshot below, Parent Offer for Tariff flows throught the top path.
Below that is the Child offer route for Discount. In API response discounts are present in the Detail section.
Finally Disounts are joined with Tariffs. | VODKB-200723-160306.pdf |
07482b1c8bde-0 | 499 | VODKB-200723-160306.pdf |
e99159e11662-0 | 500
OPTI KT Test Cell Management in 2nd Line Private Pricing
Test Cell Management Screen
Configure TestGroups , Enable / Disable, TestGroup Expiry and Test Cell Splits in Test Cell Management Screen
Data configured in this screen is pushed into two decision datas :TestGroups and Test Cells
Decision Data: TestCells: Data configured in PM Tool. Sample values below.
PM Tool Offer screen: There is a drop down to assign a Test Group, as shown below.
AdditionalLineDiscount Matrix:
Note: There is no PM screen for this decision data. It should be manually uploaded in system.
Example:
Random 4 Split A Random 4 Split A1 1 33
Random 4 Split A Random 4 Split A2 34 66
Random 4 Split A Random 4 Split A3 67 100CellGroup CellCode InitialValue FinalValue | VODKB-200723-160306.pdf |
b7e1b6d347c9-0 | 501 | VODKB-200723-160306.pdf |
f745527b0a14-0 | 502
eCare
Introduction
eCare is a new channel in NBA functionality. AOM returns offers via eCare channel in multiple containers within the Account Dashboard. A
GetNBA request will come from the account dashboard, so ‘Dashboard’ is the sub-channel in the request.
Containers are the Divisions. The new channel, sub-channel and divisions is configured via PM Tool, explained in the later part of this
document.
Business Purpose = any business purpose can be used as per business requirement
Execution mode = GetNBA
SubChannel = Dashboard
Sample GetNBA API request with SubChannel = Dashboard
{
"Identifier": {
"Account": {
"AccountNumber": "7001179200",
"Status": "Existing",
"Type": "Consumer"
},
"ServiceNumber": "447879100510"
},
"RequestorDetail": {
"Channel": "eCare",
"SubChannel": "Dashboard",
"Agent":{
"Department":"High-Value Retention"
}
},
"Context": {
"PrimaryContext": "Offers",
"NoOfActions": 10,
"Detail": [{
"Name":"CONTACT_ROLE"
,"Value":"L0-Owner"
}]
}
}
For Channel = eCare in GetNBA API request, the main strategy for eCare functionality is:
IdentifyBesteCareTreatmentsForSubscription.
The API request returns:
A List of eCare eligible NBA offers (treatments) and their priority order.
A sample GetNBA API response for eCare request is below: | VODKB-200723-160306.pdf |
1ac41a5f58b9-0 | 503
{
"InteractionId": -1552726564088101344,
"ActionList": [{
"Propensity": 0.0,
"OfferVariant": "FlexUpgrade",
"Priority": 8,
"Channel": "eCare",
"SubChannel": "Dashboard",
"OfferId": "VFO0035",
"OfferName": "UpgradeMobileToHandset",
"TreatmentId": "VFO0035-TC001",
"OfferDescription": "",
"TreatmentVariant": "OutboundCampaignFollowUp_NonOwner",
"Detail": [{
"Value": "ECareUpgrades",
"Name": "container"
},
{
"Value": "Here is an eCare upgrades offer",
"Name": "offer"
},
{
"Value": "CTA text",
"Name": "CTA"
},
{
"Value": "eCare",
"Name": "journey"
},
{
"Value": "Copy text",
"Name": "Copy"
},
{
"Value": "eCare upgrades offer",
"Name": "sash"
},
{
"Value":
"https://assets.vodafone.co.uk/cs/groups/public/documents/images/mv10_red_entertainment_image.png",
"Name": "imageURL"
},
{
"Value": "Get that new phone feeling with an upgrade today. Speak to your main Account Holder if you would
like to upgrade your plan",
"Name": "body"
},
{
"Value": "https://tcc8-www.vodafone.co.uk/upgrade-and-offers",
"Name": "CTAURL"
}, | VODKB-200723-160306.pdf |
dad9fa49f994-0 | 504
{
"Value": "It's upgrade time!",
"Name": "title"
}
],
"TreatmentName": "UpgradeMobileToHandset_eCare"
},
{
"Propensity": 0.25,
"Priority": 5,
"OfferVariant": "OfferVariantDefault",
"Channel": "eCare",
"SubChannel": "Dashboard",
"OfferId": "XSL010",
"OfferName": "AddTablet",
"Item": [{
"AdditionalNotes": "",
"ProductType": "Additional Service",
"ProductId": "107414",
"ProductDescription": "Other"
}],
"TreatmentId": "XSL010-TC001",
"OfferDescription": "",
"TreatmentVariant": "TreatmentVariantDefault_NonOwner",
"Detail": [{
"Value": "Here is an eCare extras tablet offer just for you",
"Name": "offer"
},
{
"Value": "ECareOffersForYou",
"Name": "container"
},
{
"Value": "CTA text",
"Name": "CTA"
},
{
"Value": "eCare",
"Name": "journey"
},
{
"Value": "Copy text",
"Name": "Copy"
},
{
"Value": "eCare extras tablet offer just for you",
"Name": "sash"
},
{
"Value": "Vodafone – Our Best Ever Network | Now With 5G
"Name": "imageURL" | VODKB-200723-160306.pdf |
1bb26eb81838-0 | 505
},
{
"Value": "https://www.vodafone.co.uk/",
"Name": "CTAURL"
},
{
"Value": "Save £311 on a Samsung Tab A8",
"Name": "body"
},
{
"Value": "Extra 15% discount for you",
"Name": "title"
}
],
"TreatmentName": "AddTablet_eCare"
},
eCare provide responses to AOM to indicate whether the offer presented on the account dashboard was 'shown' and how the customer
responded to the offer.
Shown: when an offer was 'shown' to a customer
Clicked: a customer click on the relevant 'accept' CTA
Dismissed: A customer has clicked on the relevant 'decline' CTA button
Error Scenarios
If Max Offers check is failed as the MaxOffers for all the Divisions are set to 0, then ““Error in GetNextBestActions: Business Logic Error:
MaxOffers Check Failed” error is returned.
Similarly if Min Offers check is failed: “Error in GetNextBestActions: Business Logic Error: MinOffers Check Failed”Selected Offer is returned to Channel by AOM GetNBA
Shown Offer is presented on eCare channel SetNBAResponse
Clicked Customer has clicked on Accept button on
eCareSetNBAResponse
Dismissed Customer has rejected the offer on eCare SetNBAResponseResponse/Outcome Description API | VODKB-200723-160306.pdf |
739b9f73e4da-0 | 506
Propositions and PM Tool screens for eCare
Offers and Treatments are configured by PM Tool: “Offer” and “Treatment” screen respectively.
offer and treatment names look like below. More details present in Offer Catalogue.
All offers have,
OfferVariant,TreatmentVariant
Channel Screen: New channel ‘eCare’ is configured.
SubChannel Screen: New sub channel ‘Dashboard’ is configured along with Divisions.AddInternationalMinutes eCare AddInternationalMinutes_eCare GetNBA
AddMobileSIMO eCare AddMobileSIMO_eCare GetNBA
AddMobilewithhandset eCare AddMobileWithHandset_eCare GetNBA
AddSmartwatch eCare AddSmartwatch_eCare GetNBAOffer Name Channel Treatment OfferExecutionMode
eCare Dashboard OffersForYouChannel SubChannel Division | VODKB-200723-160306.pdf |
9e075444c48d-0 | 507
Treatment Screen: The new channel, sub-channel, and division is associated with a treatment from the PM Tool ‘Treatment’ screen as
below:
Offer Decision Mix Screen
Max and Min value for offers required for the decision mix is configured in this screen. The decision mix logic in eCare is described in the
later part of this document.
Template Screen
eCare template is created and template attributes are assigned.Extra
NudgeBar4
NudgeBar5 | VODKB-200723-160306.pdf |
4b398a5762a6-0 | 508
Actions Screen
Two button actions are created. One for Click/Accept, one for Dismiss/Reject namely:
eCareAcceptAction
eCareDismissAction
Treatment To Treatment Variations Screen | VODKB-200723-160306.pdf |
ff08fff39569-0 | 509
The above creates a template and actions are assigned to each treatment to treatment variation.
Template assignment
Action assignment | VODKB-200723-160306.pdf |
88a7dbe9a7b6-0 | 510 | VODKB-200723-160306.pdf |
03f71d6d5aa2-0 | 511
eCare Logic
The primary strategy structure and flow for eCare is on the same lines as the GetNBA logic.
Main Strategy: IdentifyBesteCareTreatmentsForSubscription, called from GetNBA when Context(Channel) = "eCare"
Brief description of the strategy components
1] Strategy: IdentifyEligibleeCareTreatments
Get offers, offer variation with treatment for eCare.
2] Strategy: IdentifyTreatmentSubChannel
eCare offers pass through IdentifyTreatmentSubChannelForGetNBA where TreatmentToSubChannels Decision Data is imported. See PM
tool screens. The division is one level below the sub-channel. The division is the area of the dashboard where the offer is displayed. This
strategy checks if.SubChannel from Context =.TargetSubChannel from the decision data and passes those records.
3] Strategy: IdentifyBestTreatmentforSubscription
eCare treatments pass through strategy: IdentifyBestTreatmentForeCareOnGetNBA (see next page). The decision mix logic is present in
this strategy.
4] Strategy: IdentifyTreatmentVariations
The common strategy which finds eligible Treatment Variations.
5] Strategy: PopulateControlGroupPercentage
Populates Offer and Treatment level control group percentages.
6] Strategy: SelectBetweenOfferORTreatmentPotentialControlSplit
Passes through ApplyPotentialControlSplit or ApplyPotentialControlSplitAtTreatmentLevel depending on if.ControlGroupLevel="Offer" or
"Treatment"
7] Strategy PopulateOutputPropertiesForeCare
When .PotentialControlFlag="Target", strategy: PopulateOutputPropertiesForGetNBA is called to create relevant properties to be sent in
the API response. | VODKB-200723-160306.pdf |
8117d7137b81-0 | 512
Strategy: SeteCareTokens and strategy: PopulateCareOutputProperties currently have empty set properties available if the scope is
extended.
8] Strategy: SetIHPropertiesForAllChannels
Populate required IH fields for all channels while writing them to Interaction History. Maps properties for Interaction History and properties
with no value are set to default.
eCare-specific values are set for:
.pyDirection = "Inbound"
.pyOutcome = "Selected"
.InControlGroup = @if(.PotentialControlFlag="Target","N","Y")
9] Switch and Error messages
ErrorMessage - MinOffers Check Failed
Sets ErrorMessage = "MinOffers Check Failed"IdentifyBestTreatmentforSubscription.pyName=""
ErrorMessage - No Decision
Sets .ErrorMessage = "No Decision"SetIHPropertiesForAllChannels.pyName=""
SetIHPropertiesForAllChannels OtherwiseSelect Component Condition | VODKB-200723-160306.pdf |
d82e09d75882-0 | 513
eCare Decision Mix Logic
Offer Decision Mix logic is used to limit the maximum and minimum offers that can pass through a sub-channel and a Division.
The logic is present in Strategy: IdentifyBestTreatmentForeCareOnGetNBA and ApplyDecisionMixAtDivisionLevel.
Business requirements for Decision Mix Logic
Data required for the logic is present in Decision Data: OfferDecisionMix. A sample data is in the table below.
From the above decision data entries, if there is no value for Division (e.g. first row), it means the decision mix is applied at the
SubChannel level. If there are entries for Division, it means the decision mix is applied at the division level.
While setting up MaxOffers at the relevant Division level, only one of the Division MaxOffers can be set up as Unlimited (value = -1).
MaxOffers value for such Division is derived as:
Value of MaxOffers at SubChannel level (minus) Sum of MaxOffers value of all Divisions (non Unlimited) selected treatments.
If Division level MaxOffers is configured, the relevant SubChannel level MaxOffers cannot be marked as Unlimited.
Validation of Max Offers: In the above example, MaxOffers = 1 is set for Division NudgeBar2. That means not more than 1 offer can be
presented for this Division.
Validation of Min Offers: The sum of min offers at the division level should be greater than or equal to the min offer at the sub-channel
level.
The main implementation points are annotated in the strategy screenshot and described below.
Strategy: IdentifyBestTreatmentForeCareOnGetNBA
1] Filters check Channel is eCare and Division is not null.
eCare Dashboard 5 1
eCare Dashboard NudgeBar2 1 0
eCare Dashboard Extra 1 0 | VODKB-200723-160306.pdf |
d82e09d75882-1 | eCare Dashboard NudgeBar2 1 0
eCare Dashboard Extra 1 0
eCare Dashboard NudgeBar4 1 0
eCare Dashboard OffersForYou -1 1Channel SubChannel Division MaxOffers MinOffers | VODKB-200723-160306.pdf |
8759802ed6c8-0 | 514
2] Decision Data: OfferDecisionMix for eCare data is imported (see more about this new Decision Data on the PM tool screen page).
3] OfferDecisionMix for eCare is split into subchannel and division levels.
From the above decision data entries, if there is no value for Division (e.g. first row), it means the decision mix is applied at the SubChannel
level. And if there are entries for Division, it means decision mix is applied at division level.
4] At the Division level eCare offers are matched with division Decision Data.
5] eCare offers are split by divisions with unlimited MaxOffers and not unlimited MaxOffers. Only one division can have unlimited offers.
6] For not unlimited MaxOffers, a list of unique divisions is created.
7] Strategy: ApplyDecisionMixAtDivisionLevel
Uses an embedded strategy to iterate over EachDivision, Prioritize Treatments by .pxPriority and return the maximum number of offers in
priority order by Division.
8] MaxOffers for divisions with unlimited MaxOffers are set, based on MaxOffers for the subchannel.
9] Treatments are prioritized by .pxPriority and filtered to return the MaxOffers in priority order.
eCare Dashboard 5 1
eCare Dashboard NudgeBar2 1 0
eCare Dashboard NudgeBar3 1 0
eCare Dashboard NudgeBar4 1 0
eCare Dashboard NudgeBar5 -1 1Channel SubChannel Division MaxOffers MinOffers
ApplyDecisionMixAtDivisionLevel | VODKB-200723-160306.pdf |
a73f868c407e-0 | 515
10] MinOffers Check, checks the treatment count for all divisions is greater than the required MinOffers by subchannel. | VODKB-200723-160306.pdf |
629f98c866ff-0 | 516
New BDC Pipeline - dual running
Strategies are to be updated with a new pattern to support dual running of the same models from old and new pipelines. Where a model is
present in both feeds, the logic should always read from the new pipeline as priority. Previously strategies have been picking between the
old and new pipeline models at random.
Below strategies are updated as part of this Change.
A. GetBDCPropensity
Set property component “Model 967 from New Pipeline” populates this models data
“Model 967 from Old Pipeline” comes form Primary.ModelScoreListPage
The switch component “Model 967” selects between the Model 967 from the old and new pipeline
If the model id from new pipeline is not null “Model 967 from New Pipeline”
Otherwise “Model 967 from Old Pipeline” is selected
The chosen Model 967 and all “Other Models from Old Pipeline” are passed to “Join ModelID”
B. IdentifyModelBasedIntents | VODKB-200723-160306.pdf |
afe38209c9ce-0 | 517
Changes are very similar to those for GetBDCPropensity.
Set property component “Model 967 from New Pipeline” populates this models data
“Model 967 from Old Pipeline” comes form Primary.ModelScoreListPage
The switch component “Model 967” selects between the Model 967 from the old and new pipeline
If the model id from new pipeline is not null “Model 967 from New Pipeline”
Otherwise “Model 967 from Old Pipeline” is selected
The chosen Model 967 and all “Other Models from Old Pipeline” are passed to “Valid Model Scores” | VODKB-200723-160306.pdf |