1831
Upgrades - MBB Part 2
Task Dependency
HL Requirement:
A list of MBB products are presented in scrollable list as per AS IS for Mobile in all Edit screens.
and refine by fucntionality should work as is, with new attributes involved.
Configuration PM Tool
Product Attributes 861092863267 we would like to reuse the rules implemented to Fix or Flex Mobile for MBB.
862650 We would like to reuse the Insurance tab for Mobile as per AS IS to implement MBB Insurance tab (ADO-370051)
862797 We would like to reuse the behaviour implemented for Bars in Mobile journey for the MBB bundled and Device
Tariffs
921213 Logic- How we identify Top selling MBB products
899479 We need to ensure that if a customer is in Very early Upgrade
908972 We would like to display the Commissioning Tier the TSAR Agent gets for each MBB recommendation on the card
917983 We would like to reuse the error messages displayed on the Mobile journey for MBB products.
910533We would like to reuse the rules implemented to renegotiate for Mobile deals to renegotiate a deal for MBB.
Note- We have consolidated all the Mobile Renegotiation story into one
850241This user story is about how MBB device cost is calculated
902218We would like to reuse the Device tab UI and functionalities for Mobile to build MBB Device tab.
913859We would like to reuse the rules implemented in Mobile for customers who have opted out of profiling to build MBB
subscription861092 We would like to add a flag in PM Tool available so we can distinguish between MBB and Mobile customers when
we are creating cohort for commercial recommendation
Logic Yes  Logic update to include MBB plans in
Recommendation and edit flows.
APP/UI Yes Specific UI/App user stories are defined


Recommendation and edit flows.
APP/UI Yes Specific UI/App user stories are defined
separately Team Task Comments
DeviceType/  Text MBBDevice Single  Device Tablet Name  Type Description  Single/MultipleDefault Product Type Sample Value


1832
Update Decision Data - upgradelifecycles15configuration (899479)

921213- Identify Top Sold product.
Update strategy Get Recommended MBB Device.
- new datapage will be populated with top sold device product. (app team need to provide)
 input will be list of eligible MBB device products (SKUs), datapage will give one device product get all the details for reporting and api
response.
863267 -Fix or Flex - Need to include MBB Products
IsMBBProduct is true will define MBB products.
in all places where fix and flex is impacted we have to update device type =Datadevices along with Handset from AU.
Need to populate in response for MBB flow.RecommendedDeviceIsFixed and RecommendedTariffIsFixed
based on below flags.
IsFixed
FixedProductEnabledChannel
FixedProductEnabledTeam
.FixedProductEnabledOrderTypes
More details about Fix or flex
AU design - https://adqura.atlassian.net/wiki/spaces/VODKB/pages/3105259776/Assisted+Upgrade+-
+Update+the+Fix+or+Flex+visibility+flags+at+Product+Level

910533- Re negotiation validations (possible Test only Story)
Make Sure MBB devices are following all the renegotiation conditions.
All below validations are applicable for MBB products
Product Pricing Validation
Product Eligibility Validation
Product Sellable Validation
Product Compatibility Validation - Handset to Tariff Validation, Handset to Insurance Validation,Tariff to Discount Validation, Tariff to
Discount Validation, Tariff to Add On Validation, Add on to Add On Validation
Promotion Expiry Date  and element validation (if the original deal had a promo)
Any place specific to AU products like handsets need to get update with data devices. DeviceCatego
ry


Any place specific to AU products like handsets need to get update with data devices. DeviceCatego
ry
IsMBBProduct  Text MBB Product Single Y Tariff/Device Y
MBBDevice MBBDevice WithDevice -75 -180AllFromCustomerType ToCustomerType RecommendedDevic
eStatusContractEndDateFro
mContractEndDateTo Team


1833
impacted strategy - RenegotiationProductValidations and PopulateOutputPropertiesforValidateBasket
more details about renegotiation are here https://adqura.atlassian.net/wiki/spaces/VODKB/pages/3433889827/Assisted+Upgrade+-
+Renegotiation
791226 -Net Rev Calculation (possible Test only Story)
Calculate basket financials strategy involves Tariff and device products so, make sure MBB Products need to be flow and calculation
happens AsIs.
https://adqura.atlassian.net/wiki/spaces/VODKB/pages/2866446343/Assisted+Upgrade-+Calculate+Net+Revenue

913859- Opted out of profiling (test only)
MBB do not use Big Data Models, So, opted out of profiling will work AsIs. However, ProfilingConsentFlag need to be populated in all
possible cases. As per
https://adqura.atlassian.net/wiki/spaces/VODKB/pages/3379789841/Assisted+Upgrade+-+Profiling.

902218/850243 Display Device Tab:
Update Strategy: GetDeviceList
Make sure Device Type new Product Attribute need to populate as Type in this strategy from the data page D_SellablePaymHandsets.
Device Cost:
step 1: Get the tariff from the basket,
step 2: input the basket tariff and all eligible devices
a.Find each compatible device among the list of eligible devices by checking compatible devices for the basket tariff.
D_EligibleHandsetsForTariff will give the compatible handsets.
b.map the handset cost to upfront cost and set an IsValid(temp flag) to define it is compatible.
step 3: filter compatible devices with an upfront cost and non-compatable devices with a filter condition.


step 3: filter compatible devices with an upfront cost and non-compatable devices with a filter condition.
Find min upfront cost for non-compatible devices
step4: find the compatible tariffs for each non-compatible device to populate the handset cost.
 map that handset cost to min upfront cost for every product.
step 5: join both compatible and non-compatable devices before SelectWatchorHandset.
step 6: update the switch condition to route it to all devices with device cost.
Note: all compatible devices should have an upfront cost, no min upfront cost, and vice versa.
  refer GetDeviceList_36 for ProtoType strategy

899481: display device cost in Tariff Tab:
Update strategy EvaluateTariffToHandsetCompatibility.
map handset cost in data import EligibleTariffsforHandset. and make sure it passes to GetTariffList Strategy.
in the GetTariffList strategy match it to the Upfront cost to populate in LineItem.


1834
861092- customer cohorts DD
create a new SR property Upgrade Journey and add to this DD. from pm tool screen data will be updated. the possible values are
MobileBroadBand / Mobile Service.
Update strategy Populate output properties for NBAA
in our logic earlier we Set values for DealProductType as Evo or bundle.
and device type/Category is from product attributes.
we have to update with
DealProductType is updated to PromotionType
DeviceCategory should updated to existing SR property Category which app is  re-used
DealProductType and device type are as part of line items we have to populate.


1835
Upgrades - device based on loan cost
Task Dependecy
HL Requirement
Business Do not want to display device in VADR if the Device Loan Cost is zero

Recommendation screen.
Update Strategy GetRecommendedHandset
DeviceRec data join is mapped with handsetloanprice property
Update filter WithDevice with the condition handsetloanprice!=0. Which will hold any devices with loan price is 0.

Edit Screens Device Tab
Update strategy GetDeviceList
SetDeviceAttributes is having the HandsetLoanPrice, add filter after this property, and add condition handsetloanprice!=0 to drop devices
with loan price is 0.

 937471 Do not display device in VADR if the Device Loan Cost is zero
Logic Yes  Logic update to in edit rec flow.
PM Tool No
APP/UI no  Team Task Comments


1836
Upgrades - HBB Pro- Retnetion Campaign
Impacted Areas

Business Requirement:

Business would like to be able to provide a specific discount/Rank to the customer if they belong to an HBB pro ret campaign.
To identify that the customer belongs to a campaign, pro ret campaign data will be loaded into AOM via the existing Unica campaign
History load process
Configurations in PM Tool
Update Decision Data –
Retention discount and HBBPlanPrioritisation Data will be updated Churn column will be updated with campaign Type for these pro-
retention HBB Plans.
PMTool Dev: screen attribute anme will updated with Chrun Propensity /Campaign Type.
new boolean attribute IsPercentage to decide discount calculation.
the new campain type values are Winback/Fault as a local list along with high,medium and low
-we will use the same SR property to compare the values. But the value will be different for pro-ret campaigns.919653HBB Pro Ret Discount
919645HBB Pro Ret: Plan eligibility
919631HBB Pro Ret: Understanding if the customer belongs to a Pro Ret Campaign919699HBB Pro Ret Plan Prioritisation
App No
DB No
Knowledge Transfer No
Logic Yes Update Existing flow
PM Tool Yes  Configuration and existing screen update
required.Area Yes/No Comments


1837
Logic Changes:
Update Strategy GetCurrentPlanDetails
Import unica campaign history, for the subscription and get the below details for subscription.
-Customer' Subscription
- Campaign Start Date
- Campaign End Date
- Campaign Type (Winback/Fault)

source for above campaign details :
1.Campaign Type (Winback/Fault)
for .CampaignCode= TMR5991
(if cell_cd start with 4 then it is  Winback else cell_cd will start with 5 then Fault).
2..ExtractDate is the campaign start date
campaign end date - TBC (business pending )
If today is in between campaign start date and end date, then the subscription is eligible for campaign type. Set CampaignType(SR
Property) to Campaign Type(from unica). and set IsHBBProRetPlan = True.
Update strategy GetTariffDiscountForHBB
Update filter assrecordsbasedonChurnPropensity based on the campaign type value instead of churn value.
IsPercentage - is new attribute in DD Retention Discount, if it is true, then the value in retention discount should consider as %.
then the calculation should be
The Pro Ret Discount sourced from the Matrix maybe specified in % or in £. This will be indicatedby new boolean attribute.  If the discount
is a %, calculate the pro ret discount using the Acquisition Price. For example Acquisition Price is £40 and Pro Ret Discount is 20% then Pro
Ret Price = £40 – (40*0.2)= £32
if that IsPercentage is false, then AsIs exisitng logic.
skip VFT if  IsHBBProRetPlan = True.
Update strategy GetRankForHBB
DD HBBPlanPrioritisation, should work as is. Test based on the campaign type.


DD HBBPlanPrioritisation, should work as is. Test based on the campaign type.

Note: no change in eligibility plans for HBB. All should work AsIs based on the package ranking. and


1839
Upgrades - Data usage -Roaming Data
Task Dependecy
HL Requirement
Business want to display Roaming data in Data Usage.
Configuration PM Tool
Configure Product Attributes
Currently PC for addons does include International and Roaming Minutes allowance. Now add Roaming Data
It will be configured as business metadata
Configure a new Product attributes for Addons
RoamingData-Integer
Update to logic:
Update strategy -GetCustomerUsageandAllowance
2 different logic to populate Allowance & History- It can be implemented as 2 different Strategy. called from
GetCustomerUsageandAllowance. Result will contain both.(existing logic )
GetCustomerCurrentAllowance
Use GPSL Addon & Tariff data + PC data to populate customer usage details in rows.
This data will be present in Usage table as first row
Logic will create different SR rows for each Type.
ResponseType=USAGE
UsageType = Data/Mins/Texts/Roaming Mins/Int Mins / Roaming Data (new one)
Allowance = Calculated as in below
 919596Display Data Roaming Usage
Logic Yes  Logic update to include Roaming data in
data usage panel .
PM Tool No
APP/UI Yes Specific UI/App has to work on Displaying
and response attributes.  Team Task Comments
UsageType soruce UI Formating


1840

referer parent design for more details  Assisted Upgrade-Customer Profile-Usage Data
Update GetCustomerUsageHistory (every thing is exisitng ) need to update roaming data
Import UsageHistory of subscription
See the data structure for Usage history data set https://vodafone.sharepoint.com/sites/AoMProgramme/_layouts/15/Doc.aspx?so
urcedoc=%7B437d28d5-c1b5-4cf9-968b-d41286710173%7D&action=edit&wd=target%28Data.one%7CB4DAFF12-56DA-4634-B9
36-A60B00F07201%2FUsage%20History%7Ce27de858-d923-4309-86e4-a94f81d644b1%2F%29 -
 >
History table will have multiple records , by date & usage category & sub category
Map usage category & sub category values to UsageType according to the below logic
Roaming Mins: the usage cat id = 23 and the usage sub cat id = 11 ('Roaming Data'). (New Change)
Aggregate usage data by InvoiceDate, UsageType
Create History records under each type
SET ResponseType=HISTORY

 Roaming Data Product Attributes for Addon
update CalculateAddOnData to source
product attributes & sum the value ,make
sub strategy call to this.
Update groupby with this roaming data.

CalculateAddOnData - has this logic we can
make sub strategy call to this.If UK data > 25 GB then roaming is 25GB.
And if Data <25GB then show calculated
roaming data
Connect your OneDrive accoun
t


1841
Upgrades-Assisted S15 and Watch Manufacturere.doc
Task Dependecy
HL Requirement
Business want to display all the devices irrespective to manufacturer in the edit screen device list.
Business want to change the source for s15, which is wrongly mapped in initial releases.
Logical Changes:

Update strategy(907909)

Getdevice list : remove filter FilterByManufacturer which is checking manufacturer and IdentifyManufacturer substrategy which will
get manufacturer details.

