“Apply Web Treatment Eligibility” using proposition filter - RetentionWebTreatmentEligibility
“Apply InboundCC Treatment Eligibility” using proposition filter - RetentionInboundCCTreatmentEligibility
“Apply Retail Treatment Eligibility” using proposition filter - RetentionRetailTreatmentEligibility
“Apply IVR Treatment Eligibility” using proposition filter - RetentionIVRTreatmentEligibility
“Apply App Treatment Eligibility” using proposition filter - RetentionAppTreatmentEligibility
“Apply Microsite Treatment Eligibility” using proposition filter - RetentionMicrositeTreatmentEligibility
“Apply eCare Treatment Eligibility” using proposition filter - RetentioneCareTreatmentEligibility
“Apply TOBi Treatment Eligibility” using proposition filter - RetentionTOBiTreatmentEligibility
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”


1928
“Apply Microsite Treatment Eligibility”
“Apply eCare Treatment Eligibility”
“Apply TOBi Treatment Eligibility”


1930
C. New Strategy - ApplyCrossSellTreatmentCoreEligibility (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 - CrossSellMMSTreatmentEligibility
“Apply RCS Treatment Eligibility” using proposition filter - CrossSellRCSTreatmentEligibility
“Apply SMS Treatment Eligibility” using proposition filter - CrossSellSMSTreatmentEligibility
“Apply OutboundCC Treatment Eligibility” using proposition filter - CrossSellOutboundCCTreatmentEligibility
“Apply Email Treatment Eligibility” using proposition filter - CrossSellEmailTreatmentEligibility
“Apply AppPush Treatment Eligibility” using proposition filter - CrossSellAppPushTreatmentEligibility


“Apply AppPush Treatment Eligibility” using proposition filter - CrossSellAppPushTreatmentEligibility
“Apply DirectMail Treatment Eligibility” using proposition filter - CrossSellDirectMailTreatmentEligibility
“Apply Web Treatment Eligibility” using proposition filter - CrossSellWebTreatmentEligibility
“Apply InboundCC Treatment Eligibility” using proposition filter - CrossSellInboundCCTreatmentEligibility
“Apply Retail Treatment Eligibility” using proposition filter - CrossSellRetailTreatmentEligibility
“Apply IVR Treatment Eligibility” using proposition filter - CrossSellIVRTreatmentEligibility
“Apply App Treatment Eligibility” using proposition filter - CrossSellAppTreatmentEligibility
“Apply Microsite Treatment Eligibility” using proposition filter - CrossSellMicrositeTreatmentEligibility
“Apply eCare Treatment Eligibility” using proposition filter - CrossSelleCareTreatmentEligibility
“Apply TOBi Treatment Eligibility” using proposition filter - CrossSellTOBiTreatmentEligibility
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”


1931
“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”


1932
D. New Strategy - ApplyTradeInTreatmentCoreEligibility (RS: AOMFW-Artifacts)
Enable External Input
Add following filters after External Input
MMS Channel with condition as .Channel = “MMS“


1933
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 - TradeInMMSTreatmentEligibility
“Apply RCS Treatment Eligibility” using proposition filter - TradeInRCSTreatmentEligibility
“Apply SMS Treatment Eligibility” using proposition filter - TradeInSMSTreatmentEligibility
“Apply OutboundCC Treatment Eligibility” using proposition filter - TradeInOutboundCCTreatmentEligibility
“Apply Email Treatment Eligibility” using proposition filter - TradeInEmailTreatmentEligibility
“Apply AppPush Treatment Eligibility” using proposition filter - TradeInAppPushTreatmentEligibility
“Apply DirectMail Treatment Eligibility” using proposition filter - TradeInDirectMailTreatmentEligibility
“Apply Web Treatment Eligibility” using proposition filter - TradeInWebTreatmentEligibility
“Apply InboundCC Treatment Eligibility” using proposition filter - TradeInInboundCCTreatmentEligibility


“Apply InboundCC Treatment Eligibility” using proposition filter - TradeInInboundCCTreatmentEligibility
“Apply Retail Treatment Eligibility” using proposition filter - TradeInRetailTreatmentEligibility
“Apply IVR Treatment Eligibility” using proposition filter - TradeInIVRTreatmentEligibility
“Apply App Treatment Eligibility” using proposition filter - TradeInAppTreatmentEligibility
“Apply Microsite Treatment Eligibility” using proposition filter - TradeInMicrositeTreatmentEligibility
“Apply eCare Treatment Eligibility” using proposition filter - TradeIneCareTreatmentEligibility
“Apply TOBi Treatment Eligibility” using proposition filter - TradeInTOBiTreatmentEligibility
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”


1934
“Apply eCare Treatment Eligibility”
“Apply TOBi Treatment Eligibility”


1935
E. New Strategy - ApplyCareTreatmentCoreEligibility (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 - CareMMSTreatmentEligibility
“Apply RCS Treatment Eligibility” using proposition filter - CareRCSTreatmentEligibility
“Apply SMS Treatment Eligibility” using proposition filter - CareSMSTreatmentEligibility
“Apply OutboundCC Treatment Eligibility” using proposition filter - CareOutboundCCTreatmentEligibility
“Apply Email Treatment Eligibility” using proposition filter - CareEmailTreatmentEligibility
“Apply AppPush Treatment Eligibility” using proposition filter - CareAppPushTreatmentEligibility
“Apply DirectMail Treatment Eligibility” using proposition filter - CareDirectMailTreatmentEligibility


“Apply DirectMail Treatment Eligibility” using proposition filter - CareDirectMailTreatmentEligibility
“Apply Web Treatment Eligibility” using proposition filter - CareWebTreatmentEligibility
“Apply InboundCC Treatment Eligibility” using proposition filter - CareInboundCCTreatmentEligibility
“Apply Retail Treatment Eligibility” using proposition filter - CareRetailTreatmentEligibility
“Apply IVR Treatment Eligibility” using proposition filter - CareIVRTreatmentEligibility
“Apply App Treatment Eligibility” using proposition filter - CareAppTreatmentEligibility
“Apply Microsite Treatment Eligibility” using proposition filter - CareMicrositeTreatmentEligibility
“Apply eCare Treatment Eligibility” using proposition filter - CareeCareTreatmentEligibility
“Apply TOBi Treatment Eligibility” using proposition filter - CareTOBiTreatmentEligibility
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”


1936
“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”


1938
F. New Strategy - ApplyEngagementTreatmentCoreEligibility (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 - EngagementMMSTreatmentEligibility
“Apply RCS Treatment Eligibility” using proposition filter - EngagementRCSTreatmentEligibility
“Apply SMS Treatment Eligibility” using proposition filter - EngagementSMSTreatmentEligibility
“Apply OutboundCC Treatment Eligibility” using proposition filter - EngagementOutboundCCTreatmentEligibility
“Apply Email Treatment Eligibility” using proposition filter - EngagementEmailTreatmentEligibility
“Apply AppPush Treatment Eligibility” using proposition filter - EngagementAppPushTreatmentEligibility
“Apply DirectMail Treatment Eligibility” using proposition filter - EngagementDirectMailTreatmentEligibility


“Apply DirectMail Treatment Eligibility” using proposition filter - EngagementDirectMailTreatmentEligibility
“Apply Web Treatment Eligibility” using proposition filter - EngagementWebTreatmentEligibility
“Apply InboundCC Treatment Eligibility” using proposition filter - EngagementInboundCCTreatmentEligibility
“Apply Retail Treatment Eligibility” using proposition filter - EngagementRetailTreatmentEligibility
“Apply IVR Treatment Eligibility” using proposition filter - EngagementIVRTreatmentEligibility
“Apply App Treatment Eligibility” using proposition filter - EngagementAppTreatmentEligibility
“Apply Microsite Treatment Eligibility” using proposition filter - EngagementMicrositeTreatmentEligibility
“Apply eCare Treatment Eligibility” using proposition filter - EngagementeCareTreatmentEligibility
“Apply TOBi Treatment Eligibility” using proposition filter - EngagementTOBiTreatmentEligibility
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”


1939
“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”


1941
G. New Strategy - ApplyHBBTreatmentCoreEligibility (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 - HBBMMSTreatmentEligibility
“Apply RCS Treatment Eligibility” using proposition filter - HBBRCSTreatmentEligibility
“Apply SMS Treatment Eligibility” using proposition filter - HBBSMSTreatmentEligibility
“Apply OutboundCC Treatment Eligibility” using proposition filter - HBBOutboundCCTreatmentEligibility
“Apply Email Treatment Eligibility” using proposition filter - HBBEmailTreatmentEligibility
“Apply AppPush Treatment Eligibility” using proposition filter - HBBAppPushTreatmentEligibility


“Apply AppPush Treatment Eligibility” using proposition filter - HBBAppPushTreatmentEligibility
“Apply DirectMail Treatment Eligibility” using proposition filter - HBBDirectMailTreatmentEligibility
“Apply Web Treatment Eligibility” using proposition filter - HBBWebTreatmentEligibility
“Apply InboundCC Treatment Eligibility” using proposition filter - HBBInboundCCTreatmentEligibility
“Apply Retail Treatment Eligibility” using proposition filter - HBBRetailTreatmentEligibility
“Apply IVR Treatment Eligibility” using proposition filter - HBBIVRTreatmentEligibility
“Apply App Treatment Eligibility” using proposition filter - HBBAppTreatmentEligibility
“Apply Microsite Treatment Eligibility” using proposition filter - HBBMicrositeTreatmentEligibility
“Apply eCare Treatment Eligibility” using proposition filter - HBBeCareTreatmentEligibility
“Apply TOBi Treatment Eligibility” using proposition filter - HBBTOBiTreatmentEligibility
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”


1942
“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”


1944
H. New Strategy - ApplyLoyaltyTreatmentCoreEligibility (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 - LoyaltyMMSTreatmentEligibility
“Apply RCS Treatment Eligibility” using proposition filter - LoyaltyRCSTreatmentEligibility
“Apply SMS Treatment Eligibility” using proposition filter - LoyaltySMSTreatmentEligibility
“Apply OutboundCC Treatment Eligibility” using proposition filter - LoyaltyOutboundCCTreatmentEligibility
“Apply Email Treatment Eligibility” using proposition filter - LoyaltyEmailTreatmentEligibility
“Apply AppPush Treatment Eligibility” using proposition filter - LoyaltyAppPushTreatmentEligibility


“Apply AppPush Treatment Eligibility” using proposition filter - LoyaltyAppPushTreatmentEligibility
“Apply DirectMail Treatment Eligibility” using proposition filter - LoyaltyDirectMailTreatmentEligibility
“Apply Web Treatment Eligibility” using proposition filter - LoyaltyWebTreatmentEligibility
“Apply InboundCC Treatment Eligibility” using proposition filter - LoyaltyInboundCCTreatmentEligibility
“Apply Retail Treatment Eligibility” using proposition filter - LoyaltyRetailTreatmentEligibility
“Apply IVR Treatment Eligibility” using proposition filter - LoyaltyIVRTreatmentEligibility
“Apply App Treatment Eligibility” using proposition filter - LoyaltyAppTreatmentEligibility
“Apply Microsite Treatment Eligibility” using proposition filter - LoyaltyMicrositeTreatmentEligibility
“Apply eCare Treatment Eligibility” using proposition filter - LoyaltyeCareTreatmentEligibility
“Apply TOBi Treatment Eligibility” using proposition filter - LoyaltyTOBiTreatmentEligibility
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”


1945
“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”


1947
I. New Strategy - ApplyServiceTreatmentCoreEligibility (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 - ServiceMMSTreatmentEligibility
“Apply RCS Treatment Eligibility” using proposition filter - ServiceRCSTreatmentEligibility
“Apply SMS Treatment Eligibility” using proposition filter - ServiceSMSTreatmentEligibility
“Apply OutboundCC Treatment Eligibility” using proposition filter - ServiceOutboundCCTreatmentEligibility
“Apply Email Treatment Eligibility” using proposition filter - ServiceEmailTreatmentEligibility
“Apply AppPush Treatment Eligibility” using proposition filter - ServiceAppPushTreatmentEligibility
“Apply DirectMail Treatment Eligibility” using proposition filter - ServiceDirectMailTreatmentEligibility


“Apply DirectMail Treatment Eligibility” using proposition filter - ServiceDirectMailTreatmentEligibility
“Apply Web Treatment Eligibility” using proposition filter - ServiceWebTreatmentEligibility
“Apply InboundCC Treatment Eligibility” using proposition filter - ServiceInboundCCTreatmentEligibility
“Apply Retail Treatment Eligibility” using proposition filter - ServiceRetailTreatmentEligibility
“Apply IVR Treatment Eligibility” using proposition filter - ServiceIVRTreatmentEligibility
“Apply App Treatment Eligibility” using proposition filter - ServiceAppTreatmentEligibility
“Apply Microsite Treatment Eligibility” using proposition filter - ServiceMicrositeTreatmentEligibility
“Apply eCare Treatment Eligibility” using proposition filter - ServiceeCareTreatmentEligibility
“Apply TOBi Treatment Eligibility” using proposition filter - ServiceTOBiTreatmentEligibility
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”


1948
“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”


1950
J. New Strategy - ApplyRetainTreatmentCoreEligibility (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 - RetainMMSTreatmentEligibility
“Apply RCS Treatment Eligibility” using proposition filter - RetainRCSTreatmentEligibility
“Apply SMS Treatment Eligibility” using proposition filter - RetainSMSTreatmentEligibility
“Apply OutboundCC Treatment Eligibility” using proposition filter - RetainOutboundCCTreatmentEligibility
“Apply Email Treatment Eligibility” using proposition filter - RetainEmailTreatmentEligibility
“Apply AppPush Treatment Eligibility” using proposition filter - RetainAppPushTreatmentEligibility


“Apply AppPush Treatment Eligibility” using proposition filter - RetainAppPushTreatmentEligibility
“Apply DirectMail Treatment Eligibility” using proposition filter - RetainDirectMailTreatmentEligibility
“Apply Web Treatment Eligibility” using proposition filter - RetainWebTreatmentEligibility
“Apply InboundCC Treatment Eligibility” using proposition filter - RetainInboundCCTreatmentEligibility
“Apply Retail Treatment Eligibility” using proposition filter - RetainRetailTreatmentEligibility
“Apply IVR Treatment Eligibility” using proposition filter - RetainIVRTreatmentEligibility
“Apply App Treatment Eligibility” using proposition filter - RetainAppTreatmentEligibility
“Apply Microsite Treatment Eligibility” using proposition filter - RetainMicrositeTreatmentEligibility
“Apply eCare Treatment Eligibility” using proposition filter - RetaineCareTreatmentEligibility
“Apply TOBi Treatment Eligibility” using proposition filter - RetainTOBiTreatmentEligibility
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”


1951
“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”


1952
K. New Strategy - ApplyRenewTreatmentCoreEligibility (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“


1953
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 - RenewMMSTreatmentEligibility
“Apply RCS Treatment Eligibility” using proposition filter - RenewRCSTreatmentEligibility
“Apply SMS Treatment Eligibility” using proposition filter - RenewSMSTreatmentEligibility
“Apply OutboundCC Treatment Eligibility” using proposition filter - RenewOutboundCCTreatmentEligibility
“Apply Email Treatment Eligibility” using proposition filter - RenewEmailTreatmentEligibility
“Apply AppPush Treatment Eligibility” using proposition filter - RenewAppPushTreatmentEligibility
“Apply DirectMail Treatment Eligibility” using proposition filter - RenewDirectMailTreatmentEligibility
“Apply Web Treatment Eligibility” using proposition filter - RenewWebTreatmentEligibility
“Apply InboundCC Treatment Eligibility” using proposition filter - RenewInboundCCTreatmentEligibility
“Apply Retail Treatment Eligibility” using proposition filter - RenewRetailTreatmentEligibility


“Apply Retail Treatment Eligibility” using proposition filter - RenewRetailTreatmentEligibility
“Apply IVR Treatment Eligibility” using proposition filter - RenewIVRTreatmentEligibility
“Apply App Treatment Eligibility” using proposition filter - RenewAppTreatmentEligibility
“Apply Microsite Treatment Eligibility” using proposition filter - RenewMicrositeTreatmentEligibility
“Apply eCare Treatment Eligibility” using proposition filter - ReneweCareTreatmentEligibility
“Apply TOBi Treatment Eligibility” using proposition filter - RenewTOBiTreatmentEligibility
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”


1954
“Apply TOBi Treatment Eligibility”


1956
L. New Strategy - ApplyTreatmentCoreEligibility (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 -
ApplyTradeInTreatmentCoreEligibility
ApplyCareTreatmentCoreEligibility
ApplyEngagementTreatmentCoreEligibility
ApplyHBBTreatmentCoreEligibility
ApplyLoyaltyTreatmentCoreEligibility
ApplyUpsellTreatmentCoreEligibility
ApplyServiceTreatmentCoreEligibility
ApplyRetainTreatmentCoreEligibility
ApplyRenewTreatmentCoreEligibility
ApplyCrossSellTreatmentCoreEligibility
ApplyRetentionTreatmentCoreEligibility
Connect the sub-strategy components to results


1957
M. New Strategy - ApplyTreatmentCoreEligibilityForSimulation (RS: AOMFW-Artifacts)
Enable External Input
Add Sub-strategy component ApplyTreatmentCoreEligibility after External Input


1958
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 ApplyTreatmentCoreEligibility
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("Treatment 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 "ApplyTreatmentCoreEligibility"
Connect switch component “Simulation Mode Check“ to Results
N. New Strategy - ServiceSquadZoneForTreatment (RS: AOMFW-Business-Artifacts)
Enable External Input and connect to Results
O. New Strategy - RetainSquadZoneForTreatment (RS: AOMFW-Business-Artifacts)
Enable External Input
Add filter component “SMS Channel“ after External Input with condition as - .Channel = “SMS“
Add filter component “Non SMS Channel“ after External Input with condition as - .Channel != “SMS“


1959
Connect filter component “Non SMS Channel“ to Results
Add filter component “ContractEndDate within 210days“ after filter component “SMS Channel“ with condition as -
@if(@String.equalsIgnoreCase(.pyName,"PostToPreMigration"),@CalculateNumberOfDaysFromToday(Primary.LatestContractEndDate
)>=-210,true)
Connect filter component “ContractEndDate within 210days“ to Results
P. New Strategy - RenewSquadZoneForTreatment (RS: AOMFW-Business-Artifacts)
Enable External Input and connect to Results
Q. New Strategy - CrossSellSquadZoneForTreatment (RS: AOMFW-Business-Artifacts)
Save existing strategy ApplyCrossSellTreatmentEligibility as strategy CrossSellSquadZoneForTreatment
Update switch component “Prioritise By Channel“ as follows -
Select component “Apply Email Treatment Eligibility Filter No HBB“ if
EmailTreatments.pyName!=""
Select component “Apply SMS Treatment Eligibility Filter No HBB 1“ if
SMSChannel.pyName!=""
Select component “AppPush Channel“ if
AppPushChannel.pyName!=""
Disconnect filter component “Apply SMS Treatment Eligibility Filter“ from components
“Apply SMS Treatment Eligibility Filter No HBB 1”
“HBB“
Connect filter component “SMS Channel“ to components
“Apply SMS Treatment Eligibility Filter No HBB 1”
“HBB“
Disconnect filter component “Apply OutboundCC Treatment Eligibility Filter“ from components
“Apply OutboundCC Treatment Eligibility Filter No HBB”


1960
“HBB“
Connect filter component “OutboundCC Channel“ to components
“Apply OutboundCC Treatment Eligibility Filter No HBB”
“HBB“
Disconnect filter component “Apply Email Treatment Eligibility Filter“ from components
“Apply Email Treatment Eligibility Filter No HBB”
“HBB“
Connect filter component “OutboundCC Channel“ to components
“Apply Email Treatment Eligibility Filter No HBB”
“HBB“
Select the following components (as highlighted below) -
MMS Channel
Apply MMS TreatmentEligibility
RCS Channel
CrossSellRCSTreatmentEligibility
Apply SMS Treatment Eligibility Filter
Apply OutboundCC Treatment Eligibility Filter
Apply Email Treatment Eligibility Filter
Apply AppPush Treatment Eligibility Filter
DirectMail Channel
Apply DirectMail Treatment Eligibility
Web Channel
Apply Web TreatmentEligibility
InboundCC Channel
Apply InboundCC Treatment Eligibility Filter
Retail Channel
Apply Retail Treatment Eligibility
IVR  Channel
Apply IVR Treatment Eligibility Filter
App Channel
Apply App Treatment Eligibility Filter
Microsite Channel
Apply Microsite Treatment Eligibility
eCare Channel
Apply eCare Treatment Eligibility
TOBi  Channel
Apply TOBi Treatment Eligibility


1961
Add filter component “Other Channels“ with condition as -
.Channel != “SMS“ && .Channel != “OutboundCC“ && .Channel != “Email“ && .Channel != “AppPush“
Connect filter component “Other Channels“ to Results

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


1962
S. New Strategy - CareSquadZoneForTreatment (RS: AOMFW-Business-Artifacts)
Enable External Input and connect to Results
T. New Strategy - EngagementSquadZoneForTreatment (RS: AOMFW-Business-Artifacts)
Enable External Input and connect to Results
U. New Strategy - HBBSquadZoneForTreatment (RS: AOMFW-Business-Artifacts)
Enable External Input and connect to Results


1963
V. New Strategy - LoyaltySquadZoneForTreatment (RS: AOMFW-Business-Artifacts)
Enable External Input and connect to Results
W. New Strategy - UpSellSquadZoneForTreatment (RS: AOMFW-Business-Artifacts)
Save existing strategy ApplyUpsellTreatmentEligibility as strategy UpSellSquadZoneForTreatment
Update switch component “Batch mode“ as
Select External Input, Otherwise
Delete components (as highlighted) as below -
MMS Channel
RCS Channel
SMS Channel
OutboundCC Channel
Email Channel
AppPush Channel
DirectMail Channel
Web Channel
InboundCC Channel
Retail Channel
IVR  Channel
App Channel
Microsite Channel
eCare Channel
TOBi  Channel
“Apply MMS Treatment Eligibility”
“Apply RCS Treatment Eligibility”


1964
“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”
[Set Property]
Connect External Input to filter component “Switch Mobile Plan email only or other offers“

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


1965
Y. New Strategy - ApplyTreatmentSquadEligibility (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 -
TradeInSquadZoneForTreatment
CareSquadZoneForTreatment
EngagementSquadZoneForTreatment
HBBSquadZoneForTreatment
LoyaltySquadZoneForTreatment
UpsellSquadZoneForTreatment
ServiceSquadZoneForTreatment
RetainSquadZoneForTreatment
RenewSquadZoneForTreatment
CrossSellSquadZoneForTreatment
RetentionSquadZoneForTreatment
Connect the sub-strategy components to results


1966
Z. New Strategy - ApplyTreatmentSquadEligibilityForSimulation (RS: AOMFW-Artifacts)
Enable External Input
Add Sub-strategy component ApplyTreatmentSquadEligibility 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 ApplyTreatmentSquadEligibility
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("Treatment Squad 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 "ApplyTreatmentSquadEligibility"
Connect switch component “Simulation Mode Check“ to Results


1967
AA. Update Strategy - ApplyTreatmentEligibility
Delete all components excluding External Input
Add sub-strategy component ApplyTreatmentCoreEligibilityForSimulation after External Input
Add sub-strategy component ApplyTreatmentSquadEligibilityForSimulation after sub-strategy component
ApplyTreatmentCoreEligibilityForSimulation
Connect sub-strategy component ApplyTreatmentSquadEligibilityForSimulation to Results
AB. Update Strategy - IdentifyEligibleAppTreatments
Replace sub-strategy component ApplyTreatmentEligibilityForSimulation with sub-strategy component  ApplyTreatmentEligibility


1968
AC. Update Strategy - IdentifyEligibleIBCCTreatments
Replace sub-strategy component ApplyTreatmentEligibilityForSimulation with sub-strategy component  ApplyTreatmentEligibility
AD. Update Strategy - IdentifyEligibleRetailTreatments
Replace sub-strategy component ApplyTreatmentEligibilityForSimulation with sub-strategy component  ApplyTreatmentEligibility
AE. Update Strategy - IdentifyEligibleTOBiTreatments
Replace sub-strategy component ApplyTreatmentEligibilityForSimulation with sub-strategy component  ApplyTreatmentEligibility
AF. Update Strategy - IdentifyEligibleOBTreatments
Replace sub-strategy component ApplyTreatmentEligibilityForSimulation with sub-strategy component  ApplyTreatmentEligibility
AG. Update Strategy - IdentifyEligibleTreatmentsByTriggers
Replace sub-strategy component ApplyTreatmentEligibilityForSimulation with sub-strategy component  ApplyTreatmentEligibility


1969
AH. Update Strategy - IdentifyEligibleTreatmentsforIVRandSMS
Replace sub-strategy component ApplyTreatmentEligibilityForSimulation with sub-strategy component  ApplyTreatmentEligibility
AI. Update Strategy - IdentifyEligibleWebTreatments
Replace sub-strategy component ApplyTreatmentEligibilityForSimulation with sub-strategy component  ApplyTreatmentEligibility
AJ. Withdraw Strategies
ApplyCrossSellTreatmentEligibility
ApplyRenewTreatmentEligibility
ApplyUpsellTreatmentEligibility
ApplyRetainTreatmentEligibility
ApplyServiceTreatmentEligibility
ApplyRetentionTreatmentEligibility
ApplyTradeInTreatmentEligibility
ApplyCareTreatmentEligibility
ApplyEngagementTreatmentEligibility
ApplyLoyaltyTreatmentEligibility
ApplyHBBTreatmentEligibility
ApplyTreatmentEligibilityForSimulation


1970
Customer Simulation - Treatment Variant Eligibility split

Impact in Other areas
Dependencies
Logic Changes
A. New Strategy - ApplyT reatmentV ariationsCoreEligibility (RS: AOMFW -Artifacts)
B. New Strategy - ApplyT reatmentT oTreatmentV ariationsCoreEligibility (RS: AOMFW -Artifacts)
C. New Strategy - ApplyT reatmentV ariantCoreEligibility (RS: AOMFW -Artifacts)
D. New Strategy - ApplyT reatmentV ariantCoreEligibilityForSimulation (RS: AOMFW -Artifacts)
E. New Strategy - TradeInSquadZoneForT reatmentV ariant (RS: AOMFW -Business-Artifacts)
F. New Strategy - UpsellSquadZoneForT reatmentV ariant (RS: AOMFW -Business-Artifacts)
G. New Strategy - RetentionSquadZoneForT reatmentV ariant (RS: AOMFW -Business-Artifacts)
H. New Strategy - ServiceSquadZoneForT reatmentV ariant (RS: AOMFW -Business-Artifacts)
I. New Strategy - RetainSquadZoneForT reatmentV ariant (RS: AOMFW -Business-Artifacts)
J. New Strategy - RenewSquadZoneForT reatmentV ariant (RS: AOMFW -Business-Artifacts)
K. New Strategy - CareSquadZoneForT reatmentV ariant (RS: AOMFW -Business-Artifacts)
L. New Strategy - EngagementSquadZoneForT reatmentV ariant (RS: AOMFW -Business-Artifacts)


M. New Strategy - HBBSquadZoneForT reatmentV ariant (RS: AOMFW -Business-Artifacts)
N. New Strategy - LoyaltySquadZoneForT reatmentV ariant (RS: AOMFW -Business-Artifacts)
O. New Strategy - CrossSellSquadZoneForT reatmentV ariant (RS: AOMFW -Business-Artifacts)
P. New Strategy - ApplyT reatmentV ariantSquadEligibility (RS: AOMFW -Artifacts)
Q. New Strategy - ApplyT reatmentV ariantSquadEligibilityForSimulation (RS: AOMFW -Artifacts)
R. New Strategy - ApplyT reatmentV ariantEligibility (RS: AOMFW -Artifacts)
S. Update Strategy - IdentifyT reatmentV ariations
T. Withdraw Strategies

Impact in Other areas
Dependencies977272 Separate Squad Zones From Standard Treatment 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


1971

NOTE: Need to validate with Matt
if T2TVContention needs a new Simulation Funnel
if TV Additional Check needs a new Simulation Funnel
Logic Changes
A. New Strategy - ApplyTreatmentVariationsCoreEligibility (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 - TradeInTreatmentVariationsEligibility
“Execute UpSell Proposition Filter” using proposition filter - UpSellTreatmentVariationsEligibility
“Execute Retention Proposition Filter” using proposition filter - RetentionTreatmentVariationsEligibility
“Execute Service Proposition Filter” using proposition filter - ServiceTreatmentVariationsEligibility
“Execute Retain Proposition Filter” using proposition filter - RetainTreatmentVariationsEligibility
“Execute Renew Proposition Filter” using proposition filter - RenewTreatmentVariationsEligibility


“Execute Renew Proposition Filter” using proposition filter - RenewTreatmentVariationsEligibility
“Execute CrossSell Proposition Filter” using proposition filter - CrossSellTreatmentVariationsEligibility
“Execute Care Proposition Filter” using proposition filter - CareTreatmentVariationsEligibility
“Execute Engagement Proposition Filter” using proposition filter - EngagementTreatmentVariationsEligibility
“Execute HBB Proposition Filter” using proposition filter - HBBTreatmentVariationsEligibility
“Execute Loyalty Proposition Filter” using proposition filter - LoyaltyTreatmentVariationsEligibility
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”PM Tool No
App Yes
DB Yes


1972
“Execute Renew Proposition Filter”
“Execute CrossSell Proposition Filter”
“Execute Care Proposition Filter”
“Execute Engagement Proposition Filter”
“Execute HBB Proposition Filter”
“Execute Loyalty Proposition Filter”
B. New Strategy - ApplyTreatmentToTreatmentVariationsCoreEligibility (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 - TradeInTreatmentToTreatmentVariationEligibility


1973
“Execute UpSell Proposition Filter” using proposition filter - UpSellTreatmentToTreatmentVariationEligibility
“Execute Retention Proposition Filter” using proposition filter - RetentionTreatmentToTreatmentVariationEligibility
“Execute Service Proposition Filter” using proposition filter - ServiceTreatmentToTreatmentVariationEligibility
“Execute Retain Proposition Filter” using proposition filter - RetainTreatmentToTreatmentVariationEligibility
“Execute Renew Proposition Filter” using proposition filter - RenewTreatmentToTreatmentVariationEligibility
“Execute CrossSell Proposition Filter” using proposition filter - CrossSellTreatmentToTreatmentVariationEligibility
“Execute Care Proposition Filter” using proposition filter - CareTreatmentToTreatmentVariationEligibility
“Execute Engagement Proposition Filter” using proposition filter - EngagementTreatmentToTreatmentVariationEligibility
“Execute HBB Proposition Filter” using proposition filter - HBBTreatmentToTreatmentVariationEligibility
“Execute Loyalty Proposition Filter” using proposition filter - LoyaltyTreatmentToTreatmentVariationEligibility
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”
“Execute HBB Proposition Filter”
“Execute Loyalty Proposition Filter”


1974
C. New Strategy - ApplyTreatmentVariantCoreEligibility (RS: AOMFW-Artifacts)
Save existing strategy IdentifyTradeInTreatmentVariations as Strategy ApplyTreatmentVariantCoreEligibility
Delete following components (as highlighted below) -
TradeIn TreatmentToTreatmentVariations
Active
Identify Treatment Variants For Treatment
Apply FUT Check
Get TradeIn Propositions From Treatment Variants Group
Apply TradeIn TreatmentToTreatmentVariation  Proposition Filter
Type - Treatment To Treatment Variations Data
Apply TradeIn Treatment Variant Proposition Filter
Type - Treatments Data
ApplyTreatmentToTreatmentVariationsDataToTreatments
Add filter component “Treatment To Treatment Variations Data“ after External Input with condition as -
Type = “Treatment To Treatment Variations Data“
Connect filter component “Treatment To Treatment Variations Data“ to components -
Eligible Treatment Variations Treatments
Unique List of Treatment Variants
Add filter component “Treatment Variations Data“ after External Input with condition as -
Type = “Treatment Variations Data“
filter component “Treatment Variations Data“ to data join component “Identify Active Treatment Variants For Treatment“
Add sub-strategy ApplyTreatmentToTreatmentVariationsCoreEligibility after data join component “Eligible Treatment Variations
Treatments”
Add sub-strategy ApplyTreatmentVariationsCoreEligibility after data join component “Identify Active Treatment Variants For
Treatment”
Update data join component “Eligible Treatment Variations Treatments”
join with component ApplyTreatmentVariationsCoreEligibility
add join condition .pyIssue = .pyIssue
Update group by component “Unique List of Treatment Variants“
add group by  on .pyIssue
Update data join component “Identify Active Treatment Variants For Treatment”
add join condition .pyIssue = .pyIssue


add join condition .pyIssue = .pyIssue
Connect sub-strategy ApplyTreatmentToTreatmentVariationsCoreEligibility to Results


1975
D. New Strategy - ApplyTreatmentVariantCoreEligibilityForSimulation (RS: AOMFW-Artifacts)
Enable External Input
Add Sub-strategy component ApplyTreatmentVariantCoreEligibility 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 ApplyTreatmentVariantCoreEligibility
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("Treatment 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 "ApplyTreatmentVariantCoreEligibility"
Connect switch component “Simulation Mode Check“ to Results
E. New Strategy - TradeInSquadZoneForTreatmentVariant (RS: AOMFW-Business-Artifacts)
Enable External Input and connect to Results


1976
F. New Strategy - UpsellSquadZoneForTreatmentVariant (RS: AOMFW-Business-Artifacts)
Enable External Input and connect to Results
G. New Strategy - RetentionSquadZoneForTreatmentVariant (RS: AOMFW-Business-Artifacts)
Enable External Input and connect to Results
H. New Strategy - ServiceSquadZoneForTreatmentVariant (RS: AOMFW-Business-Artifacts)
Enable External Input and connect to Results


1977
I. New Strategy - RetainSquadZoneForTreatmentVariant (RS: AOMFW-Business-Artifacts)
Enable External Input and connect to Results
J. New Strategy - RenewSquadZoneForTreatmentVariant (RS: AOMFW-Business-Artifacts)
Enable External Input and connect to Results
K. New Strategy - CareSquadZoneForTreatmentVariant (RS: AOMFW-Business-Artifacts)
Enable External Input and connect to Results


1978
L. New Strategy - EngagementSquadZoneForTreatmentVariant (RS: AOMFW-Business-Artifacts)
Enable External Input and connect to Results
M. New Strategy - HBBSquadZoneForTreatmentVariant (RS: AOMFW-Business-Artifacts)
Enable External Input and connect to Results
N. New Strategy - LoyaltySquadZoneForTreatmentVariant (RS: AOMFW-Business-Artifacts)
Enable External Input and connect to Results


1979
O. New Strategy - CrossSellSquadZoneForTreatmentVariant (RS: AOMFW-Business-Artifacts)
Enable External Input
Add filter component “Not Email“ after External Input with condition as -
.Channel!="Email"||.OfferName="MobileAddFixed"
Connect filter component “Not Email“ to Results
Add filter component “Email“ after External Input with condition as -
.Channel="Email"&&.OfferName!="MobileAddFixed"
Add sub-strategy PrioritiseCrossSellTreatmentVariants after filter component “Email“
Connect sub-strategy PrioritiseCrossSellTreatmentVariants to Results
P. New Strategy - ApplyTreatmentVariantSquadEligibility (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)


1980
Add following sub-strategy components after Squad based filters as created above respectively -
TradeInSquadZoneForTreatmentVariant
CareSquadZoneForTreatmentVariant
EngagementSquadZoneForTreatmentVariant
HBBSquadZoneForTreatmentVariant
LoyaltySquadZoneForTreatmentVariant
UpsellSquadZoneForTreatmentVariant
ServiceSquadZoneForTreatmentVariant
RetainSquadZoneForTreatmentVariant
RenewSquadZoneForTreatmentVariant
CrossSellSquadZoneForTreatmentVariant
RetentionSquadZoneForTreatmentVariant
Connect the sub-strategy components to results
Q. New Strategy - ApplyTreatmentVariantSquadEligibilityForSimulation (RS: AOMFW-Artifacts)
Enable External Input
Add Sub-strategy component ApplyTreatmentVariantSquadEligibility 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 ApplyTreatmentVariantSquadEligibility
Join on pyName


1981
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("Treatment Variant Squad
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 "ApplyTreatmentVariantSquadEligibility"
Connect switch component “Simulation Mode Check“ to Results
R. New Strategy - ApplyTreatmentVariantEligibility (RS: AOMFW-Artifacts)
Save existing strategy IdentifyTradeInTreatmentVariations as strategy ApplyTreatmentVariantEligibility
Delete the following components (as highlighted below) -
Eligible Treatment Variations Treatments
Apply TradeIn TreatmentToTreatmentVariation  Proposition Filter
Unique List of Treatment Variants
Identify Active Treatment Variants For Treatment
Apply TradeIn Treatment Variant Proposition Filter
Rename sub-strategy component “TradeIn TreatmentToTreatmentVariations“ to “ImportAllTreatmentToTreatmentVariations“ and
uncheck “Specify a single component within the strategy“
Rename filter component “Active” to “Active Treatment to Treatment Variations“


1982
Rename sub-strategy component “Get TradeIn Propositions From Treatment Variants Group“ to “ImportAllTreatmentVariations“ and
uncheck “Specify a single component within the strategy“
Rename filter component “Active Propositions” to “Active Treatment Variations“
Update data join component to add the following join condition -
.pyIssue = .pyIssue
Add set property component “Treatment To Treatment Variations Data“ after sub-strategy “Apply FUT Check“ and set -
.Type = “Treatment To Treatment Variations Data“
Add set property component “Treatment Variations Data“ after filter component “Active Treatment Variations“ and set -
.Type = “Treatment Variations Data“
Add sub-strategy component “ApplyTreatmentVariantCoreEligibilityForSimulation“
Connect the following components to sub-strategy component “ApplyTreatmentVariantCoreEligibilityForSimulation“ -
“Treatment To Treatment Variations Data“
“Treatment Variations Data“
Connect sub-strategy component “ApplyTreatmentVariantCoreEligibilityForSimulation“ to set property “Type - Treatment To
Treatment Variations Data“
Disconnect sub-strategy ApplyTreatmentToTreatmentVariationsDataToTreatments from Results
Add sub-strategy ApplyTreatmentVariantSquadEligibilityForSimulation after sub-strategy
ApplyTreatmentToTreatmentVariationsDataToTreatments
Connect sub-strategy ApplyTreatmentVariantSquadEligibilityForSimulation to Results
S. Update Strategy - IdentifyTreatmentVariations
Delete the following components (as highlighted below) -
GetActiveTreatmentVariationsForTreatment
Reset Tags For Matching
Match Eligible Propositions
Record Dropped Propositions
Eligible Propositions
Simulation Mode Check
“TradeIn Treatments”
“UpSell Treatments”
“Retention Treatments”
“Service Treatments”
“Retain Treatments”


“Retention Treatments”
“Service Treatments”
“Retain Treatments”
“Renew Treatments”
“CrossSell Treatments”
“Care Treatments”


1983
“Engagement Treatments”
“HBB Treatments”
“Loyalty Treatments”
IdentifyServiceTreatmentVariations
IdentifyRetentionTreatmentVariations
IdentifyUpsellTreatmentVariations
IdentifyTradeInTreatmentVariations
IdentifyCareTreatmentVariations
IdentifyCrossSellTreatmentVariations
IdentifyRenewTreatmentVariations
IdentifyRetainTreatmentVariations
Identify Engagement TreatmentVariations
Identify Loyalty TreatmentVariations
Identify HBB TreatmentVariations

Add sub-strategy ApplyTreatmentVariantEligibility after External Input
Connect sub-strategy ApplyTreatmentVariantEligibility to set property component “Eligible Treatment Variants“
Connect set property component “Eligible Treatment Variations After Additional Check“ to sub-strategy component
“IdentifyBestTreatmentVariantForTreatment“
T. Withdraw Strategies
IdentifyServiceTreatmentVariations
IdentifyRetentionTreatmentVariations
IdentifyUpsellTreatmentVariations
IdentifyTradeInTreatmentVariations
IdentifyCareTreatmentVariations
IdentifyCrossSellTreatmentVariations


1984
IdentifyRenewTreatmentVariations
IdentifyRetainTreatmentVariations
Identify Engagement TreatmentVariations
Identify Loyalty TreatmentVariations
Identify HBB TreatmentVariations


1985
Bundle Event Tech Debt - Remove Outbound Calls from MVP Flow

Impact in Other areas
Dependencies
Logic Changes
A. Update Strategy- AllTreatmentsForEligibleOffers
Add a new Filter 'CustomerSegment  Check' and add below Condition
      !@String.equalsIgnoreCase(.CustomerSegment,"Consumer")
Add this Filter Between ‘OutboundCC Treatments' filter and 'OutboundTreatmentsByTrigger’ SetProperty1009209 Bundle Event Tech Debt - Remove Outbound Calls from MVP Flow
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


1987
OB Enabler - App Push & Inbox into CM

Impact in Other areas
Dependencies
Change Description
Logic Changes
A. New Data Set - BestAppPushT reatmentsForChannelManagement
B. New Data Set - UniqueListOfAppPushCustomersForChannelManagement
C. New Data Flow - ProcessAppPushByLegacy
D. New Data Flow - ProcessAppPushByBatch
E. Update Data Flow - ProcessOutbound
G. Update Data Flow - ProcessBestOBT reatmentsAsT arget
F. New Data Flow - ProcessAppPushByChannelManagement (SR Class)
G.  Data Flow - ProcessAppPush (used by TIL) - No Update, Dev Test Only

Impact in Other areas
Dependencies
Change Description
Move AppPush channel into Channel Management functionality following the same design pattern as SMS in Channel Management
No requirement for separate strategy as used by SMS 924885 The ability to use channel management capability for App Push &
Inbox - for RT and batch.
PM Tool No
PM Tool KT Documentation No
Knowledge Transfer Yes
App Yes   As per App design
DB No  Area Yes/No Comments
PM Tool No
App Yes  Logic E2E test can be done once app work is completed
DB No  Area Yes/No Comments


1988
New Channel management feature toggle for AppPush channel (When rule) is required
The change will be done for both Batch and Real-time execution for AppPush


1989
Logic Changes
A. New Data Set - BestAppPushTreatmentsForChannelManagement
Create a new C* Data Set BestAppPushTreatmentsForChannelManagement on SR class with following keys -
pySubjectID
pyName
OfferID
TargetSubChannel
OfferVariant
TreatmentVariant
SegmentKey
B. New Data Set - UniqueListOfAppPushCustomersForChannelManagement
Create a new C* Data Set UniqueListOfAppPushCustomersForChannelManagement on Subscription class with only one Key as
CustomerID

C. New Data Flow - ProcessAppPushByLegacy
Source - Abstract
Primary Destination - Data Set - BestAppPushTreatmentsAfterControlGroups
Add Branch for secondary destination
Add Convert shape in to the secondary destination to convert from SR class to SR class -
Enable Auto-copy
Set .CreateTs = @DateTime.getCurrentTimeStamp()
Set secondary destination to data set - pxInteractionHistory
Add another Branch for secondary destination
Add Convert shape in to the secondary destination 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


1990

D. New Data Flow - ProcessAppPushByBatch
Source - Abstract
Primary Destination - Data Flow - ProcessAppPushByLegacy
Filter for Primary Destination - “AppPush By Legacy“ and evaluate true if when rule -  TBC (Created by App as part of Feature Toggle)
returns false
Add Branch for secondary destination - Data Set - BestAppPushTreatmentsForChannelManagement
Filter for Secondary Destination - “AppPush By Channel Management“ and evaluate true if when rule -  TBC (Created by App as part of
Feature Toggle) returns true

E. Update Data Flow - ProcessOutbound
Replace the destination on “AppPush Treatments” branch from Data set - BestAppPushTreatmentsAfterControlGroups with new Data flow -
ProcessAppPushByBatch


1991
G. Update Data Flow - ProcessBestOBTreatmentsAsTarget
Rename Filter “All IH For OBCC, AppPush, DirectMail, RCS & MMS“ to “All IH For OBCC, DirectMail, RCS & MMS” and update filter
condition to -
@String.equalsIgnoreCase(.Channel,"OutboundCC")||@String.equalsIgnoreCase(.Channel,"DirectMail")||@String.equalsIgnoreCase
(.Channel,"RCS")||@String.equalsIgnoreCase(.Channel,"MMS") = true
Rename Filter “Only IH for OBCC, AppPush, DirectMail, RCS and MMS“ to “Only IH for OBCC, DirectMail, RCS and MMS” and update
filter condition to -
@String.equalsIgnoreCase(.Channel,"OutboundCC")||@String.equalsIgnoreCase(.Channel,"DirectMail")||@String.equalsIgnoreCase
(.Channel,"RCS")||@String.equalsIgnoreCase(.Channel,"MMS") = true
F. New Data Flow - ProcessAppPushByChannelManagement (SR Class)
Source - BestAppPushTreatmentsForChannelManagement data set
Primary Destination data set - AppPush Staging (To be confirmed by App)
Add Convert shape to convert from SR class to AppPush Staging class as per the mapping below (TBC) -
queue_id QueueId
interaction_id pxInteractionID
treatment_name pyName
treatment_variant TreatmentVariant
offer_name OfferName
offer_variant OfferVariant
create_datetime pxDecisionTimeAppPush Staging (Target) SR (Source)


1992
Add Branch for secondary destination
Add Convert shape in to the secondary destination to convert from SR class to SR class -
Enable Auto-copy
Set .CreateTs = @DateTime.getCurrentTimeStamp()
Set secondary destination to data set - pxInteractionHistory
Add another Branch for secondary destination
Add Convert shape in to the secondary destination 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

G.  Data Flow - ProcessAppPush (used by TIL) - No Update, Dev Test Only
This Data Flow does not require any update. But the activity InvokeAppPushNotification will be updated by App team to toggle between
Legacy delivery of AppPush and Channel Management. Dev test is required.payload Payload
priority pxPriority
partition_key PartitionKey
account_pool AccountPool
destination_address ContactDetail


1994
Upgrades- Digital campaign Recommendation

Impacted Areas

Business Requirements:
Business wants to consider Digital campaign details in AOM, to build a new recommendation.
As part of the digital request AOM Will get product details as LineItem Details and pathway in Bundle_Type attribute which will be using
internally to build recommendations.961802 Dig Ph3 reporting
961286 Digital Upgrades Phase 3 - Identify the customer's Campaign's
Pathway using input from the Digital Platform
961291 Digital Upgrades Phase 3 - Campaign details passed to AOM by the
Digital Platform
961648 Digital Upgrades Phase 3 - Commercial Recommendation if the
customer has a valid campaign in context
961930 AOM will send a generic reason for Campaign Bundle
Recommendation
961806 Digital Upgrades Phase 3 -adding Campaign as a Recommendation
Type in Reporting961266 Digital Upgrades Phase 3 - Customer has opted out of data profiling
and campaign products are passed by digital
App Yes New properties(line item details) in
GetRecommendation API
DB No
Knowledge Transfer No
Logic Yes Updating existing DU logic.
PM Tool Yes Config Update for Recommendation
Reasons DD
PM Tool KT Documentation N/A N/A
UI/VADR N/A N/AArea Yes/No Comments


1995

Configuration in PM Tools
Update Decision Data for Campaign Bundle Recommendation Reasons as below

This will be just config change, implemented in 3.7. AsIs, Please find this for attributes to use for logic implementation. Logic for Rec
Reasons

Logic Changes:

New strategy:
Create a new SR property Boolean as IsDigitalCampaign.
Create a new strategy GetCampaignDetailsFromDigital
1. Data Import "LineItemList (Campaign Items)" calls page Primary.LineItemList
2. Get all line item details like product id and etc as below.

1. Get Tariff/Handset details form data import. 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
RecommendationTrigger Reason DescriptionReason Type Ranking Reason Title Logic to apply in
strategy


1996
2. And set
a. .RecommendationType ="Campaign",
b. .IsDigitalCampaign = true, only when we have campaign details.
c.  .Connect this strategy to InputForRecCal

Update strategies:

CalculateUpgradeDeal
961266 – As part of this story, we have to pass one recommendation even customer is opted out, but we have valid campaign
details.
1. Changes to opted out conditions.
a. In Filter 'Logic Recommendation condition', get IsDigitalCampaign  from new strategy and update condition with or
 (@String.equalsIgnoreCase(.IsDigitalCampaign,"Y") && @String.equalsIgnoreCase(Primary.Context(Channel),"WEB"))
In filter 'No Error for Logic Recommendation' add in the condition && @if(@String.equalsIgnoreCase(Primary.ProfilingConsentflag,"Y"),
true, @if(@String.equalsIgnoreCase(.RecommendationType,"Campaign"), true, false))
1. IdentifyLogicRecommendation
a. 961291 Digital Upgrades Phase 3 - Campaign details passed to AOM by the Digital Platform
i. Add a filter based on web channel and get digital lineitem details in that path.
ii. Get tariff/handset details (based on availability) and Set recommendation position = 1
iii. Add a set property "Add Campaign Detail" in the flow between "Not T4" and add switch for only campaign recommendation and
campaign recommendation + normal logic rec based on channel and concent flag. Then connect to "CalculatedUpgradeDiscount" .
iv. Apply discount to that available products.

PickBestPathway
961286 – MAKE SURE Bundle_type is considered and in case no value, we have to consider from BDC pathway. Existing logic. Test
only.
We will be always recommending based on this pathway value only.


only.
We will be always recommending based on this pathway value only.

1. Decompose Recommendation
a. Update .RecommendationType set properties to "Campaign" when we have campaign recommendation.


1997

1. 'Dedupe Campaign and Commercial Recommendations'
a. 961648 Digital Upgrades Phase 3 - Commercial Recommendation if the customer has a valid campaign in context.
i. Strategy to compare commercial and campaign recommendation.
ii. Make sure commercial rec will be next position to campaign recommendation.
iii. If the customer has a valid campaign in context and if AOM recommends a commercial rec for the pos 1, then AOM does not send
that commercial Rec (at all)
iv. If the Commercial Rec device is the same than the Campaign Device, then AOM does not sent the Commercial Rec to Digital
v. The same device is defined as the same manufacturer, model, storage i.e. if it is different colour but the manufacturer, model and
storage are same then don’t sent the device. (this might be happening based on the groupby Test only ).

1. 'IdentifyRecommendationReasons'
a. 61930 AOM will send a generic reason for Campaign Bundle Recommendation
i. .ReasonTitle, .ReasonDescription and .ReasonType. and rank SR properties to be updated for campaign details and to be added
to the rec reasons DD.
ii. Same will be added to IH reporting too (check with app for IH reporting table extension)

Other stories:

961802 Dig Ph3 reporting, (In place already, need to check response in 4.01) test only story.

3.7/4.1 Digital Upgrades  please find the miro page for above stories.


1998
Upgrades - Exclude Discount list
HL Requirement
Introducing a list of discounts , which won’t be showed in discount list.  during edit deal.
business want to list out few discounts and manage that list in pm tool. AOM will be validating them from the list before giving GPL
results to remove.
 Assisted Upgrade Business Config:

1. Edit Screen:

Update Strategy Getdiscountlist
we will be having all lists of discounts at the Order By Discount Amount Prioritize component, we will be checking this discount with the
ExcludeDiscountList config value.
If the product id matches with the list in the config filter out that discount. else send to GPL output.
@String.contains(D_VFUKFWAOMFWDataAOMBusinessConfig[ConfigType:ExcludeDiscountList,ConfigName:ExcludeDiscountCode].Con
figValue, .ProductCode)
the product code should be from the available discounts from strategy.

 1015809Ensure that the 50% watch discount is not visible in the Mobile Journey
Logic Yes  Logic update to include exclusion for few
discount codes.
PM Tool Yes   Pm tool config is required in business
config screen to manage discountlist to be
excluded
APP/logic Yes  app/logic to update the business config
DB No  Team Task Comments
ExcludeDiscountListExcludeDiscountCod
eTBC Logic 922033This config Identifies
if discount need not
to be showed to
agent while editing
the deal.ConfigType ConfigName ConfigValue Logic/App US Usage


2000
Upgrades - 5G Ultra
HL Requirement
Introducing 5G Ultra connectivity to Devices.
Business want to Highlight 5GSA Devices on Current Holding and Recommendation Screens
Add Refine By Criteria to allow 5GSA Filterable, So that Agent can able to get only 5G ultra
A. Assisted Upgrade Meta Data Config:

need to update Connection type Product attribute to 5G Ultra(Deepak need to confirm the text )
             1046118 Device 5G Ultra Compatibility Indicator in the 'Existing Products'
            1046139 Device 5G Ultra Compatibility Indicator in the 'Selected products'
            1046179 Device 5G Ultra Compatibility Indicator in the Edit Device Screen
            1046170 Filter By 5G Ultra in the 'Refine by'
            1046190 Filter or sort By 5G Ultra in the Device Tab10460875G Ultra – Strategic Commercial Launch
Logic Yes  Logic update to include this in Get
Recommendation,refineby and GPL flow.
PM Tool Yes   Pm tool config is required in business
config screen to manage 5g Ultra.
APP/logic Yes  app/lto update the logic to consider new
attribute and refiney selection.
DB No  Team Task Comments


2001
this will be available, to logic as product attributes for handsets. currently we are only applying for Handsets in Mobile service only.
B.GetRecommendation Flow:
 Make sure this connection type is passing till GETRecommendation API end. which we can do in PopulateOutputPropertiesForNBAA.
we are setting the connection type in line item level. this should work for UI/APP Team.
Refine by flow:
C.Update Strategy GetRecommendedHandset
this will be impacting only devices so  need to be updated.
App team will be sending new 5G Ultra as a context parameter.
update the SetProperty'ContextProperties' as below
                 .Has5GUltra =Primary.Context("Has5GUltra")
Update the Filter'RefineByFilter' as below
@if(ContextProperties.HandsetManufacturer="" && ContextProperties.HandsetModel="",true,
@if(@String.equalsIgnoreCase(ContextProperties.HandsetManufacturer,.Manufacturer)
&&
@String.equalsIgnoreCase(ContextProperties.HandsetModel,.DeviceName),true,false))
&&
@if(ContextProperties.Has5G="True",@String.equalsIgnoreCase(.ConnectionType,"5G"), true)
&&
@if(ContextProperties.Has5GUltra="True",@String.equalsIgnoreCase(.ConnectionType,"5GUltra"), true)
&&
@if(ContextProperties.IsValid="True",.NearlyNew="True",true)
&&
@if(ContextProperties.DeviceCostRange!="",
.HandsetLoanPrice >= ContextProperties.ValueInteger1 &&
@if(ContextProperties.ValueInteger2 != 0,
.HandsetLoanPrice < ContextProperties.ValueInteger2, true),true)
Note : condition should use same wording/value configured in Product attributes and refine by param. example : 5G Ultra


2002

GPL Flow: GetDeviceList
make sure connection type is moved to end ,in the above strategy , so that UI/App can access this connection type data , during the
devices screen


2003
Add the unsubscribeURL to IMI outbound API call

Impact in Other areas
Dependencies
Logic Changes
A. Update Strategy - PopulateOutputPropertiesForEmailByChannelManagement
Update SetProperty component 'SetContactDetails' as below
        .ValueText1= @PegaMKTUtilities.encryptURLQueryParams("&pname=" +.pyName+      "&iid="+.pxInteractionID + "&cid="
+.pySubjectID + "&email="+.EmailAddress ,true)
      .UnsubscribeUrlValue= D_VFUKFWAOMFWDataAOMConfig[ConfigType:Microsite,ConfigName:UnsubscribeURL].ConfigValue +
“&px=“ + .ValueText1
 1043690
 Add the unsubscribeURL to IMI outbound API call
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


2004
Upgrades MBB -Refine By

Impact in Other areas
Business Requirement:
Businesses want to include refine by capability in MBB Flow. An agent can able to select recommendations based on selection.
Unlike MBB Recommendations (only two cards) for refine by, we will be recommending three eligible recommendations(three cards
based on criteria).
Logic Changes
A. Update Strategy - GetRecommendedMBBDevice
Rename SellablePaymHandsets to SellableMBBDevices
SellableMBBDevices -> Properties Mapping -> DeviceCategory = ProductAttributes(DeviceCategory)
From SellableMBBDevices -> Filter the MBB Devices based on the below criteria.993186 MBB: Refine By Recommendation Logic
994600 MBB: Device Tab Ordering in Edit Screen
993117 MBB: Stock check for MBB Recommendation
804003 MBB-Pre S15 Calculation for Evo Airtime and Device
911886 MBB-Keeping the Pilot UI up to date for ongoing Commercial UAT
1010508 MBB - Giga Cube Eligibility
1017571 MBB Device Tab - Perform Top 5 Device Stock Check when 1st loading the Device Tab
991394 Refine by and CRE Results enhancement
1029173 MBB Logic Recommendations and CRE Results946119 Refine by-Logic for Selecting Evo specific Device using the Refine by option
PM Tool Yes configuration changes. offer catlag need to be updated for gigacube new proposition
willbe introduced.
App yes pilot ui will be app story. logic need to provide information to app on demand. no dev
required for core logic as it is common for VDAR and Pilot UI.
DB No  Area Yes/No Comments
 Device Type Manufacturer &
ModelStorage Device cost 5G Unlimited Nearly
New


2005

After the refine by filter, we will be getting top sold product from datapage (aPP Prodvided ) and  make a substrategy call to
GetStockDetails, apply Stock filter.993117
For all available devices we will be giving top three devices with ranks. (Rank is  attribute from datapage  count of most sold
products)
MostSoldProduct data page will give rank (count of accepted outcome in IH) need to get that property from this datapage. (app team
need to update that DP).
order devices based on recommendation rank
Error messages should be same as paym.
The above steps needs to be performed only for SecondaryContext from Context is RefineBy. Remaining flow works as-is for non refine
by cases.
If the Refine by criteria returns a Device, only Devices that are in stock, pre ordered or back order presented see 993117Device Type =
Laptop/Tablet (new)Laptop/Tablet empty/True/Fals
eempty/valu
eempty/range True/FalseTrue/FalseTrue/False
Device Type =
GigaCube/Dongle/Mobile
-Wifi(new)Giga/Dongle/Mo
bile-Wifiempty empty/valu
eempty/range True/FalseTrue/FalseTrue/False
Manufacturer Laptop/Tablet TRUE empty/valu
eempty/range True/FalseTrue/FalseTrue/False
Model Laptop/Tablet TRUE empty/valu
eempty/range True/FalseTrue/FalseTrue/False
Storage Values TRUE value empty/range True/FalseTrue/FalseTrue/False
Device cost(range for
MBB)Values empty/True/Fals
eempty/valu
erange True/FalseTrue/FalseTrue/False
5G Values empty/True/Fals
eempty/valu


5G Values empty/True/Fals
eempty/valu
eempty/range TRUE True/FalseTrue/False
Unlimited Values empty/True/Fals
eempty/valu
eempty/range True/FalseTRUE True/False
Nearly New Values empty/True/Fals
eempty/valu
eempty/range True/FalseTrue/FalseTRUE
DeviceType DeviceType in Product Attributes
Laptop/Tablet/GigaCube/Dongle/Mobile-Wifi
Manufacturer Manufacturer
Model DeviceName in Product Attributes
DeviceStorage (Check with App team on Name) DeviceData in Product Attributes
Cost HandsetLoanPrice from Datapage -> what about bundled?
Has5G ConnectionType from Product Attributes
NearlyNew NearlyNew from Product AttributesContext from API Return Sellable MBB Devices from D_PaymHandset


2006
Note: refer GetRecommendedHandset for exisitng AU refine by condition  need add new attributes for MBB.
B. Update Strategy - GetRecommendedMBBTariff.
 for GetRecommendedMBBTariff (see GetRecommendedMBBTariff_SK refine by)
need to Add in stock for tariff products (device stock has already been checked in previous strategy)

From ‘EvaluateTariffToHandsetCompatibility’ create an alternate path to ‘Essential Tariff Properties’ which calls a filter ‘Seconday Context is
Refine By’ with filter condition @String.equalsIgnoreCase(.Primary.Context(SecondaryContext),”Refine By”) and add the conditions for simo
and unlimited.
SIMOParam=Subscription.Context("SIMO ")
UnLimitedParam=Subscription.Context("Unlimited")
above parameters are already available from calculate upgrade deal.
Update Strategy -PickBestPathway(existing logic) need to test for MBB
Existing logic should be updated to consider SIMO  filter condition coming from context
if NBAAMode =NBA or (NBAAMode=RefineBy Run  and (SIMOParam !=True) )run existing logic
else if NBAAMode =RefineBy  and SIMOParam =True >Select only the records TariffType=SIMOnly
994600
MBB: Device Tab Ordering in Edit Screen
Update strategy OrderMBBDeviceList to so that devices are ordered by Evo devices and non-Evo Device ordered by device type and within
the device type, the devices are ordered in alphabetical order
993117: Stock check
as part of refine by we are already checking the stock once we got the recommendations in the above sections.
for normal get recommendation flow, we have to place a stock check. GetRecommendedMBBTariff and GetRecommendedMBBDevice


strategies need to be updated for normal flow.
need to add get stock details strategy and filter out of of stock products before getting most sold products.
1029173/1010508 - CRE criteria.
if Customer is Eligible for Recommendation from CRE, CRE RetentionElgiblity.Indicator =True (existing code).
CREType=
Based on the CRE flags, MBB recommendations need to be populated as below.
 Rec 1 Rec 1  Rec 2 Rec 2


2007
From(current
holding)CREType(fl) Not CRE Eligible
for Rec (CREType) CREType
(True)Not CRE Eligible
for Rec (CREType)
Tablet If coming from an
Apple tablet –
present an Apple
tablet (the top selling
Apple tablet over
past 1 month)
If coming from a non
Apple tablet  –
present a Samsung
tablet (the top selling
Samsung tablet over
past 1 month)
If dont know the
device or a device
needs to be
recommended
because of the CRE
result, recommend
the top selling Apple
tablet over the past
monthN/A  Present an eligible
tariff with equal to or
greater than Data
allowance compared
to current tariff data
allowance. If card 1
is a SIMO we want to
ensure the tariff is
different, therefore
select the next tariff
up in terms of data
from card 1. If card 1
is top of the ladder
SIMO then logic is
not to populate card
2 with a
recommendation

MBB 24th month
SIMOIf coming from an
Apple tablet –
present an Apple
tablet (the 2nd top
selling Apple tablet
over past 1 month)
If coming from a non
Apple tablet  –
present a Samsung
tablet (the 2nd top
selling Samsung
tablet over past 1
month)
If don't know the
device, recommend
the 2nd top selling
tablet over the past
month
Laptop If coming from an


the 2nd top selling
tablet over the past
month
Laptop If coming from an
Apple Laptop –
present an Apple
tablet (the top selling
Apple tablet over
past 1 month)
If coming from a non
Apple Laptop  –
present a Samsung
tablet (the top selling
Samsung tablet over
past 1 month)
If dont know the
device+B11,
recommend top
selling tablet (for the
last month)N/A  MBB 24th month
SIMOIf coming from an
Apple tablet –
present an Apple
tablet (the 2nd top
selling Apple tablet
over past 1 month)
If coming from a non
Apple tablet  –
present a Samsung
tablet (the 2nd top
selling Samsung
tablet over past 1
month)
If don't know the
device, recommend
the 2nd top selling
tablet over the past
month
Dongle MBB SIMO no rec  MBB 24th month
SIMOno rec
Wifi MBB SIMO no rec  MBB 24th month
SIMOno rec
Giga (all but 30
days SIMO)MBB SIMO 5G Giga Device  MBB 24th month
SIMOIf coming from an
Apple tablet –


2008
present an Apple
tablet (the 2nd top
selling Apple tablet
over past 1 month)
If coming from a non
Apple tablet  –
present a Samsung
tablet (the 2nd top
selling Samsung
tablet over past 1
month)
If don't know the
device, recommend
the 2nd top selling
tablet over the past
month
SIMO (all but 30
days)MBB SIMO Top Selling Tablet
(rule as above) MBB 24th month
SIMOIf coming from an
Apple tablet –
present an Apple
tablet (the 2nd top
selling Apple tablet
over past 1 month)
If coming from a non
Apple tablet  –
present a Samsung
tablet (the 2nd top
selling Samsung
tablet over past 1
month)
If don't know the
device, recommend
the 2nd top selling
tablet over the past
month
SIMO 30 days MBB SIMO MBB SIMO  MBB 24th month
SIMOIf coming from an
Apple tablet –
present an Apple
tablet (the 2nd top
selling Apple tablet
over past 1 month)
If coming from a non
Apple tablet  –
present a Samsung
tablet (the 2nd top
selling Samsung
tablet over past 1
month)


2009
note:when ever we are recommending two simo plans, first one will be top sold product and second one will be higher data than card 1
tariff.
CRE criteria for GetRec with example
refine by for the same get rec
for simo flag, we are not recommending simo 30 plans, all are > 30 days. If don't know the
device, recommend
the 2nd top selling
tablet over the past
month
Giga 30 days SIMO MBB SIMO 5G Giga Device  MBB 24th month
SIMOEmpty


2010
Release 4.02


2011
Trade-In - Buy Back Guarantee Redemption

Impact in Other areas
Dependencies
Logic Changes:
Configure below product codes for two new child offers in Offer to offer variation decision data1030172 Import BBG Child Offers
1030173 Determine BBG offer eligibility
1030174 Rank Prioritise Devices based on BBG price
1030176 Arbitrate Child Offers
1030178 Populate API Response
1030166 GetNBA API changes1029620 (Epic) Trade-In - Buy Back Guarantee Redemption (Phase 3 - Redemption)
PM Tool Yes
PM Tool KT Documentation No
Knowledge Transfer No
App Yes
DB No  Area Yes/No Comments
PM Tool Yes
App Yes
DB No  Area Yes/No Comments
TradeInCOBRA …
19 Jan 2023, 07:22 AMV1.xlsx COBRA  CATAL…
19 Jan 2023, 07:21 AMSVS.zip
 Cobra Decision …
11 Jan 2023, 04:34 PMges.pdf
 ArbitrateBBGW …
24 Nov 2022, 06:31 PMice.pdf
 CalculateBBG …
24 Nov 2022, 12:49 PMity.pdf
 IdentifyEligible …
24 Nov 2022, 08:02 AMegy.pd
New Child Offer Names Product Codes


2012
Update IdentifyEligibleTradeInOffers
Update ApplyOfferCoreEligibility strategy:
TradeInOfferEligibility PF : Default eligibility criteria is set to true for two new BBG child offes called “BBGTradeInOneTimeCredit“ and
“BBGTradeInMonthlyCredit“ .
Import new sub strategy called CalculateBBGEligibility
Import existing sub strategy called GetProductDetails
Connect substrategy to new filter called “TradeIn BillCredit Check“ and add condition as .ValueText="BillCredit" and join this to new set
property called “TradeInOneTimeBillCredit Spot Price“ and in this set property set .ValueInteger2=.ValueText1
Connect substrategy to new filter called “TradeIn Monthly Credit Check“ and add condition as .ValueText="MonthlyCredit" and join this to
new set property called “TradeIn MonthlyCredit Spot Price“ and in this set property set .ValueInteger2=.ValueText1
Connect new sub strategy CalculateBBGValue to new two filters.
In first filter called,”TradeInBillCredit Spot Price Check” add condition as TradeInOneTimeBillCreditSpot Price.ValueInteger2>=0 and join
it to new set property called “Set Bill Credit Details“ and in this set property component set .pyName="BBGTradeInOneTimeCredit"
In Second filter called,”TradeInMonthlyCredit Spot Price Check” add condition as TradeIn MonthlyCredit SpotPrice.ValueInteger2>=0
and join it to new set property called “Set TradeIn MonthlyCredit Details “ and in this set property set property component set .pyName =
"BBGTradeInMonthlyCredit"
Connect existing Proposition Filter called “TradeInOfferEligibility“ to three new filters. Name first filter as “BBGTradeInOneTimeCredit


Child offer“.and name second filter as “BBGTradeInMonthlyCredit Child Offer“. For the third filter name it as “Excluding BBG Offers“
In first filter called “BBGTradeInOneTimeCredit Child offer“ add condition as
@String.equalsIgnoreCase(.pyName,"BBGTradeInOneTimeCredit")
In second filter called “BBGTradeInOneTimeCredit Child offer“ add condition as
@String.equalsIgnoreCase(.pyName,"BBGTradeInMonthlyCredit")
In third filter called “Excluding BBG Offers“ add condition as @String.notEqualsIgnoreCase(.pyName,"BBGTradeInMonthlyCredit") &&
@String.notEqualsIgnoreCase(.pyName,"BBGTradeInOneTimeCredit")
Connect the first filter to new data join called “Join with TradeIn Montly Credit BBG Value” and in the dropdown refer existing set
property called “Set TradeIn MonthlyCredit Details “ and add join condition as .pyName=.pyName and enable check box for Exclude
source component results that do not match join condition. In the properties mapping map .ValueText="Matched" and Map
AssetIntegrationId,BuybackStartDate,BuybackEndDate,AssetIntegrationIdValue,ProductDescription,
BuyBackStartValue,BuyBackEndValue,BuybackGuarantee,BuybackGuaranteeValue
Note: Make sure to pass these variables till end
Connect the data join to new filter component called “Only Matched Records“ and add condition as .ValueText=”Matched” and join this
filter to Result componentBBGTradeInMonthlyCredit 118095
BBGTradeInOneTimeCredit 118096


2013
Connect the Second filter to new data join called “Join with TradeIn OneTime Credit BBG Value” and in the dropdown refer existing set
property called “Set Bill Credit Details“ and add join condition as .pyName=.pyName and enable check box for Exclude source
component results that do not match join condition. In the properties mapping map .ValueText="Matched"  and Map
AssetIntegrationId,BuybackStartDate,BuybackEndDate,AssetIntegrationIdValue,ProductDescription,
BuyBackStartValue,BuyBackEndValue,BuybackGuarantee,BuybackGuaranteeValue
Connect the data join to existing filter component called “Only Matched Records“
Connect the third filter called “Excluding BBG Offers“ directly to Result component.

Eligibility Criteria:
1. Customer has device in current holdings (as passed in context) where current date is within defined BBG Start & End dates.
For each eligible device (in current holdings): Device SKU (ProductId) is within the Trade In device SKU group
Create New Strategy CalculateBBGEligibility(TBC)
Create new strategy CalculateBBGEligibility in class:VFUK-FW-AOMFW-Data-Subscription
Import two sub strategies in this new strategy called “CalculateBBGEligibility“
Import first existing sub strategy called “GetProductDetails“. Run on other page and provide condition as Primary.ProductDetails
Create SR property TradeInGroupSKU of Text Type
Connect this sub strategy to new filter component called “TradeInGroupSKU Data“ and add condition as
@String.equalsIgnoreCase(.Name,"TradeInGroupSKU")
Create new SR property called “TradeInGroupSKU“ of data type Text in SR class: VFUK-AOMFW-SR


Join this new filter called “TradeInGroupSKU Data“ to new set property. Name the set property as “Set TradeInGroupSKU List“ and set
condition as .TradeInGroupSKU=.Value in this set property


2014
Create new strategy GetBBGData:
Create new strategy called “GetBBGData“ in class: VFUK-FW-AOMFW-Int-ProductDetail
In this new strategy “GetBBGData“, import new data import component and name this component as “Import Details“ and in this
component, import page called “Primary.Detail“ and in properties mapping tab map .ValueText1=.Name and .ValueText2=.Value
Create new SR properties AssetIntegrationId,AssetIntegrationIdValue,BuybackStartDate,BuybackEndDate
,BuybackGuarantee,BuybackGuaranteeValue in class: VFUK-AOMFW-SR
Join above data import called “Import Details“ to 5 new filters.
In first filter called “AssetIntegrationId“ add condition as @String.equalsIgnoreCase(.ValueText1,"AssetIntegrationId")
Name second filter as “ProductDescription“ and add condition in filter as @String.equalsIgnoreCase(.ValueText1,"ProductDescription")
Add condition as @String.equalsIgnoreCase(.ValueText1,"BuybackStartDate") in third filter called “BuybackStartDate“
Add a condition in a fourth filter named “BuybackEndDate”, as @String.equalsIgnoreCase(.ValueText1,"BuybackEndDate")
In a fifth filter named “BuybackGuarantee“, add condition as @String.equalsIgnoreCase(.ValueText1,"BuybackGuarantee")
Connect all these 5 filters to a new set property called “Set BBG Details“ and in this set property set below properties and connect it to
result component
AssetIntegrationId Text
AssetIntegrationIdValue Text
BuyBackStartPeriod Text
BuyBackEndPeriod Text
BuybackGuarantee Text
BuybackGuaranteeValue IntegerSr Property Name Data Type
Target Source


2015
Connect this set property “Set BBG Details“ to result component.
Strategy: CalculateBBGEligibility: Import above newly created strategy called “GetBBGData“ in strategy called
“CalculateBBGEligibility“ and name this strategy as “Get CurrentHoldings BBG Data“ and add condition as Run on other page called
“primary.Details“ and invoke GetBBGData strategy
Create two new SR Properties BuyBackStartValue and BuyBackEndValue of Text Type in class: VFUK-AOMFW-SR
Connect this sub strategy component  called “Get CurrentHoldings BBG Data“ to new set property called “Reformat BBG Dates“ and in
this set property set below details.ValueText4 Primary.Context
.ProductType Primary.ProductType
.Value Primary.Id
.AssetIntegrationId AssetIntegrationId.ValueText1
.AssetIntegrationIdValue AssetIntegrationId.ValueText2
.ValueText4 ProductDescription.ValueText1
.ProductDescriptionValue ProductDescription.ValueText2
.ValueText5 BuybackStartDate.ValueText1
.BuyBackStartPeriod BuybackStartDate.ValueText2
.ValueText5 BuybackEndDate.ValueText1
.BuyBackEndPeriod BuybackEndDate.ValueText2
.BuybackGuarantee BuybackGuarantee.ValueText1
.BuybackGuaranteeValue BuybackGuarantee.ValueText2
Target Source


2016
Connect above set property “Get CurrentHoldings BBG Data“ to new filter component called “Validate SKUs with SKUGroup“ and add
condition as @contains(SetTradeInGroupSKU.ValueText3,.Value)
Join filter called  “Validate SKUs with SKUGroup“ to new filter component named, “Validate Current Day is within BBG Period“ and add
condition as .BuyBackStartValue>=0&&.BuyBackEndValue<=0
Join the above filter called “Validate Current Day is within BBG Period“ to new empty set property called “Valid Data“. In this set property
dont set anything.
Connect this set property, “Valid Data“ to two new group by components.
In first Group by component named,”Highest BBG Value” add condition as “With Highest“=.BuybackGuaranteeValue
In second group by component named, “Lowest BBG Value“ add condition as “With Lowest“=.BuybackGuaranteeValue
Connect the existing set property component called “Valid Data“ to two new filters.
Name the second filter as “Different BBG Values“ and add condition as
@notEquals(HighestBBGValue.BuybackGuaranteeValue,LowestBBGValue.BuybackGuaranteeValue)
Connect the second filter called “Different BBG Values“ to new prioritize component and name prioritize component as “Prioritize One
Random Current Product Holding“ and prioritize on .BuybackGuaranteeValue and order by Highest and select only top 1 record and
connect this prioritize component to result component. Refer below image .BuyBackStartValue @String.replaceAll(.BuyBackStartPeriod,'/','-')
.BuyBackStartValue @AOMUtilities.ConvertDDMMYYYYToPegaDateTime(.BuyBackStart
Value)


Value)
.BuyBackStartValue @AOMUtilities.CalculateNumberOfDaysFromToday(.BuyBackStartV
alue)
.BuyBackEndValue @String.replaceAll(.BuyBackEndPeriod,'/','-')
.BuyBackEndValue @AOMUtilities.ConvertDDMMYYYYToPegaDateTime(.BuyBackEnd
Value)
.BuyBackEndValue @AOMUtilities.CalculateNumberOfDaysFromToday(.BuyBackEndVa
lue)


2017
Name the first filter as “Same BBG Value“ and add condition as
@equals(HighestBBGValue.BuybackGuaranteeValue,LowestBBGValue.BuybackGuaranteeValue)
Connect this filter “Same BBG Value“ to two new group by components.
In first group by component called “Highest BBG End Date“ add condition with highest as .BuyBackEndValue
In first group by component called “Lowest BBG End Date“ add condition with lowest as .BuyBackEndValue
Connect existing filter called “Same BBG Value“ to two new filters.
In first first filter called “Same BBG End Dates“ add condition as @equals(HighesBBGEndDate.BuyBackEndValue
,LowestBBGEndDate.BuyBackEndValue)
In second filter called “Diffferent BBG End Dates“ add condition as
@notEquals(HighesBBGEndDate.BuyBackEndValue,LowestBBGEndDate.BuyBackEndValue)
Connect the filter called “Same BBG End Dates“ to new filter called “Prioritize Random BBG End Date“ with prioritize by
.BuyBackEndValue in descending order with top 1 record and join this component to result component. Refer below image.
Connect the filter called “Diffferent BBG End Dates“ to new filter called “Prioritize Closest BBG End Data“ with prioritize by
.BuyBackEndValue in ascending order with lowest top 1 record and join this component to result component. Refer below image.


2018
Reference CalculateBBGEligibility Strategy:

Update Strategy: SetPriceForGetNBA
Add new filter in between External input and set property called “Not BBG Devices“ and add condition in this new filter as
!@String.contains(.OfferName,"BBG")
Add new path from exteranl input. Join external input to new filter called “BBG Offers“ and add condition as
@String.equalsIgnoreCase(.ParentChild,"Child")&&@String.contains(.OfferName,"BBG")
Connect filter “BBG Offers“ to new set property called “Set Price For BBG“ and set below fields and join this set property to result
component