Update strategy(919524):
CalculateS15MafandBand :
update set property  SetPreS15Calculation and FlexiPreS15Maf, remove reference of .CustomNumberField208 and update with
.CustomNumberField002.
And enable switch to consider this component with condition.
@String.equalsIgnoreCase(SetPreS15Calculation.PreS15Calculation,"Flexi").

 919524New Pre S15 Field calculates15maf and bands907909Change in the identifying manufacturere in refine by for watch recommendation.
Logic Yes  Logic update Strategy changes.
PM Tool No
APP/UI No  Team Task Comments


1843
Simulation Post Processing

Impact in Other areas
Dependencies
Logic Changes
A. Update Strategy - Import<Channel>T reatments
B. New Strategy - ImportAllT reatmentsWithoutActiveCheck
C. Update Strategy - ImportAllT reatments
D.  Update Strategy - AllPropositionsLookup

Impact in Other areas
Dependencies

Logic Changes

A. Update Strategy - Import<Channel>Treatments
Make the following changes to the 15 strategies below -
ImportOutboundCCTreatments954431 Simulation Post Processing
PM Tool No
PM Tool KT Documentation No
Knowledge Transfer No
App No
DB No  Area Yes/No Comments
PM Tool No
App No
DB No  Area Yes/No Comments


1844
ImportInboundCCTreatments
ImportEmailTreatments
ImportDirectMailTreatments
ImportAppPushTreatments
ImportWebTreatments
ImportSMSTreatments
ImportRetailTreatments
ImportIVRTreatments
ImportAppTreatments
ImportRCSTreatments
ImportMMSTreatments
ImportMicrositeTreatments
ImporteCareTreatments
ImportTOBiTreatments
Change -
Remove filter component “Active Treatments”
Connect all proposition import components to Results
B. New Strategy - ImportAllTreatmentsWithoutActiveCheck
Save existing ImportAllTreatments strategy as ImportAllTreatmentsWithoutActiveCheck
Please note that with introduction of any new channels, this strategy should be updated for Simulation along with the original
strategy ImportAllTreatments used by main decisioning funnel.
C. Update Strategy - ImportAllTreatments
Disconnect all sub-strategy components from Results
Add new filter component - “Active Treatments” with condition -
.pyIsActive && .Enabled
Connect all sub-strategy components to filter component - “Active Treatments”


1845
Connect filter component - “Active Treatments” to Results
D.  Update Strategy - AllPropositionsLookup
Replace sub-strategy ImportAllTreatments with sub-strategy ImportAllTreatmentsWithoutActiveCheck


1846
MBB Upgrade - Logic Review / Update
GetDeviceList
US 902218:
DeviceCategory from Product Attributes needs to be mapped in Sellable Devices. These contains Values such as Tablet/Laptop.
Also, UI needs to be informed to take DeviceCategory and map it to DeviceType in the Device Tab.
Perform the upfront cost calculation only for Bundled Device and Tariff (Fetch the PromotionType=Bundled from context). For Evo
Devices upfront cost should me marked as '-'
US 854004/US850243 :
Scenario 1(854004) -
For incompatible devices, the upfront cost will contain the minimum Handset cost from the Handset-to-tariff compatibility table for
the respective device, in combination with all other compatible tariffs. The upfront value will be displayed as ‘From £xx.xx' cost in
the upfront cost column. → The criteria says value should be displayed as 'From £xx.xx’ . As UI will not be knowing whethere it is
compatible or incompatible devices we have to send From but if logic send From it would be From 15, there will not be pound
symbol in between. Needs to be discussed with Business and accordingly update.
PopulateOutputPropertiesForDevice should have productrecommendationtype=Device for MBB devices (DeviceType = Data
Device then productrecommendationtype=Device else Handset)
PromotionType !=”” → Is considered as Data Device. I believe when you are building a own deal we will not have Promotion Type in Get
Recommendation then DeviceType will be considered as Handset → needs to be checked with Sunand

GetTariffList
US 899481
As per app/UI team, they are mapping Upfront cost in the tariff tab to Handset Cost , however we are mapping DefaultUpfrontCost to


Handset Cost in CombineAllTariffs.
GetListofActiveTariffs - SetRecommendedTariffDetails - RecommendedTariffCustomerType along with existing code, we need to
find out how to identify MBB customer (We will check with Sunand once he is back) based on it,
if SegmentofTariff = Loan, then MBBLoan
if MBBFlag=Y and SIMOnly=Y and SegmentofTariff=CBU then MBBSimo
if MBBFlag=Y and SIMOnly=N and SegmentofTariff=CBU then MBBDevice
PopulateOutputPropertiesForTariff  > SetPropertiesforTariff > Category > Along with existing code, we need to check for
RecommendedCustomerType = MBBSIMO then SIMO, RecommendedCustomerType=MBBLoan then EVO,
RecommendedCustomerType=MBBDevice then Bundled. .
Acceptance Criteria says → The upfront cost is only populated for Tariffs which are compatible with selected Device (if any in the
basket) → This needs to be handled, for the remaining devices mark it as -


1847
Release 3.07


1848
OB Enabler - App Push & Inbox into Templating

Impact in Other areas
Dependencies
Change Description
Logic Changes
A. New Strategy - AssignAppPushT emplates
B. Update Strategy - PopulateOutputPropertiesForAppPushBatch
C. Update Strategy - PopulateOutputPropertiesForAppPushByT rigger
D. Update Strategy - GetPropositionDataForT reatment (Used for AppPush Seed Test)

Impact in Other areas
Dependencies
Change Description
PM Tool to enable Standard Templating solution for AppPush Channel but using T2TVAttributes only (no separate configurations for
T2TVActions)
PM Tool to make existing Templating solution for AppPush Channel as read-only so that user uses only new templating solution for any
changes (new or update); change should be complete across all SubChannels (Push, Inbox & InApp)
Logic is updated to look at the Standard Templates for AppPush Channel and if standard template is not available; otherwise, use legacy
templates
With the above approach, no migration of template data for existing AppPush treatments are required 924887 Uplift Templating solution for App push and inbox.
PM Tool Yes
PM Tool KT Documentation Yes
Knowledge Transfer Yes
App No
DB No  Area Yes/No Comments
PM Tool Yes
App No
DB No  Area Yes/No Comments


1849
New story is required for later sprints to remove the Legacy Templating structure once all existing AppPush treatments moved to new
Standard Templating structure by Opti team

Logic Changes
A. New Strategy - AssignAppPushTemplates
Enable External Input
Add Set Property “Set Default Scenario”
Scenario = “Default”
Call to Sub-strategy ImportTreatmentToTreatmentVariationAttributes
After Set Property “Set Default Scenario”, add Data join component “Get Template Details“
Join with Sub-strategy ImportTreatmentToTreatmentVariationAttributes
On conditions TreatmentName,OfferVariant, TreatmentVariant and Scenario
Do not exclude unmatched records
Map in property mapping -
ValueText = "Template Available"
TargetSubChannel = TargetSubChannel
TreatmentAttributes = TemplateDetails
After Data join, Add filter component “Template Not Available” with condition
ValueText = NULL
Connect  filter component “Template Not Available” to Results
After Data join, Add another filter component “Template Available” with condition
ValueText != NULL
After filter component “Template Available”, add Group By component “Treatments with Template Available“
Group by TreatmentName
After filter component “Template Available”, add filter component “Push Template” with condition
TargetSubChannel = “Push”
After filter component “Template Available”, add filter component “Inbox Template” with condition


1850
TargetSubChannel = “Inbox”
After filter component “Template Available”, add filter component “InApp Template” with condition
TargetSubChannel = “InApp”
After Group By component “Treatments with Template Available“, add set property “Reset Legacy Templates”
PushNotificationJSON = NULL
InboxNotificationJSON = NULL
InAppNotificationJSON = NULL
After set property “Reset Legacy Templates”, add Data join “Get Push Template Details”
Join with filter component “Push Template”
On conditions TreatmentName,OfferVariant, TreatmentVariant and Scenario
Do not exclude unmatched records
Map in property mapping -
PushNotificationJSON = TreatmentAttributes
After Data join “Get Push Template Details”, add Data join “Get Inbox Template Details”
Join with filter component “Inbox Template”
On conditions TreatmentName,OfferVariant, TreatmentVariant and Scenario
Do not exclude unmatched records
Map in property mapping -
InboxNotificationJSON = TreatmentAttributes
After Data join “Get Inbox Template Details”, add Data join “Get InApp Template Details”
Join with filter component “InApp Template”
On conditions TreatmentName,OfferVariant, TreatmentVariant and Scenario
Do not exclude unmatched records
Map in property mapping -
InAppNotificationJSON = TreatmentAttributes
Connect Data join “Get InApp Template Details” to Results

B. Update Strategy - PopulateOutputPropertiesForAppPushBatch
Call sub-strategy AssignAppPushTemplates after External Input and connect to main path

C. Update Strategy - PopulateOutputPropertiesForAppPushByTrigger
Call sub-strategy AssignAppPushTemplates after External Input and connect to main path


1851
D. Update Strategy - GetPropositionDataForTreatment (Used for AppPush Seed Test)
Add filter component - “Not AppPush” after set property “Get All Parent & Child Treatments“ with condition as
.Channel != "AppPush"
Connect filter component - “Not AppPush” to Results
Add another filter component - “AppPush” after set property “Get All Parent & Child Treatments“ with condition as
.Channel = "AppPush"
Call sub-strategy AssignAppPushTemplates after filter component - “AppPush”
Connect ub-strategy AssignAppPushTemplates to Results


1852
OB Enabler - SMS Pega Marketing decom

Impact in Other areas
Dependencies
Change Description
Logic Changes
A. Update Data Flow - GetBestT reatmentsByGetNBA
B. Update Data Flow - ProcessSMSForT2S

Impact in Other areas
Dependencies
Change Description
Move SMS on Real-time execution mode (ProcessEvent & GetNBA) into Channel Management

Logic Changes
A. Update Data Flow - GetBestTreatmentsByGetNBA
Update Filter “SMS“ 924873 Decommission the use of Pega Marketing to send SMS for Trigger
event and GNBA (Post NSCL)
PM Tool No
PM Tool KT Documentation No
Knowledge Transfer Yes
App Yes
DB No  Area Yes/No Comments
PM Tool No
App Yes
DB No  Area Yes/No Comments


1853
Rename as “SMS By Pega Marketing“
Add new condition to evaluate true if when rule - Toggle_ChannelManagement20220420T132037 returns false
Add new branch and add filter “SMS By Channel Management“ and add rolling conditions -
.Channel = “SMS“
.DVTMode != true
evaluate true if when rule - Toggle_ChannelManagement20220420T132037 returns true
Add destination to the new Branch - Activity - SendRealtimeSMS
Add new branch and add filter “IH Validation CM“ and add rolling conditions -
.Channel = “SMS“
.DVTMode != true
evaluate true if when rule - Toggle_ChannelManagement20220420T132037 returns true
Add destination to the new Branch - Data set - pxInteractionHistory
Add new branch and add filter “IH Reporting Validation CM“ and add rolling conditions -
.Channel = “SMS“
.DVTMode != true
evaluate true if when rule - Toggle_ChannelManagement20220420T132037 returns true
Add Convert shape to the new Branch to convert from SR class to VFUK-FW-AOMFW-Data-InteractionHistoryReporting class
Enable Auto-copy
set .InteractionID = .pxInteractionID
set .OutcomeTime = .pxOutcomeTime
set .SubscriptionId = .pySubjectID
Set secondary destination to data set - InteractionHistoryReporting


1855
B. Update Data Flow - ProcessSMSForT2S
Update Filter “SaveSMSFlag“
Rename as “SMS By Pega Marketing“
Add new condition to evaluate true if when rule - Toggle_ChannelManagement20220420T132037 returns false
Add new branch and add filter “SMS By Channel Management“ and add rolling conditions -
.SaveSMSFlag = false
.ErrorMessage = ““
.InControlGroup = “N“
evaluate true if when rule - Toggle_ChannelManagement20220420T132037 returns true
Add destination to the new Branch - Activity - SendRealtimeSMS
Add new branch and add filter “IH Validation CM“ and add rolling conditions -
.SaveSMSFlag = false
.ErrorMessage = ““
.InControlGroup = “N“
evaluate true if when rule - Toggle_ChannelManagement20220420T132037 returns true
Add destination to the new Branch - Data set - pxInteractionHistory
Add new branch and add filter “IH Reporting Validation CM“ and add rolling conditions -
.SaveSMSFlag = false
.ErrorMessage = ““
.InControlGroup = “N“
evaluate true if when rule - Toggle_ChannelManagement20220420T132037 returns true
Add Convert shape to the new Branch to convert from SR class to VFUK-FW-AOMFW-Data-InteractionHistoryReporting class
Enable Auto-copy
set .InteractionID = .pxInteractionID
set .OutcomeTime = .pxOutcomeTime
set .SubscriptionId = .pySubjectID
Set secondary destination to data set - InteractionHistoryReporting
Update filter “ErrorMessage is null and In controlGroup“
Add condition .InControlGroup = “Y“


1857
Personalised Video (Build - Email/SMS/AppPush, Dev Test - Email Only)

Impact in Other areas
Dependencies
Change Description
Logic Changes - Core
A. New Decision Data - T2TVHandoverActions
B. New Strategy - ImportAllT2TVHandoverActions
C. New Strategy - ReplaceDataT okensForHandoverActionT emplates (RS: Business-Artefacts)
D. New Strategy - SetHandoverActions
D. Update Strategy - Get Proposition Data For Treatment
E. New Strategy - SetLandingPageCT AInTemplate
F. Update Strategy - SetLandingPageCT A
G. Update Strategy - ApplyT reatmentDataT oTreatments
Logic Changes - Email
H. Update Strategy - PopulateOutputPropertiesForEmailByChannelManagement
Logic Changes - SMS
I. Update Strategy - PopulateOutputPropertiesForSMSByBatch
J. Update Strategy - PopulateOutputPropertiesForSMSByT rigger
Logic Changes - AppPush (with Template)923976 Flag Treatments as Requiring Video and optionally
requiring redirect to an external landing pageIn Scope
923977 Idomoo integration; AoM call for personalised video and
handling the returned URLApp Story
923978 Redirect to digital Landing Page App Story
923981 Test Video Generation for Seeds (Email Only) In Scope
923983 NFRs Not Logic
923984 Report on video plays - BUSINESS UAT/FUT TEST
STORY ONLYNot Logic
923985 Splunk monitoring and alerting for video generation,
redirect to landing page(s) and responsesNot Logic
926572 Store Idomoo outcome and video URL in IH Not Logic
926572 Introduce functionality to launch Landing page from
AppPush (Batch & RT) - LogicIn Scope
975826 Introduce functionality to launch Landing page from OB


975826 Introduce functionality to launch Landing page from OB
Email - LogicIn Scope
923976 Introduce functionality to launch Landing page from OB
SMS - LogicIn Scope923974 Test Catalogue (Email Only) In Scope


1858
g g pp ( p )
K. Update Strategy - AssignAppPushT emplates
L. Update Strategy - PopulateOutputPropertiesForAppPushBatch
M. Update Strategy - PopulateOutputPropertiesForAppPushByT rigger
Logic Changes - AppPush (without Template)
N. New Strategy - SetLandingPageCT AForAppPush
O. Update Strategy - PopulateOutputPropertiesForAppPushBatch
P. Update Strategy - PopulateOutputPropertiesForAppPushByT rigger

Impact in Other areas
Dependencies
Change Description
Email (Batch - IMI SubChannel), SMS (Batch & Real-time) & AppPush (Batch & Real-time) will use existing Landing Page solution (but
Not the Microsite Decisioning Funnel)
New “section” in PM tool on T2TV screen will be introduced to capture Personalised Video generation metadata
Introduce new Decision data T2TVHandoverActions to store Personalised Video generation metadata and use in Strategy FW
If the Treatment contains a HandOverAction available, Strategy FW will call existing SaveMetaData function to store Personalised Video
generation metadata in C* dataset and retrieve the Unique Key corresponding to the record stored and make the Key available to the
Treatment data as VideoHandoverActionId
Strategy FW will generate the Landing Page URL following exiting design pattern for SMS and extend this functionality to Email &
AppPush
When the Landing Page URL is clicked from the Outbound Comms (Email, SMS & AppPush), the existing Microsite Case will be
initiated.
If the corresponding Customer/Treatment data contains VideoHandoverActionId, the case will retrieve the relevant Personalised
Video generation metadata from C* dataset, retrieve the Personalised Video URL from Idoomoo and redirect to external site for
presenting the Personalised Video


presenting the Personalised Video
If the corresponding Customer/Treatment data does not contain VideoHandOverActionId, the case will execute the Microsite
Decisioning funnel following as-is processPM Tool Yes
PM Tool KT Documentation Yes
Knowledge Transfer Yes
App Yes
DB Yes  Area Yes/No Comments
PM Tool Yes
App Yes
DB Yes  Area Yes/No Comments


1859
Seedtest of Personalised Video will be available using existing outbound Seed-testing functionality for Email/SMS/AppPush
Storing Idoomoo Outcome and Video URL - This will be stored in a new table instead of IH

Logic Changes - Core
A. New Decision Data - T2TVHandoverActions
Create Proposition Decision Data T2TVHandoverActions in each of the squads (Issue) with following additional properties -
TreatmentName
TreatmentID
OfferName
OfferVariant
TreatmentVariant
ActionType
ActionAttributes
TemplateAttributes

T2TVHandoverActions Care T2TVHandoverActions
T2TVHandoverActions CrossSell T2TVHandoverActions
T2TVHandoverActions Engagement T2TVHandoverActions
T2TVHandoverActions HBB T2TVHandoverActions
T2TVHandoverActions Loyalty T2TVHandoverActions
T2TVHandoverActions Renew T2TVHandoverActions
T2TVHandoverActions Retain T2TVHandoverActionsDecision Data Issue Group


1860

B. New Strategy - ImportAllT2TVHandoverActions
Save ImportAllT2TVActions structure as new strategy ImportAllT2TVHandoverActions
Update the proposition import components to import new “T2TVHandoverActions” group from respective Issues as below (screenshot
from T2TVActions strategy)
C. New Strategy - ReplaceDataTokensForHandoverActionTemplates (RS: Business-Artefacts)
Enable External Input
Add set property component “Replace Data Tokens in ActionAttributes“ after External Input
Do not set any properties
THIS IS PLACEHOLDER to for data token replacement in ActionAttributes
Add set property component “Replace Data Tokens in TemplateAttributes“ after set property component “Replace Data Tokens in
ActionAttributes“
Do not set any properties
THIS IS PLACEHOLDER to for data token replacement in ActionAttributes
Connect set property component “Replace Data Tokens in TemplateAttributes“ to ResultsT2TVHandoverActions Retention T2TVHandoverActions
T2TVHandoverActions Service T2TVHandoverActions
T2TVHandoverActions TradeIn T2TVHandoverActions
T2TVHandoverActions Upsell T2TVHandoverActions


1861

D. New Strategy - SetHandoverActions
Enable External Input
Call Sub-strategy ImportAllT2TVHandoverActions
Add data join component “Join HandoverAction Data“ after External Input
Join with Sub-strategy ImportAllT2TVHandoverActions
Join on -
TreatmentName
OfferVariant
TreatmentVariant
Do not Exclude
Map properties -
ActionType = ActionType
ActionAttributes = ActionAttributes
TemplateAttributes = TemplateAttributes
Add filter “Handover Action Not Available” after data join “Join HandoverAction Data“ with condition -
ActionAttributes = NULL
Connect filter “Handover Action Not Available” to Results
Add another filter “Handover Action Available” after data join “Join HandoverAction Data“ with condition -
ActionAttributes != NULL
Add sub-strategy ReplaceDataTokensForHandoverActionTemplates after filter “Handover Action Available”
Add set property component “Set VideoHandoverActionId“ after sub-strategy ReplaceDataTokensForHandoverActionTemplates
create SR property VideoHandoverActionId (text)
VideoHandoverActionId =
@AOMUtilities.SaveOffersMetadata(Primary.CustomerID,"pxInteractionID,Channel,OfferName,OfferVariant,TreatmentName,Treatm
entVariant,AOMInteractionId,ActionType,ActionAttributes,TemplateAttributes",myStepPage)


1862
Connect et property component “Set VideoHandoverActionId“ to Results

D. Update Strategy - Get Proposition Data For Treatment
Disconnect set property component ““Get All Parent & Child Treatments” from Results
Add new set property component “Set SeedUser Flag“ after set property component ““Get All Parent & Child Treatments”
create SR property SeedUser (boolean)
SeedUser = true
Add filter component “Email Channel“ after set property component “Set SeedUser Flag“
.Channel = “Email“
Add filter component “SMS Channel“ after set property component “Set SeedUser Flag“
.Channel = “SMS“
Add filter component “AppPush Channel“ after set property component “Set SeedUser Flag“
.Channel = “AppPush“
Connect filter component “Email Channel“ to Results
Add sub-strategy PopulateOutputPropertiesForSMSByBatch after filter component “SMS Channel“
Connect sub-strategy PopulateOutputPropertiesForSMSByBatch to Results
Add sub-strategy PopulateOutputPropertiesForAppPushBatch after filter component “AppPush Channel“
Connect sub-strategy PopulateOutputPropertiesForAppPushBatch to Results


1863
E. New Strategy - SetLandingPageCTAInTemplate
Enable External Input
Add filter component “Template does not contain LandingPageCTA“ with condition -
!@contains(.TreatmentAttribute,”[LandingPageCTA]”)
Connect filter component “Template does not contain LandingPageCTA“ to Results
Add filter component “Template contains LandingPageCTA“ with condition -
@contains(.TreatmentAttribute,”[LandingPageCTA]”)
Add set property component “Set Microsite URL“ after filter component “Template contains LandingPageCTA“
.MicrositeURL = D_VFUKFWAOMFWDataAOMConfig[ConfigType:Microsite,ConfigName:OffersURL].ConfigValue
.Metadatacode =
@AOMUtilities.SaveOffersMetadata(Primary.CustomerID,"pxInteractionID,Channel,OfferName,OfferVariant,TreatmentName,Treatm
entVariant,AOMInteractionId,VideoHandoverActionId,SeedUser",myStepPage)
.LandingPageCTA = .MicrositeURL+.Metadatacode
TreatmentAttributes = @String.replaceAll(.TreatmentAttributes,"[LandingPageCTA]",.LandingPageCTA)
Connect set property component “Set Microsite URL“ to Results
F. Update Strategy - SetLandingPageCTA
Update set property component “Set Microsite URL“ after filter component “Template contains LandingPageCTA“
.Metadatacode =
@AOMUtilities.SaveOffersMetadata(Primary.CustomerID,"pxInteractionID,Channel,OfferName,OfferVariant,TreatmentName,Treatm
entVariant,AOMInteractionId,VideoHandoverActionId,SeedUser",myStepPage)
G. Update Strategy - ApplyTreatmentDataToTreatments
Update data join component “All Treatments With Properties“
Add mapping
SeedUser = SeedUser


1864
Logic Changes - Email
H. Update Strategy - PopulateOutputPropertiesForEmailByChannelManagement
Disconnect data join component “Join Treatment Attributes“ from sub-strategy “PopulateSquadSpecificOutputProperties“
Add sub-strategy “SetHandoverActions” after data join component “Join Treatment Attributes“
Add sub-strategy “SetLandingPageCTAinTemplate“ after sub-strategy “SetHandoverActions”
Connect sub-strategy “SetLandingPageCTAinTemplate“ to sub-strategy “PopulateSquadSpecificOutputProperties“
Logic Changes - SMS
I. Update Strategy - PopulateOutputPropertiesForSMSByBatch
Disconnect set property component “Use Data Tokens“ from sub-strategy “SetLandingPageCTA“
Add sub-strategy “SetHandoverActions” after set property component “Use Data Tokens“
Connect sub-strategy “SetHandoverActions” to sub-strategy “SetLandingPageCTA“

J. Update Strategy - PopulateOutputPropertiesForSMSByTrigger
Disconnect set property component “Use Data Tokens“ from sub-strategy “SetLandingPageCTA“
Add sub-strategy “SetHandoverActions” after set property component “Use Data Tokens“
Connect sub-strategy “SetHandoverActions” to sub-strategy “SetLandingPageCTA“


1865

Logic Changes - AppPush (with Template)
K. Update Strategy - AssignAppPushTemplates
Disconnect filter component “Template Available“ from filter components -
TargetSubChannel Push
TargetSubChannel Inbox
TargetSubChannel InApp
Add sub-strategy “SetLandingPageCTAinTemplate“ after filter component “Template Available“
Connect sub-strategy “SetLandingPageCTAinTemplate“ to filter components -
TargetSubChannel Push
TargetSubChannel Inbox
TargetSubChannel InApp
L. Update Strategy - PopulateOutputPropertiesForAppPushBatch
Disconnect External Input from filter components
With Product Code
Without Product Code
Add sub-strategy “SetHandoverActions” after External Input
Add sub-strategy “AssignAppPushTemplates“ after sub-strategy “SetHandoverActions”
Connect sub-strategy “AssignAppPushTemplates“ to filter components
With Product Code
Without Product Code


1866

M. Update Strategy - PopulateOutputPropertiesForAppPushByTrigger
Disconnect External Input from filter components
With Product Code
Without Product Code
Add sub-strategy “SetHandoverActions” after External Input
Add sub-strategy “AssignAppPushTemplates“ after sub-strategy “SetHandoverActions”
Connect sub-strategy “AssignAppPushTemplates“ to filter components
With Product Code
Without Product Code
Logic Changes - AppPush (without Template)
N. New Strategy - SetLandingPageCTAForAppPush
Enable External Input
Add filter component “Template does not contain LandingPageCTA“ with condition -
PushNotificationJSON AND InboxNotificationJSON AND InAppNotificationJSON does not contain [LandingPageCTA]
Connect filter component “Template does not contain LandingPageCTA“ to Results
Add filter component “Template contains LandingPageCTA“ with condition -
PushNotificationJSON OR InboxNotificationJSON OR InAppNotificationJSON does not contain [LandingPageCTA]
Add set property component “Set Microsite URL“ after filter component “Template contains LandingPageCTA“
.MicrositeURL = D_VFUKFWAOMFWDataAOMConfig[ConfigType:Microsite,ConfigName:OffersURL].ConfigValue
.Metadatacode =
@AOMUtilities.SaveOffersMetadata(Primary.CustomerID,"pxInteractionID,Channel,OfferName,OfferVariant,TreatmentName,Treatm
entVariant,AOMInteractionId,VideoHandoverActionId,SeedUser",myStepPage)
.LandingPageCTA = .MicrositeURL+.Metadatacode
PushNotificationJSON = @String.replaceAll(.PushNotificationJSON,"[LandingPageCTA]",.LandingPageCTA)
InboxNotificationJSON = @String.replaceAll(.InboxNotificationJSON,"[LandingPageCTA]",.LandingPageCTA)


InAppNotificationJSON = @String.replaceAll(.InAppNotificationJSON,"[LandingPageCTA]",.LandingPageCTA)
Connect set property component “Set Microsite URL“ to Results


1867

O. Update Strategy - PopulateOutputPropertiesForAppPushBatch
Disconnect External Input from filter components
With Product Code
Without Product Code
Add sub-strategy “SetHandoverActions” after External Input
Add sub-strategy “SetLandingPageCTAForAppPush“ after sub-strategy “SetHandoverActions”
Connect sub-strategy “SetLandingPageCTAForAppPush“ to filter components
With Product Code
Without Product Code

P. Update Strategy - PopulateOutputPropertiesForAppPushByTrigger
Disconnect External Input from filter components
With Product Code
Without Product Code


1868
Add sub-strategy “SetHandoverActions” after External Input
Add sub-strategy “SetLandingPageCTAForAppPush“ after sub-strategy “SetHandoverActions”
Connect sub-strategy “SetLandingPageCTAForAppPush“ to filter components
With Product Code
Without Product Code


1869
NBA FW - Revise High Intent Bypass for Offer Self Contention

Impact in Other areas
Dependencies
Logic Changes:
A.Update Stratgey ApplyOfferSelfContentionStrategy
Update the filter Component 'Apply Contention' as below
      .ApplyOfferSelfContentionStrategy="Yes"
Update the filter Component 'No Contention' as below
       .ApplyOfferSelfContentionStrategy!="Yes"
Move Negative Outcome code Snippet to After the 'Apply Contention' Filter970332 Revise High Intent Bypass for Offer Self Contention
PM Tool No
PM Tool KT Documentation No
Knowledge Transfer No
App No
DB No  Area Yes/No Comments
PM Tool No
App No
DB No  Area Yes/No Comments


1870
After Moving the Negative Outcome code  , Add 2 Filter
          1)Add First Filter and name it as 'LowConfidenceScore Path' and .ConfidenceScoreRange!="High" and
              Connect to 'Join By Latest Batch Selection By Subscription Sent' Data join Component.
         2)Add Second Filter and name it as 'HighConfidenceScore Path' and .ConfidenceScoreRange="High"
             and  Connect to 'Set OfferRelevancy For No Contention' SetProperty Component.


1871
Customer Simulation - Offer Eligibility split

Impact in Other areas
Dependencies
Logic Changes
A. New Strategy - ApplyOf ferCoreEligibility (RS: AOMFW -Artifacts)
B. New Strategy - ApplyOf ferCoreEligibilityForSimulation (RS: AOMFW -Artifacts)
C. New Strategy - TradeInSquadZoneForOf fer (RS: AOMFW -Business-Artifacts)
D. New Strategy - CareSquadZoneForOf fer (RS: AOMFW -Business-Artifacts)
E. New Strategy - EngagementSquadZoneForOf fer (RS: AOMFW -Business-Artifacts)
F. New Strategy - HBBSquadZoneForOf fer (RS: AOMFW -Business-Artifacts)
G. New Strategy - LoyaltySquadZoneForOf fer (RS: AOMFW -Business-Artifacts)
H. New Strategy - UpsellSquadZoneForOf fer (RS: AOMFW -Business-Artifacts)
I. New Strategy - ServiceSquadZoneForOf fer (RS: AOMFW -Business-Artifacts)
J. New Strategy - RetainSquadZoneForOf fer (RS: AOMFW -Business-Artifacts)
K. New Strategy - RenewSquadZoneForOf fer (RS: AOMFW -Business-Artifacts)
L. New Strategy - CrossSellSquadZoneForOf fer (RS: AOMFW -Business-Artifacts)
M. New Strategy - RetentionSquadZoneForOf fer (RS: AOMFW -Business-Artifacts)
N. New Strategy - ApplyOf ferSquadEligibility (RS: AOMFW -Artifacts)


N. New Strategy - ApplyOf ferSquadEligibility (RS: AOMFW -Artifacts)
O. New Strategy - ApplyOf ferSquadEligibilityForSimulation (RS: AOMFW -Artifacts)
P. New Strategy - ApplyOf ferEligibility (RS: AOMFW -Artifacts)
Q. Update Strategy - IdentifyEligibleOf fers
R. Withdraw Strategies
S. Update Data - simulation_funnel_ref

Impact in Other areas
Dependencies977155 Separate Squad Zones From Standard Offer Eligibility
PM Tool No
PM Tool KT Documentation No
Knowledge Transfer No
App Yes App Versioning
DB Yes  Update funnel audit and post processing Area Yes/No Comments
Area Yes/No Comments


1872

Logic Changes

A. New Strategy - ApplyOfferCoreEligibility (RS: AOMFW-Artifacts)
Enable External Input
Add following filters after External Input
“TradeIn” with condition as - @equalsIgnoreCase(.BusinessPurpose,TradeIn)
“UpSell” with condition as - @equalsIgnoreCase(.BusinessPurpose,UpSell)
“Retention” with condition as - @equalsIgnoreCase(.BusinessPurpose,Retention)
“Service” with condition as - @equalsIgnoreCase(.BusinessPurpose,Service)
“Retain” with condition as - @equalsIgnoreCase(.BusinessPurpose,Retain)
“Renew” with condition as - @equalsIgnoreCase(.BusinessPurpose,Renew)
“CrossSell” with condition as - @equalsIgnoreCase(.BusinessPurpose,CrossSell)
“Care” with condition as - @equalsIgnoreCase(.BusinessPurpose,Care)
“Engagement” with condition as - @equalsIgnoreCase(.BusinessPurpose,Engagement)
“HBB” with condition as - @equalsIgnoreCase(.BusinessPurpose,HBB)
“Loyalty” with condition as - @equalsIgnoreCase(.BusinessPurpose,Loyalty)
Add following filters after Squad based filters as created above respectively -
“Execute TradeIn Proposition Filter” using proposition filter - TradeInOffersEligibility
“Execute UpSell  Proposition Filter” using proposition filter - UpSellOffersEligibility
“Execute Retention Proposition Filter” using proposition filter - RetentionOffersEligibility
“Execute Service  Proposition Filter” using proposition filter - ServiceOffersEligibility
“Execute Retain Proposition Filter” using proposition filter - RetainOffersEligibility
“Execute Renew Proposition Filter” using proposition filter - RenewOffersEligibility
“Execute CrossSell  Proposition Filter” using proposition filter - CrossSellOffersEligibility
“Execute Care  Proposition Filter”  using proposition filter - CareOffersEligibility


“Execute Care  Proposition Filter”  using proposition filter - CareOffersEligibility
“Execute Engagement  Proposition Filter” using proposition filter - EngagementOffersEligibility
“Execute HBB Proposition Filter” using proposition filter - HBBOffersEligibility
“Execute Loyalty Proposition Filter” using proposition filter - LoyaltyOffersEligibility
Connect the following filters to results
“Execute TradeIn Proposition Filter”
“Execute UpSell  Proposition Filter”
“Execute Retention Proposition Filter”
“Execute Service  Proposition Filter”
“Execute Retain Proposition Filter”
“Execute Renew Proposition Filter”
“Execute CrossSell  Proposition Filter”
“Execute Care  Proposition Filter”PM Tool No
App Yes
DB Yes


1873
“Execute Engagement  Proposition Filter”
“Execute HBB Proposition Filter”
“Execute Loyalty Proposition Filter”

B. New Strategy - ApplyOfferCoreEligibilityForSimulation (RS: AOMFW-Artifacts)
Enable External Input
Add Sub-strategy component ApplyOfferCoreEligibility after External Input
Add set property component “Reset Tags For Matching“ after External Input and set -
ValueInteger = 0
AdhocText1 = NULL
Add data join component “Match Eligible Propositions“ after set property component “Reset Tags For Matching“
Join with Sub-strategy component ApplyOfferCoreEligibility
Join on pyName
Do not Exclude
Map Properties
ValueInteger = 1
Add set property component “Record Dropped Propositions“ after data join component “Match Eligible Propositions“ and set -
AdhocText1 = @if(.ValueInteger=1,"",@AOMUtilities.CaptureSimulationDropOff("Offer Core Eligibility",myStepPage))
Add filter component “Eligible Propositions“ with condition - .ValueInteger=1
Add switch component “Simulation Mode Check“
Select "Eligible Propositions" if @String.equalsIgnoreCase(Primary.Context(SimulationMode),"true")
Otherwise, select "ApplyOfferCoreEligibility"
Connect switch component “Simulation Mode Check“ to Results


1874

C. New Strategy - TradeInSquadZoneForOffer (RS: AOMFW-Business-Artifacts)
Enable External Input and connect to Results
D. New Strategy - CareSquadZoneForOffer (RS: AOMFW-Business-Artifacts)
Enable External Input and connect to Results

E. New Strategy - EngagementSquadZoneForOffer (RS: AOMFW-Business-Artifacts)
Enable External Input and connect to Results


1875

F. New Strategy - HBBSquadZoneForOffer (RS: AOMFW-Business-Artifacts)
Enable External Input and connect to Results

G. New Strategy - LoyaltySquadZoneForOffer (RS: AOMFW-Business-Artifacts)
Enable External Input and connect to Results

H. New Strategy - UpsellSquadZoneForOffer (RS: AOMFW-Business-Artifacts)
Save existing strategy IdentifyEligibleUpselOffers as strategy UpsellSquadZoneForOffer
Remove the filter component “Execute Upsell Proposition Filters“
Connect filter component “Mapped Offers“ to components -
GetOffersForOOBTriggers
ApplyInternationalEligibility
Every other offer


1876
Data Extras
Remove the filter component “Execute Upsell Proposition Filters 1“
Connect filter component “Not TIL or GetNBA“ to Results
Remove the filter component “Execute Upsell Proposition Filters 1 1“
Connect filter component “GetNBA execution mode“ to components -
AddDataExtra
NotAddDataExtra
I. New Strategy - ServiceSquadZoneForOffer (RS: AOMFW-Business-Artifacts)
Save existing strategy IdentifyEligibleServiceOffers as strategy ServiceSquadZoneForOffer
Remove filter component “Execute Service Proposition Filters“
Connect External Input to components -
TIL
Batch & Events

J. New Strategy - RetainSquadZoneForOffer (RS: AOMFW-Business-Artifacts)
Save existing strategy IdentifyEligibleRetainOffers as strategy RetainSquadZoneForOffer
Remove filter component “Retain Offer Eligibility“
Connect External Input to components -
ProcessEvent
NotProcessEvent


1877

K. New Strategy - RenewSquadZoneForOffer (RS: AOMFW-Business-Artifacts)
Save existing strategy IdentifyEligibleRenewOffers as strategy RenewSquadZoneForOffer
Remove filter component “Execute Renew Proposition Filters“
Connect External Input to components -
Offers For ExecutionMode - TIL
Offers For ExecutionMode - Not TIL

L. New Strategy - CrossSellSquadZoneForOffer (RS: AOMFW-Business-Artifacts)
Save existing strategy IdentifyEligibleCrossSellOffers as strategy CrossSellSquadZoneForOffer
Remove filter component “CrossSellEligibility“
Connect External Input to components -
Execution Mode -Not Landing page
Execution Mode-LandingPages


1878

M. New Strategy - RetentionSquadZoneForOffer (RS: AOMFW-Business-Artifacts)
Save existing strategy IdentifyEligibleRetentionOffers as strategy RetentionSquadZoneForOffer
Remove filter component “Retention Offer Eligibility“
Connect following components to Results-
Marketing flags check
Execution Mode-LandingPages

N. New Strategy - ApplyOfferSquadEligibility (RS: AOMFW-Artifacts)
Enable External Input
Add following filters after External Input
“TradeIn” with condition as - @equalsIgnoreCase(.BusinessPurpose,TradeIn)
“UpSell” with condition as - @equalsIgnoreCase(.BusinessPurpose,UpSell)
“Retention” with condition as - @equalsIgnoreCase(.BusinessPurpose,Retention)
“Service” with condition as - @equalsIgnoreCase(.BusinessPurpose,Service)
“Retain” with condition as - @equalsIgnoreCase(.BusinessPurpose,Retain)
“Renew” with condition as - @equalsIgnoreCase(.BusinessPurpose,Renew)
“CrossSell” with condition as - @equalsIgnoreCase(.BusinessPurpose,CrossSell)
“Care” with condition as - @equalsIgnoreCase(.BusinessPurpose,Care)
“Engagement” with condition as - @equalsIgnoreCase(.BusinessPurpose,Engagement)
“HBB” with condition as - @equalsIgnoreCase(.BusinessPurpose,HBB)
“Loyalty” with condition as - @equalsIgnoreCase(.BusinessPurpose,Loyalty)
Add following sub-strategy components after Squad based filters as created above respectively -
TradeInSquadZoneForOffer
CareSquadZoneForOffer
EngagementSquadZoneForOffer
HBBSquadZoneForOffer


1879
LoyaltySquadZoneForOffer
UpsellSquadZoneForOffer
ServiceSquadZoneForOffer
RetainSquadZoneForOffer
RenewSquadZoneForOffer
CrossSellSquadZoneForOffer
RetentionSquadZoneForOffer
Connect the sub-strategy components to results

O. New Strategy - ApplyOfferSquadEligibilityForSimulation (RS: AOMFW-Artifacts)
Enable External Input
Add Sub-strategy component ApplyOfferSquadEligibility after External Input
Add set property component “Reset Tags For Matching“ after External Input and set -
ValueInteger = 0
AdhocText1 = NULL
Add data join component “Match Eligible Propositions“ after set property component “Reset Tags For Matching“
Join with Sub-strategy component ApplyOfferSquadEligibility
Join on pyName
Do not Exclude
Map Properties
ValueInteger = 1
Add set property component “Record Dropped Propositions“ after data join component “Match Eligible Propositions“ and set -
AdhocText1 = @if(.ValueInteger=1,"",@AOMUtilities.CaptureSimulationDropOff("Offer Squad Eligibility",myStepPage))
Add filter component “Eligible Propositions“ with condition - .ValueInteger=1


1880
Add switch component “Simulation Mode Check“
Select "Eligible Propositions" if @String.equalsIgnoreCase(Primary.Context(SimulationMode),"true")
Otherwise, select "ApplyOfferSquadEligibility"
Connect switch component “Simulation Mode Check“ to Results

P. New Strategy - ApplyOfferEligibility (RS: AOMFW-Artifacts)
Enable External Input
Add sub-strategy component ApplyOfferCoreEligibilityForSimulation after External Input
Add sub-strategy component ApplyOfferSquadEligibilityForSimulation after sub-strategy component
ApplyOfferCoreEligibilityForSimulation
Connect sub-strategy component ApplyOfferSquadEligibilityForSimulation to Results

Q. Update Strategy - IdentifyEligibleOffers
Remove the following components (as highlighted below) -
IdentifyEligibleRetentionOffers
IdentifyEligibleRenewOffers
IdentifyEligibleUpsellOffers
IdentifyEligibleCrossSellOffers
IdentifyEligibleTradeInOffers
IdentifyEligibleRetainOffers
IdentifyEligibleServiceOffers
IdentifyEligibleCareOffers
IdentifyEligibleEngagementOffers
IdentifyEligibleLoyaltyOffers
IdentifyEligibleHBBOffers


1881
“TradeIn”
“UpSell”
“Retention”
“Service”
“Retain”
“Renew”
“CrossSell”
“Care”
“Engagement”
“HBB”
“Loyalty”
Reset Tags For Matching
Match Eligible Propositions
Record Dropped Propositions
Eligible Propositions
Eligible Offers
Simulation Mode Check
Add sub-strategy component ApplyOfferEligibility after sub-strategy component TestCellManagement
Connect sub-strategy component ApplyOfferEligibility to set property component “set execution Mode“
Connect sub-strategy component SetOfferLevelPropensity to Results

R. Withdraw Strategies
IdentifyEligibleRetentionOffers
IdentifyEligibleRenewOffers
IdentifyEligibleUpsellOffers


1882
IdentifyEligibleCrossSellOffers
IdentifyEligibleTradeInOffers
IdentifyEligibleRetainOffers
IdentifyEligibleServiceOffers
IdentifyEligibleCareOffers
IdentifyEligibleEngagementOffers
IdentifyEligibleLoyaltyOffers
IdentifyEligibleHBBOffers
S. Update Data - simulation_funnel_ref
This will be used by the post-processing for Customer Simulation
1 Offer Offers By Eligible
IntentsOffersByEligibleIn
tentsY Y Y
2 Offer Global Eligibility
For BatchGlobalEligibilityFo
rBatchY
3 Offer Control Group
ContentionControlGroupCon
tentionY Y Y
4 Offer Offer Eligibility OfferEligibility Y Y Y
4 Offer Offer Core
EligibilityOfferCoreEligibilit
yY Y Y
5 Offer Offer Squad
EligibilityOfferSquadEligibi
lityY Y Y
6 OfferVariant Offer Variant
EligibilityOfferVariantEligibi
lityY Y Y
7 OfferVariant Pick Best Offer
VariantPickBestOfferVari
antY Y Y
8 Treatment Global Contact
Strategy No
BundlingGlobalContactStr
ategyNoBundlingY
9 Treatment Business
Purpose Contact
Strategy No
BundlingBusinessPurpose
ContactStrategyN
oBundlingY
10 Treatment Offer Self
Contention
Strategy No
BundlingOfferSelfContenti
onStrategyNoBun
dlingY Y Y
11 Treatment Run time Volume
Capacity CheckRuntimeVolumeC
apacityCheckY
12 Treatment Channel EligibilityChannelEligibilityY Y Yfunnel_order funnel_level funnel_step funnel_flag batchnba getnba til


1883
 13 Treatment Channel
ContentionChannelContenti
onY Y Y
14 Treatment Treatment
EligibilityTreatmentEligibilit
yY Y Y
15 Treatment Pick Best
Treatments For
OfferPickBestTreatme
ntsForOfferY  Y
16 Treatment Global Contact
Strategy BundlingGlobalContactStr
ategyBundlingY
17 Treatment Business
Purpose Contact
Strategy BundlingBusinessPurpose
ContactStrategyB
undlingY
18 Treatment Offer Self
Contention
Strategy BundlingOfferSelfContenti
onStrategyBundli
ngY
19 Treatment Bundled
TreatmentBundledTreatmen
tY
20 Treatment Pick Best
Treatment For
CustomerPickBestTreatme
ntForCustomerY Y Y
21 TreatmentVariantTreatment Variant
EligibilityTreatmentVariant
EligibilityY Y Y
22 TreatmentVariantPick Best
Treatment Variant
By TreatmentPickBestTreatme
ntVariantByTreat
mentY Y Y
23 TreatmentVariantPick Best
Treatment Variant
For CustomerPickBestTreatme
ntVariantForCust
omerY Y Y
24 TreatmentVariantFinal Selection FinalSelection Y Y Y


1884
Customer Simulation - Offer Variant Eligibility split

Impact in Other areas
Dependencies
Logic Changes
A. New Strategy - ApplyOf ferVariantCoreEligibility (RS: AOMFW -Artifacts)
B. New Strategy - ApplyOf ferVariantCoreEligibilityForSimulation (RS: AOMFW -Artifacts)
C. New Strategy - TradeInSquadZoneForOf ferVariant (RS: AOMFW -Business-Artifacts)
D. New Strategy - RetentionSquadZoneForOf ferVariant (RS: AOMFW -Business-Artifacts)
E. New Strategy - RetainSquadZoneForOf ferVariant (RS: AOMFW -Business-Artifacts)
F. New Strategy - RenewSquadZoneForOf ferVariant (RS: AOMFW -Business-Artifacts)
G. New Strategy - CrossSellSquadZoneForOf ferVariant (RS: AOMFW -Business-Artifacts)
H. New Strategy - CareSquadZoneForOf ferVariant (RS: AOMFW -Business-Artifacts)
I. New Strategy - EngagementSquadZoneForOf ferVariant (RS: AOMFW -Business-Artifacts)
J. New Strategy - HBBSquadZoneForOf ferVariant (RS: AOMFW -Business-Artifacts)
K. New Strategy - LoyaltySquadZoneForOf ferVariant (RS: AOMFW -Business-Artifacts)
L. New Strategy - UpsellSquadZoneForOf ferVariant (RS: AOMFW -Business-Artifacts)
M. New Strategy - ServiceSquadZoneForOf ferVariant (RS: AOMFW -Business-Artifacts)
N. New Strategy - ApplyOf ferVariantSquadEligibility (RS: AOMFW -Artifacts)


O. New Strategy - ApplyOf ferVariantSquadEligibilityForSimulation (RS: AOMFW -Artifacts)
P. New Strategy - ApplyOf ferVariantEligibility (RS: AOMFW -Artifacts)
Q. Update Strategy - IdentifyOf ferVariantsForEligibleOf fers
R. Withdraw Strategies
S. Update Data - simulation_funnel_ref

Impact in Other areas
Dependencies977166 Separate Squad Zones From Standard Offer Variant Eligibility
PM Tool No
PM Tool KT Documentation No
Knowledge Transfer No
App Yes App Versioning
DB Yes  Update funnel audit and post processing Area Yes/No Comments
Area Yes/No Comments


1885

Logic Changes
A. New Strategy - ApplyOfferVariantCoreEligibility (RS: AOMFW-Artifacts)
Enable External Input
Add following filters after External Input
“TradeIn” with condition as - @equalsIgnoreCase(.pyIssue,TradeIn)
“UpSell” with condition as - @equalsIgnoreCase(.pyIssue,UpSell)
“Retention” with condition as - @equalsIgnoreCase(.pyIssue,Retention)
“Service” with condition as - @equalsIgnoreCase(.pyIssue,Service)
“Retain” with condition as - @equalsIgnoreCase(.pyIssue,Retain)
“Renew” with condition as - @equalsIgnoreCase(.pyIssue,Renew)
“CrossSell” with condition as - @equalsIgnoreCase(.pyIssue,CrossSell)
“Care” with condition as - @equalsIgnoreCase(.pyIssue,Care)
“Engagement” with condition as - @equalsIgnoreCase(.pyIssue,Engagement)
“HBB” with condition as - @equalsIgnoreCase(.pyIssue,HBB)
“Loyalty” with condition as - @equalsIgnoreCase(.pyIssue,Loyalty)
Add following filters after Squad based filters as created above respectively -
“Execute TradeIn Proposition Filter” using proposition filter - TradeInOfferVariationsEligibility
“Execute UpSell Proposition Filter” using proposition filter - UpSellOfferVariationsEligibility
“Execute Retention Proposition Filter” using proposition filter - RetentionOfferVariationsEligibility
“Execute Service Proposition Filter” using proposition filter - ServiceOfferVariationsEligibility
“Execute Retain Proposition Filter” using proposition filter - RetainOfferVariationsEligibility
“Execute Renew Proposition Filter” using proposition filter - RenewOfferVariationsEligibility
“Execute CrossSell Proposition Filter” using proposition filter - CrossSellOfferVariationsEligibility
“Execute Care Proposition Filter” using proposition filter - CareOfferVariationsEligibility


“Execute Care Proposition Filter” using proposition filter - CareOfferVariationsEligibility
“Execute Engagement Proposition Filter” using proposition filter - EngagementOfferVariationsEligibility
“Execute HBB Proposition Filter” using proposition filter - HBBOfferVariationsEligibility
“Execute Loyalty Proposition Filter” using proposition filter - LoyaltyOfferVariationsEligibility
Connect the following filters to results
“Execute TradeIn Proposition Filter”
“Execute UpSell Proposition Filter”
“Execute Retention Proposition Filter”
“Execute Service Proposition Filter”
“Execute Retain Proposition Filter”
“Execute Renew Proposition Filter”
“Execute CrossSell Proposition Filter”
“Execute Care Proposition Filter”
“Execute Engagement Proposition Filter”PM Tool No
App Yes
DB Yes


1886
“Execute HBB Proposition Filter”
“Execute Loyalty Proposition Filter”
B. New Strategy - ApplyOfferVariantCoreEligibilityForSimulation (RS: AOMFW-Artifacts)
Enable External Input
Add Sub-strategy component ApplyOfferVariantCoreEligibility after External Input
Add set property component “Reset Tags For Matching“ after External Input and set -
ValueInteger = 0
AdhocText1 = NULL
Add data join component “Match Eligible Propositions“ after set property component “Reset Tags For Matching“
Join with Sub-strategy component ApplyOfferVariantCoreEligibility
Join on pyName
Do not Exclude
Map Properties
ValueInteger = 1
Add set property component “Record Dropped Propositions“ after data join component “Match Eligible Propositions“ and set -
AdhocText1 = @if(.ValueInteger=1,"",@AOMUtilities.CaptureSimulationDropOff("Offer Variant Core Eligibility",myStepPage))
Add filter component “Eligible Propositions“ with condition - .ValueInteger=1
Add switch component “Simulation Mode Check“
Select "Eligible Propositions" if @String.equalsIgnoreCase(Primary.Context(SimulationMode),"true")
Otherwise, select "ApplyOfferVariantCoreEligibility"
Connect switch component “Simulation Mode Check“ to Results


1887

C. New Strategy - TradeInSquadZoneForOfferVariant (RS: AOMFW-Business-Artifacts)
Enable External Input and connect to Results

D. New Strategy - RetentionSquadZoneForOfferVariant (RS: AOMFW-Business-Artifacts)
Enable External Input and connect to Results

E. New Strategy - RetainSquadZoneForOfferVariant (RS: AOMFW-Business-Artifacts)
Enable External Input and connect to Results


1888

F. New Strategy - RenewSquadZoneForOfferVariant (RS: AOMFW-Business-Artifacts)
Enable External Input and connect to Results

G. New Strategy - CrossSellSquadZoneForOfferVariant (RS: AOMFW-Business-Artifacts)
Enable External Input and connect to Results

H. New Strategy - CareSquadZoneForOfferVariant (RS: AOMFW-Business-Artifacts)
Enable External Input and connect to Results


1889

I. New Strategy - EngagementSquadZoneForOfferVariant (RS: AOMFW-Business-Artifacts)
Enable External Input and connect to Results

J. New Strategy - HBBSquadZoneForOfferVariant (RS: AOMFW-Business-Artifacts)
Enable External Input and connect to Results

K. New Strategy - LoyaltySquadZoneForOfferVariant (RS: AOMFW-Business-Artifacts)
Enable External Input and connect to Results


1890
L. New Strategy - UpsellSquadZoneForOfferVariant (RS: AOMFW-Business-Artifacts)
Save existing strategy ApplyUpsellOfferVariationsEligibility as strategy UpsellSquadZoneForOfferVariant
Remove the following components (highlighted below) -
Type - Offers Data
Upsell OfferToOfferVariations
UpSell OfferVariations
Active Offer To Offer Variations1
Active Offer Variations
Get Business Purpose
Identify Active Offer Variations For Offer
Offer Variation ProductCode Check Against ProductHolding
Execute Offer Variations Proposition Filter for eligibility check
Type - Offer To Offer Variations Data
Type - Offer Variations Data
Apply OfferData To OfferToOfferVariations
Apply OfferToOfferVariations Data To OfferVariations
Unique List Of Offer Variants
Connect External Input to following components -
GetNBA Mode
Batch and Events variants
Batch
TIL only


1891
M. New Strategy - ServiceSquadZoneForOfferVariant (RS: AOMFW-Business-Artifacts)
Save existing strategy ApplyUpsellOfferVariationsEligibility as strategy UpsellSquadZoneForOfferVariant
Remove the following components (highlighted below) -
Type - Offers Data
Service OfferToOfferVariations
Service OfferVariations
Active Offer To Offer Variations1
Active Offer Variations
Get Business Purpose
Identify Active Offer Variations For Offer
Offer Variation ProductCode Check Against ProductHolding
Execute Offer Variations Proposition Filter for eligibility check
Type - Offer To Offer Variations Data
Type - Offer Variations Data
Apply OfferData To OfferToOfferVariations
Apply OfferToOfferVariations Data To OfferVariations
Unique List Of Offer Variants


1892
Connect External Input to following components -
Batch and Events variants
TIL only

N. New Strategy - ApplyOfferVariantSquadEligibility (RS: AOMFW-Artifacts)
Enable External Input
Add following filters after External Input
“TradeIn” with condition as - @equalsIgnoreCase(.BusinessPurpose,TradeIn)
“UpSell” with condition as - @equalsIgnoreCase(.BusinessPurpose,UpSell)
“Retention” with condition as - @equalsIgnoreCase(.BusinessPurpose,Retention)
“Service” with condition as - @equalsIgnoreCase(.BusinessPurpose,Service)
“Retain” with condition as - @equalsIgnoreCase(.BusinessPurpose,Retain)
“Renew” with condition as - @equalsIgnoreCase(.BusinessPurpose,Renew)
“CrossSell” with condition as - @equalsIgnoreCase(.BusinessPurpose,CrossSell)
“Care” with condition as - @equalsIgnoreCase(.BusinessPurpose,Care)
“Engagement” with condition as - @equalsIgnoreCase(.BusinessPurpose,Engagement)


1893
“HBB” with condition as - @equalsIgnoreCase(.BusinessPurpose,HBB)
“Loyalty” with condition as - @equalsIgnoreCase(.BusinessPurpose,Loyalty)
Add following sub-strategy components after Squad based filters as created above respectively -
TradeInSquadZoneForOfferVariant
CareSquadZoneForOfferVariant
EngagementSquadZoneForOfferVariant
HBBSquadZoneForOfferVariant
LoyaltySquadZoneForOfferVariant
UpsellSquadZoneForOfferVariant
ServiceSquadZoneForOfferVariant
RetainSquadZoneForOfferVariant
RenewSquadZoneForOfferVariant
CrossSellSquadZoneForOfferVariant
RetentionSquadZoneForOfferVariant
Connect the sub-strategy components to results


1895

O. New Strategy - ApplyOfferVariantSquadEligibilityForSimulation (RS: AOMFW-Artifacts)
P. New Strategy - ApplyOfferVariantEligibility (RS: AOMFW-Artifacts)
Save existing strategy ApplyRetentionOfferVariationsEligibility as ApplyOfferVariantEligibility
Rename sub-strategy component “Retention OfferToOfferVariations” to “ImportAllOfferToOfferVariations“ and Uncheck “Specify a
single component within the strategy“ for external strategy ImportAllOfferToOfferVariations
Rename sub-strategy component “Retention OfferVariations” to “ImportAllOfferVariations“ and Uncheck “Specify a single component
within the strategy“ for external strategy ImportAllOfferVariations
Remove filter component “Execute Offer Variations Proposition Filter for eligibility check“
Add sub-strategy component “ApplyOfferVariantCoreEligibilityForSimulation“ after data join component “Identify Active Offer
Variations For Offer“
Update data join component “Get Business Purpose“
Add new join condition - .pyIssue = .pyIssue
Add filter component “Apply Product Holding Check“ with condition as -
@equalsIgnoreCase(.BusinessPurpose,UpSell) || @equalsIgnoreCase(.BusinessPurpose,Retention) ||
@equalsIgnoreCase(.BusinessPurpose,Service) || @equalsIgnoreCase(.BusinessPurpose,Retain) ||
@equalsIgnoreCase(.BusinessPurpose,CrossSell) || @equalsIgnoreCase(.BusinessPurpose,Care) ||
@equalsIgnoreCase(.BusinessPurpose,Engagement) || @equalsIgnoreCase(.BusinessPurpose,HBB) ||
@equalsIgnoreCase(.BusinessPurpose,Loyalty)
Add filter component “Do Not Apply Product Holding Check“ with condition as -
@equalsIgnoreCase(.BusinessPurpose,TradeIn) || @equalsIgnoreCase(.BusinessPurpose,Renew)


@equalsIgnoreCase(.BusinessPurpose,TradeIn) || @equalsIgnoreCase(.BusinessPurpose,Renew)
Add sub-strategy component “OfferVariationProductCodeCheckAgainstProductHolding“ after filter component “Apply Product
Holding Check“
Connect sub-strategy component “OfferVariationProductCodeCheckAgainstProductHolding“ to set property component “Type -
Offer To Offer Variations Data“
Connect filter component “Do Not Apply Product Holding Check“ to set property component “Type - Offer To Offer Variations Data“
Update group by component “Unique List Of Offer Variants“
Add .pyIssue to Group output rows by
Update data join component “Identify Active Offer Variations For Offer“
Add new join condition - .pyIssue = .pyIssue
Disconnect sub-strategy component “Apply OfferToOfferVariations Data To OfferVariations“ from Results


1896
Add sub-strategy component “ApplyOfferVariantSquadEligibilityForSimulation“ after sub-strategy component “Apply
OfferToOfferVariations Data To OfferVariations“
Connect sub-strategy component “ApplyOfferVariantSquadEligibilityForSimulation“ to Results
Q. Update Strategy - IdentifyOfferVariantsForEligibleOffers
Remove following components (highlighted below) -
CrossSell Offer Variations Eligibility
Retain Offer Variations Eligibility
Service Offer Variations Eligibility
Retention Offer Variations Eligibility
Upsell OfferVariations Eligibility
Renew Offer Variations Eligibility
TradeIn OfferVariationsEligibility
Care Offer Variations Eligibility
Engagement Offer Variations Eligibility
Loyalty Offer Variations Eligibility
HBB Offer Variations Eligibility
“TradeIn”
“UpSell”
“Retention”
“Service”
“Retain”
“Renew”
“CrossSell”
“Care”
“Engagement”
“HBB”
“Loyalty”
Reset Tags For Matching
Match Eligible Propositions
Record Dropped Propositions
Eligible Propositions
Eligible Offer Variants
Simulation Mode Check
GetActiveOfferVariationsForOffers


1897
Add sub-strategy component ApplyOfferVariantEligibility after sub-strategy component “Eligible Offers“
Connect sub-strategy component ApplyOfferVariantEligibility to filter component “Offervariant Eligibility“
Connect set property component “Set VariantRank For Each Offer Variants“ to sub-strategy component “Identify Best OfferVariant For
Offer“

R. Withdraw Strategies
ApplyCrossSellOfferVariationsEligibility
ApplyRetainOfferVariationsEligibility
ApplyServiceOfferVariationsEligibility
ApplyRetentionOfferVariationsEligibility
ApplyUpsellOfferVariationsEligibility
ApplyRenewOfferVariationsEligibility
ApplyTradeInOfferVariationsEligibility
ApplyCareOfferVariationsEligibility
ApplyEngagementOfferVariationsEligibility
ApplyLoyaltyOfferVariationsEligibility
ApplyHBBOfferVariationsEligibility
S. Update Data - simulation_funnel_ref
This will be used by the post-processing for Customer Simulation
funnel_order funnel_level funnel_step funnel_flag batchnba getnba til


1898
1 Offer Offers By Eligible
IntentsOffersByEligibleIn
tentsY Y Y
2 Offer Global Eligibility
For BatchGlobalEligibilityFo
rBatchY
3 Offer Control Group
ContentionControlGroupCon
tentionY Y Y
4 Offer Offer Core
EligibilityOfferCoreEligibilit
yY Y Y
5 Offer Offer Squad
EligibilityOfferSquadEligibi
lityY Y Y
6 OfferVariant Offer Variant
EligibilityOfferVariantEligibi
lityY Y Y
6 OfferVariant Offer Variant
Core EligibilityOfferVariantCore
EligibilityY Y Y
7 OfferVariant Offer Variant
Squad EligibilityOfferVariantSqua
dEligibilityY Y Y
8 OfferVariant Pick Best Offer
VariantPickBestOfferVari
antY Y Y
9 Treatment Global Contact
Strategy No
BundlingGlobalContactStr
ategyNoBundlingY
10 Treatment Business
Purpose Contact
Strategy No
BundlingBusinessPurpose
ContactStrategyN
oBundlingY
11 Treatment Offer Self
Contention
Strategy No
BundlingOfferSelfContenti
onStrategyNoBun
dlingY Y Y
12 Treatment Run time Volume
Capacity CheckRuntimeVolumeC
apacityCheckY
13 Treatment Channel EligibilityChannelEligibilityY Y Y
14 Treatment Channel
ContentionChannelContenti
onY Y Y
15 Treatment Treatment
EligibilityTreatmentEligibilit
yY Y Y
16 Treatment Pick Best
Treatments For
OfferPickBestTreatme
ntsForOfferY  Y
17 Treatment Global Contact
Strategy BundlingGlobalContactStr
ategyBundlingY


1899

 18 Treatment Business
Purpose Contact
Strategy BundlingBusinessPurpose
ContactStrategyB
undlingY
19 Treatment Offer Self
Contention
Strategy BundlingOfferSelfContenti
onStrategyBundli
ngY
20 Treatment Bundled
TreatmentBundledTreatmen
tY
21 Treatment Pick Best
Treatment For
CustomerPickBestTreatme
ntForCustomerY Y Y
22 TreatmentVariantTreatment Variant
EligibilityTreatmentVariant
EligibilityY Y Y
23 TreatmentVariantPick Best
Treatment Variant
By TreatmentPickBestTreatme
ntVariantByTreat
mentY Y Y
24 TreatmentVariantPick Best
Treatment Variant
For CustomerPickBestTreatme
ntVariantForCust
omerY Y Y
25 TreatmentVariantFinal Selection FinalSelection Y Y Y


1900
Upgrades - MBB Upgrades Part 3

Impact in Other areas
Logic Changes

A. Update Strategy - GetDeviceList

Make substrategy call to OrderMBBDeviceList and connect to SetRankPositionforSellableDevices
So for Evo only, we will display a dash for upfront cost. For non Evo, we will display a dash for device cost -which will be based on
compatability.
B. New Strategy - OrderMBBDeviceList
Bottom to top
a. From ExternalInput, fiter DeviceType=Tablet then sort the devices in ascending order of the device names. Set Rank for each
devices.
b. From ExternalInput, fiter DeviceType=Laptop then sort the devices in ascending order of the device names. Set Rank for each
devices.
c. From ExternalInput, fiter DeviceType=Gigacube then sort the devices in ascending order of the device names. Set Rank for each
devices.
d. From ExternalInput, fiter DeviceType=Mobile Wi-fi then sort the devices in ascending order of the device names. Set Rank for each
devices.
e. From ExternalInput, fiter DeviceType=Dongle then sort the devices in ascending order of the device names. Set Rank for each
devices.951211 Evo- Building your own Deal for Evo device (Empty slot on
recommended screen)
816023 MBB Toolkit
994600 MBB: Device Tab Ordering in Edit Screen956423 Evo- Deleting an Evo Device from the Edit screen
PM Tool ?? no
PM Tool KT Documentation No  no
App No
DB No  Area Yes/No Comments


1901
From ExternalInput join on device name each flow seperately.
Sort lowest first based on the calculation (refer final priortise component in OrderWatchList)


1902
Upgrades - Retail Channel
 Impact in Other areas
Dependencies
Logic Changes
A. Create New Strategy IdentifyBestUpgradeTreatments
  Create Strategy IdentifyBestUpgradeTreatments
a. Update the Strategy to cater for 3 channels Web, Retail, InboundCC based on the Channel value from the Context as below
         938125 Retail- TNR figure to display on click
962898 Create or Manage Commercial Recommendation in PM Tool for
Retail Agent
938334 Edit screen- New UI to Display both In Store Stock check and
warehouse for Retail Agent938564 Retail logic to Select products - logic to check stock to use both store
and warehouse stock for Retail Agent
PM Tool ??
PM Tool KT Documentation No
Knowledge Transfer No
App No
DB No  Area Yes/No Comments
PM Tool ??
App No
DB No  Area Yes/No Comments


1903

B. Create New Dataflow IdentifyBestUpgradeTreatments
Save as the Data flow IdentifyBestIBCCTreatments to IdentifyBestUpgradeTreatments
Update the Data flow ‘IdentifyBestUpgradeTreatments’ to add new Strategy IdentifyBestUpgradeTreatments in this DF.
Update the dataflow GetAssistedUpgrade, update the first Destination with above new Dataflow 'IdentifyBestUpgradeTreatments'
C. Update the Stratgey IdentifyBestRetailTreatmentsForSubscription
Add ‘CalculateDeal’ SubStratgey Between ‘IdentifyBestTreatmentforSubscription’ and ‘IdentifyTreatmentVariations’
D. Create a new Strategy ‘PopulateOutputPropertiesForReatil’
Add External Input and Add 2 filter
First Filter is for GetNBA and call sub-Strategy ‘PopulateOutputPropertiesForGetNBA’
Second filter is for NBAA and call Sub Strategy ‘PopulateOutputPropertiesForNBAA’


1904
 And connect both to Results
Add this Stratgey in place of ‘PopulateOutputPropertiesForGetNBA’ in ‘IdentifyBestRetailTreatmentsForSubscription’
E. Update Stratgey SetIHForRetail
Update the SetIHForRetail Strategy like SetIHForInboundCC (to setup all IH Data like InboundCC)
F. Update Stratgey GetStockDetails
Update the Component ‘Set Inputs’ and set. StockLocationList
=@if(@equalsIgnoreCase(Primary.Context(Channel),"InboundCC"),”VFWarehouse” ,"VFWarehouse,Stock")


1905
Upgrades - Digital Upgrades Part1 Design
Upgrades –GetRecommendation for Digital upgrades
961221Digital Upgrades Phase 3 - Customer has opted out of data profiling
961276Digital Upgrades Phase 3 - Identify the customer's Pathway
961297Digital Upgrades Phase 3 - Segment Strategy
961306Digital Upgrades Phase 3 - Digital Pick & Mix
961342Digital Upgrades Phase 3 - selecting 3 separate devices from the Big Data Model
961354Digital Upgrades Phase 3 - ensuring that out of stock devices are not being recommended to the Digital Platform
961365Digital Upgrades Phase 3 - Recommend a Tariff for bundle recommendation
961386Digital Upgrades Phase 3 - Selecting the recommended tariff and Discount
961612Digital Upgrades Phase 3 - Being able to manage S15 Logic Recommendations Threshold for the Digital Channel
961631Digital Upgrades Phase 3 - Apply very early upgrades rules
961640Digital Upgrades Phase 3 - Include Promos in the Max Discount Calculations
961645Digital Upgrades Phase 3 - Commercial Recommendation
961651Digital Upgrades Phase 3 - Being able to create Commercial Recommendations for the Digital Channel Only
961659Digital Upgrades Phase 3 - Ensure that Add Ons are not selectable in the Commercial Rec screen if the Digital Channel
has been selected
961668Digital Upgrades Phase 3 -check pathway upgrades eligibility
961683Digital Upgrades Phase 3 - update the Commercial UI (Pilot 1) to include Digital
961691Digital Upgrades Phase 3 - pass VFT offer with the Logic and Commercial Recommendations
961926Digital Upgrades Phase 3 - Recommendation Reasons
961933Digital Upgrades Phase 3 - Recommendation Reasons Logic
961698Digital Upgrades Phase 3 - Update the 'As Is' Plan order list to include the Bundle Rec info
961802Digital Upgrades Phase 3 - Reporting


961802Digital Upgrades Phase 3 - Reporting
961825Digital Upgrades Phase 3 -create a new Logic Triage Parameter to identify that the 1st Plan/Discount combination is
sourced from a Bundle Recommendation961162Digital Upgrades Phase 3 - Bundle Recommendations


1906
HL Requirement:
As part of Digital upgrades, Business wants to use GetRecommendation flow to identify the recommendations. AOM need to
provide up to 3 recommendations same as assisted upgrades logic. Few configuration changes are updated as per Digital
request. And the response structure will be upated as per digital expectations.
3.7/4.1 Digital Upgrades  miro for Digital upgrades design.
Task Dependecy
Update to logic:
Create New Strategy IdentifyBestUpgradeTreatments
Create Strategy IdentifyBestUpgradeTreatments
a. Update the Strategy to cater for 3 channels Web, Retail, InboundCC based on the Channel value from the Context as below
Logic Yes  Logic update to include Roaming data in
data usage panel .
PM Tool No Configuration changes and screen changes
are there.
APP/UI Yes Specific app api level changes required.  Team Task Comments


1907

 Create New Dataflow IdentifyBestUpgradeTreatments
Save as the Data flow IdentifyBestIBCCTreatments to IdentifyBestUpgradeTreatments
Update the Data flow ‘IdentifyBestUpgradeTreatments’ to add new Strategy IdentifyBestUpgradeTreatments in this DF.
Update the dataflow GetAssistedUpgrade, update the first Destination with above new Dataflow 'IdentifyBestUpgradeTreatments'
Update strategy -IdentifyBestWebTreatmentsForSubscritption
existing strategy will be holding only 2nd line pricing for digital channel. We are going to implement/include Upgrades Logic to Web
channel.
Upgrade deal (strategy need to include in the flow. We must include similar to IdentifyBestIBCCTreatmentsForSubscritption. Where we
will get top recommendations and join back with Treatment variations logic based on pathway.
The output of this strategy should match with Getrecommendation api output as per digital request.

Update strategy -PickBestPathWay
If the BUNDLE_TYPE parameter passed through the Detail structure of GetRecommendations, if it is 'SIMO' or 'DEVICE' the pathway
will be defined in accordance with this request.
Budle_type = SIMO, then pathway= SIMO , if it is Device set pathway = device for digital.(check it is handset for AU)


1908
Update strategy -IdentifyLogicRecommendations.
For a Handset pathway will be returned all devices in stock avoiding to propose the same device
manufacturer, model and storage variations. For a SIMO pathway will be returned all sellable and
eligible eShop tariffs
GetRecommendedHandset strategy will be updated.
The line item and child line item structure will be updated along with existing properties. Digital specific logic is added.
Set a newpath for Recommendation Reasons, with new response type = Reasons.
IdentifyRecommendationReasons New strategy to get Recommendation details.
Out put of this strategy should be associated with each line item. Which includes Recommendation Reason
Title/Description/reason/rank.
VFT logic should work AsIs for Digital flow.
Update strategy -GetRecommendedHandset.
Along with the existing logic, we have to dedupe the handsets based on Device Manufacturer, model and memory variants.
Once we have all list of devices,
We need to send only one device with combination manufacturer+model+memory.
Groupby all devices manufacturer+model+memory.
Update Stratgey GetStockDetails
We must send stock details of VFWarehouse and store.
Changes as part of retail should work AsIs.
We have to call warehouse stock for AU and Retail and digital will call store and warehouse.
Update strategy -PopulateOutputpropertiesforNBAA.
This strategy will be included based on the execution mode. In digital flow.
The line item and child lineitem structure will be updated along with existing properties. Digital specific logic is added.
Set a newpath for Recommendation Reasons, with new response type = Reasons.
IdentifyRecommendationReasons New strategy to get Recommendation details.
Output of this strategy should be associated with each line item. Which includes Recommendation Reason


Output of this strategy should be associated with each line item. Which includes Recommendation Reason
Title/Description/reason/rank.
VFT logic should work AsIs for Digital flow.
New strategy - IdentifyRecommendationReasons.
Create a new DD  GetRecommendationReasons, with Trigger/ Title/Description/reason/rank as a attributes.
Please find the logic to apply fo reach trigger.
Set trigger Value when logic is true with the recommendation in respective strategies. And, can be match with DD based on the Trigger.
When Trigger (from strategy) = Trigger from DD
Get all Title/Description/reason/rank as a attributes from DD and apply to the recommendation line item.
A recommendation can have multiple reasons.

Trigger Reason Reason Type Ranking Reason Title Logic to apply in


1909
Commercial
Recommendation
TriggerA special upgrade
offer for youPlan 1 Here’s a phone we
think you’d like /
Here’s a plan we think
you’d likeCommercial
Recommendation
Campaign
Recommendation
TriggerA special upgrade
offer for youPlan 1 Here’s a phone we
think you’d like / Here’s
a plan we think you’d
likeCampaign
Recommendation
Addon Data  TriggerBased on your
current plan’s data
allowancePlan 2 Based on your current
plan’s data allowanceThe data
recommended is
within + or - 10% of
customer’s current
allowance
Data Usage TriggerBased on the
amount of data
you’ve been usingPlan 3 Based on the amount
of data you’ve been
usingThe data
recommended is
within + or - 20% of
current usage and
the
Recommendation
presented is more
than current data
allowance
Roaming Trigger You’ve recently used
roaming - here’s a
plan you might like
with roaming
included.Plan 4 Keep roaming with us Recommendation
includes roaming
as part the Plan
and recent (within
3mths) roaming
usage identified
Entertainment
TriggerYou’ve enjoyed
entertainment with
us before - here’s a
plan you might like
with entertainment
included.Plan 5  Recommendation
includes an
entertainment plan
and the customer
had entertainment
Handset Pathway
TriggerBased on phones
you’ve shown
interest in beforeDevice 6  The customer
pathway is handset
Simo Pathway


interest in beforeDevice 6  The customer
pathway is handset
Simo Pathway
TriggerBased on plans
you’ve shown
interest in beforePlan 7  The customer’
pathway is SIMO
5G Connectivity
TriggerEnjoy 5G speeds,
seamless streaming
and near-instant
connectionsDevice 8  The recommended
device is a 5G
Device   Description strategy


1910
Please find this for attributes to use for logic implementation.Logic for Rec Reasons

Update strategy -SetIHPropertiesforWEB.
Set TriageAttribute as “NorecommendationFound” When we get no recommendations
Make Sure this will load into IHReoprting table. (inform data team/App team to extract DB if needed).

961651Update DD Commercial Recommendations
Structural changes required - a new Attribute Applicable Channel will be introduced into this DD.
so, that we can differentiate Digital Comm. Rec and non-Digital Comm. Rec separately.
961659 (test only ) pm tool will make sure  Addons won't be able to select for Digital Channel. so, logic will work as is. without Addons.

Update strategy -PopulateOutputpropertiesforNBAA. (recommendation reasons)
 each Recommendation reason property should be concatinated and attached to reporting property in json format.
set valuetext = Rectitle:Rectitle, Recreason:Recreason,Recrank:Recrank,RecDescription:RecDescription |
 Rectitle:Rectitle, Recreason:Recreason,Recrank:Recrank,RecDescription:RecDescription (“|” will be delimiter for each rec
reason (with all properties).
then use this function ConvertKeyValuePairsToJSONArray( confirm with app team) to turn it valuetext into json
set rec reasons (new attribute)  = @ConvertKeyValuePairsToJSONArray(value text)

961825 tariff and discount attribute need to load in triage attribute and how to load it is like 112254 (tariffcode)-552245(discount
code).
we have to load only first rec- details.
 ProductDetails we have this already as part of gpl call  in SetIHPropertiesForAllChannels
example: ProductDetails


example: ProductDetails
{TariffId:<Tariifcode> , DiscountId:<DiscountCode>}
 Digital Upgrades - Get Product List Integration (Tariff & Discount)

961612 Update DD S15Threshold
Structural changes required - a new Attribute Applicable Channel will be introduced into this DD.
so, that we can differentiate Digital Comm. Rec and non-Digital Comm. Rec separately.
 NetRevenue TriggerBeen using more
data recently? This
plan could suit your
needs.Plan 9  If Net Rev of the
Rec is  less and we
are recommending
more data than the
current total data
allowance


1911
Upgrades - Device Edit Screen: Do not Recommend the device in the Top 5 if
the device is out of stock
Impact in Other areas
Logic Changes
A. Update Strategy - GetDeviceList

Impact in Other areas
Logic Changes
A. Update Strategy - GetDeviceList
After GroupBy (GroupByManufacturerandProductNamewithlowestRacRank) make substrategy call to GetStockDetails
Add a filter with below condition
//Any status if quantity is more than zero then recommend device
.Quantity > 0 ||
//If GSA fails then recommend device
@String.equalsIgnoreCase(.QuantityStatus,"Stock Details Unavailable") ||
//if Quantity is 0 and status is backpreorderable and backorderable then recommend device
(.Quantity<=0 && (@String.equalsIgnoreCase(.QuantityStatus,"Backpreorderable") ||
@String.equalsIgnoreCase(.QuantityStatus,"Backorderable")))
connect filter to OrderByRankPosition966558 Device Edit Screen: Do not Recommend the device in the Top 5 if
the device is out of stock
PM Tool No
PM Tool KT Documentation No
Knowledge Transfer No
App No
DB No  Area Yes/No Comments


1912
Release 4.01


1913
Expose Loan Spine To Logic

Impact in Other areas
Dependencies
Logic Changes
Create a new Property Loans(check with App team) of type Page List
A. Update Data Flow - PrepareBatchData
Add a new compose at the end and compose with SubscriptionID from Loan table and Customerid from main path.
Add a new dataset import for Loan dataset1009209 Expose Loan Spine To Logic
Area Yes/No Comments
PM Tool No
PM Tool KT Documentation No
Knowledge Transfer No
App Yes
DB No  Area Yes/No Comments
PM Tool No
App Yes
DB No  Area Yes/No Comments


1914

B. Update Data Flow - PrepareDataForGetRecommendation
Add a new compose at the end and compose with SubscriptionID from Loan table and Customerid from main path.
Add a new dataset import for Loan dataset


1915
C. Update Data Flow - PrepareRealtimeDataForTILSimulation
Add a new compose at the end and compose with SubscriptionID from Loan table and Customerid from main path.
Add a new dataset import for Loan dataset


1916
D. Update Data Flow - PrepareRealtimeDataForGetNBASimulation
Add a new compose at the end and compose with SubscriptionID from Loan table and Customerid from main path.
Add a new dataset import for Loan dataset


1917
E. Update Data Flow - PrepareRealtimeData
Add a new compose at the end and compose with SubscriptionID from Loan table and Customerid from main path.
Add a new dataset import for Loan dataset


1918
F. Update Data Flow - PrepareRealtimeDataForProcessEvent
Add a new compose at the end and compose with SubscriptionID from Loan table and Customerid from main path.
Add a new dataset import for Loan dataset


1920
Align 2nd Line Propositions with EVO 2.0

Impact in Other areas
Dependencies
Logic Changes

Offer Catalogue for Evo 2.0 changes
A. Update Decision Table - EvaluateTariffType
Update EvaluateTariffType table as below. make sure below order is followed in the Table1001585 Align 2nd Line Propositions with EVO 2.0
Area Yes/No Comments
PM Tool No
PM Tool KT Documentation No
Knowledge Transfer No
App No
DB No  Area Yes/No Comments
Area Yes/No Comments
PM Tool No
App No
DB No  Area Yes/No Comments
OfferCatalogue …
04 Nov 2022, 06:42 AM03.xlsx


1921
B. Update Stratgey - GetAllTariffs
Add a Filter and name it as All MBB SIMO and add below condition and connect to it from 'EvaluateTariffTypes' Decision table
             @String.equalsIgnoreCase(.TariffType,"DataSIMOnly")||@String.equalsIgnoreCase(.TariffType,"Tablet")
Add a SetProperty Merge DataSIMO with Tablet plans and Set as below
                  .TariffType ="DataSIMOnly"
Add a new Datajoin Join Offers with DataSIMO tariffs  and connect from Second Line Offers Filter and Merge DataSIMO with Tablet
plans  SetProperty
and do the Properties mapping similar to 'Join Offers with non SIMO eligible tariffs' Datajoin
and connect it to the results


1923
Customer Simulation - Treatment Eligibility split

Impact in Other areas
Dependencies
Logic Changes
A. New Strategy - ApplyUpSellT reatmentCoreEligibility (RS: AOMFW -Artifacts)
B. New Strategy - ApplyRetentionT reatmentCoreEligibility (RS: AOMFW -Artifacts)
C. New Strategy - ApplyCrossSellT reatmentCoreEligibility (RS: AOMFW -Artifacts)
D. New Strategy - ApplyT radeInT reatmentCoreEligibility (RS: AOMFW -Artifacts)
E. New Strategy - ApplyCareT reatmentCoreEligibility (RS: AOMFW -Artifacts)
F. New Strategy - ApplyEngagementT reatmentCoreEligibility (RS: AOMFW -Artifacts)
G. New Strategy - ApplyHBBT reatmentCoreEligibility (RS: AOMFW -Artifacts)
H. New Strategy - ApplyLoyaltyT reatmentCoreEligibility (RS: AOMFW -Artifacts)
I. New Strategy - ApplyServiceT reatmentCoreEligibility (RS: AOMFW -Artifacts)
J. New Strategy - ApplyRetainT reatmentCoreEligibility (RS: AOMFW -Artifacts)
K. New Strategy - ApplyRenewT reatmentCoreEligibility (RS: AOMFW -Artifacts)
L. New Strategy - ApplyT reatmentCoreEligibility (RS: AOMFW -Artifacts)
M. New Strategy - ApplyT reatmentCoreEligibilityForSimulation (RS: AOMFW -Artifacts)
N. New Strategy - ServiceSquadZoneForT reatment (RS: AOMFW -Business-Artifacts)


O. New Strategy - RetainSquadZoneForT reatment (RS: AOMFW -Business-Artifacts)
P. New Strategy - RenewSquadZoneForT reatment (RS: AOMFW -Business-Artifacts)
Q. New Strategy - CrossSellSquadZoneForT reatment (RS: AOMFW -Business-Artifacts)
R. New Strategy - TradeInSquadZoneForT reatment (RS: AOMFW -Business-Artifacts)
S. New Strategy - CareSquadZoneForT reatment (RS: AOMFW -Business-Artifacts)
T. New Strategy - EngagementSquadZoneForT reatment (RS: AOMFW -Business-Artifacts)
U. New Strategy - HBBSquadZoneForT reatment (RS: AOMFW -Business-Artifacts)
V. New Strategy - LoyaltySquadZoneForT reatment (RS: AOMFW -Business-Artifacts)
W. New Strategy - UpSellSquadZoneForT reatment (RS: AOMFW -Business-Artifacts)
X. New Strategy - RetentionSquadZoneForT reatment (RS: AOMFW -Business-Artifacts)
Y. New Strategy - ApplyT reatmentSquadEligibility (RS: AOMFW -Artifacts)
Z. New Strategy - ApplyT reatmentSquadEligibilityForSimulation (RS: AOMFW -Artifacts)
AA. Update Strategy - ApplyT reatmentEligibility
AB. Update Strategy - IdentifyEligibleAppT reatments
AC. Update Strategy - IdentifyEligibleIBCCT reatments
AD. Update Strategy - IdentifyEligibleRetailT reatments


AD. Update Strategy - IdentifyEligibleRetailT reatments
AE. Update Strategy - IdentifyEligibleT OBiT reatments
AF. Update Strategy - IdentifyEligibleOBT reatments
AG. Update Strategy - IdentifyEligibleT reatmentsByT riggers
AH. Update Strategy - IdentifyEligibleT reatmentsforIVRandSMS
AI. Update Strategy - IdentifyEligibleW ebTreatments
AJ. Withdraw Strategies
 977247 Separate Squad Zones From Standard Treatment Eligibility


1924
Impact in Other areas
Dependencies

Logic Changes
A. New Strategy - ApplyUpSellTreatmentCoreEligibility (RS: AOMFW-Artifacts)
Enable External Input
Add following filters after External Input
MMS Channel with condition as .Channel = “MMS“
RCS Channel with condition as .Channel = “RCS“
SMS Channel with condition as .Channel = “SMS“
OutboundCC Channel with condition as .Channel = “OutboundCC“
Email Channel with condition as .Channel = “Email“
AppPush Channel with condition as .Channel = “AppPush“
DirectMail Channel with condition as .Channel = “DirectMail“
Web Channel with condition as .Channel = “Web“
InboundCC Channel with condition as .Channel = “InboundCC“
Retail Channel with condition as .Channel = “Retail“
IVR  Channel with condition as .Channel = “IVR“
App Channel with condition as .Channel = “App“
Microsite Channel with condition as .Channel = “Microsite“
eCare Channel with condition as .Channel = “eCare“
TOBi  Channel with condition as .Channel = “TOBi“
Add following filters after Channel based filters as created above respectively -
“Apply MMS Treatment Eligibility” using proposition filter - UpsellMMSTreatmentEligibility
“Apply RCS Treatment Eligibility” using proposition filter - UpsellRCSTreatmentEligibility
“Apply SMS Treatment Eligibility” using proposition filter - UpsellSMSTreatmentEligibilityPM Tool No
PM Tool KT Documentation No
Knowledge Transfer No
App Yes App Versioning
DB Yes  Update funnel audit and post processing Area Yes/No Comments
PM Tool No
App Yes
DB Yes  Area Yes/No Comments


1925
“Apply OutboundCC Treatment Eligibility” using proposition filter - UpsellOutboundCCTreatmentEligibility
“Apply Email Treatment Eligibility” using proposition filter - UpsellEmailTreatmentEligibility
“Apply AppPush Treatment Eligibility” using proposition filter - UpsellAppPushTreatmentEligibility
“Apply DirectMail Treatment Eligibility” using proposition filter - UpsellDirectMailTreatmentEligibility
“Apply Web Treatment Eligibility” using proposition filter - UpsellWebTreatmentEligibility
“Apply InboundCC Treatment Eligibility” using proposition filter - UpsellInboundCCTreatmentEligibility
“Apply Retail Treatment Eligibility” using proposition filter - UpsellRetailTreatmentEligibility
“Apply IVR Treatment Eligibility” using proposition filter - UpsellIVRTreatmentEligibility
“Apply App Treatment Eligibility” using proposition filter - UpsellAppTreatmentEligibility
“Apply Microsite Treatment Eligibility” using proposition filter - UpsellMicrositeTreatmentEligibility
“Apply eCare Treatment Eligibility” using proposition filter - UpselleCareTreatmentEligibility
“Apply TOBi Treatment Eligibility” using proposition filter - UpsellTOBiTreatmentEligibility
Connect the following filters to Results
“Apply MMS Treatment Eligibility”
“Apply RCS Treatment Eligibility”
“Apply SMS Treatment Eligibility”
“Apply OutboundCC Treatment Eligibility”
“Apply Email Treatment Eligibility”
“Apply AppPush Treatment Eligibility”
“Apply DirectMail Treatment Eligibility”
“Apply Web Treatment Eligibility”
“Apply InboundCC Treatment Eligibility”
“Apply Retail Treatment Eligibility”
“Apply IVR Treatment Eligibility”
“Apply App Treatment Eligibility”
“Apply Microsite Treatment Eligibility”
“Apply eCare Treatment Eligibility”
“Apply TOBi Treatment Eligibility”


1926
B. New Strategy - ApplyRetentionTreatmentCoreEligibility (RS: AOMFW-Artifacts)
Enable External Input
Add following filters after External Input


1927
MMS Channel with condition as .Channel = “MMS“
RCS Channel with condition as .Channel = “RCS“
SMS Channel with condition as .Channel = “SMS“
OutboundCC Channel with condition as .Channel = “OutboundCC“
Email Channel with condition as .Channel = “Email“
AppPush Channel with condition as .Channel = “AppPush“
DirectMail Channel with condition as .Channel = “DirectMail“
Web Channel with condition as .Channel = “Web“
InboundCC Channel with condition as .Channel = “InboundCC“
Retail Channel with condition as .Channel = “Retail“
IVR  Channel with condition as .Channel = “IVR“
App Channel with condition as .Channel = “App“
Microsite Channel with condition as .Channel = “Microsite“
eCare Channel with condition as .Channel = “eCare“
TOBi  Channel with condition as .Channel = “TOBi“
Add following filters after Channel based filters as created above respectively -
“Apply MMS Treatment Eligibility” using proposition filter - RetentionMMSTreatmentEligibility
“Apply RCS Treatment Eligibility” using proposition filter - RetentionRCSTreatmentEligibility
“Apply SMS Treatment Eligibility” using proposition filter - RetentionSMSTreatmentEligibility
“Apply OutboundCC Treatment Eligibility” using proposition filter - RetentionOutboundCCTreatmentEligibility
“Apply Email Treatment Eligibility” using proposition filter - RetentionEmailTreatmentEligibility
“Apply AppPush Treatment Eligibility” using proposition filter - RetentionAppPushTreatmentEligibility
“Apply DirectMail Treatment Eligibility” using proposition filter - RetentionDirectMailTreatmentEligibility
“Apply Web Treatment Eligibility” using proposition filter - RetentionWebTreatmentEligibility