\n
Your contract end date will stay the same and if you change your mind you have 14 days to move back.\", \"button_text\": \"Change my \nplan\" } }, \"message\": { \"title\": \"You're running low on data\", \"expiry\": \"$[SR.TreatmentDynamicExpiry]\" }}\nStep 2: From the above example below are Data tokens\na)$[SR.FirstName]\nb)$[SR.ProductDescription3]\nc)$[SR.MobileDataDescription]", "source": "VODKB-200723-160306.pdf"} {"id": "42ff4a50fc2a-1", "text": "b)$[SR.ProductDescription3]\nc)$[SR.MobileDataDescription]\nd)$[SR.RecCostText]\nStep 3 : We use PopulateOutputPropertiesForAppPushByTrigger strategy to populate data for Data Tokens.", "source": "VODKB-200723-160306.pdf"} {"id": "0eea7d6fb122-0", "text": "296\n \nStep 4: After populating the Data Tokens we will pass the data to the platform .\nStep 5: Platform Team use above data and Replace the Data tokens in the Appush Body Text.\n \nSMS Data Token\nLet us Consider the below example for SMS Data Tokens Which are used in Batch.\nFrom the above example, [FirstName] is the Data Token. When a Customer receives the above text through an SMS the Data Token[First \nName] gets replaced with the actual name of the customer.\nHi [FirstName], you're eligible for a 15% discount on additional phones or our new Unlimited data SIM only plans. Can't decide what's best \nfor you? Click here https://www.vodafone.co.uk/householddiscounts to chat to one of our helpful agents who can guide you through your \noptions. Terms apply. To end texts, send STOP SMS to 9774.", "source": "VODKB-200723-160306.pdf"} {"id": "0057ec68296c-0", "text": "297\nCreating and replacing Data Tokens:\n1. Create an SR Property with the same name as the Data Token.\n2. Set a value to the SR Property in an Output properties Strategy.\n 3. Replace the Token with the actual value using a Replace All() function as below.", "source": "VODKB-200723-160306.pdf"} {"id": "08334d85445b-0", "text": "298\nChannel Specifics : How-To", "source": "VODKB-200723-160306.pdf"} {"id": "0991e2341c1d-0", "text": "299\nOffer Flows : How-To\nIn Pega Marketing, there is a one-to-one relation between offers and propositions. .When a strategy selects a proposition for a customer, \nthe offer flow associated with that proposition is invoked.\nPage links:\nEmail Offer Flows", "source": "VODKB-200723-160306.pdf"} {"id": "ef913a3e0a8d-0", "text": "300\nEmail Offer Flows\nLet us Consider Batch NBA use case for the Creation of Email offer Flows.\n Steps in creating Email offer flow : There are 2 ways to create a new offer flow.\n Step 1: Switch to the PegaMarketing Portal.\nStep 2: After Switching ,Select the content tab on left hand side panel and Click on Actions.\nStep 3: Click on the Create button , and select Action .\nStep 4: Enter the name of the offer flow.\nStep 5: Select the issue and Group.\nStep 6: Select the Application and Relevant Rule set Version.\nStep 7: After performing Step 4,5,6 click on the Create button.\nStep 8: Now it will redirect to the Offer Flow Screen.", "source": "VODKB-200723-160306.pdf"} {"id": "95979a4d85c8-0", "text": "301\nStep 9: On the Details tab Enter the basic details and click on Flow tab .\nStep 10: Click on the \u2018+\u2019 icon and select the Send Email.", "source": "VODKB-200723-160306.pdf"} {"id": "243b1dd76ce0-0", "text": "302\nStep 11: Connect the StartShape to Send Email shape and Send Email shape to End Shape.\nStep 12: Open the send Email shape and Select Specify Treatment and Enter the Email Template.\nStep 13: Select Deliver Online and select Use Subject from Treatment.\nStep 14: Go to the Adavnce setting and select Email Account.\nStep 15: Select Specify Email Account and Enter the Mailjet as Email Account.\nStep 16: Select Use Email Account Settings under From/Reply To section .\nEnter the Email Template which holds the name of the Email treatment to be sent. If you enable Deliver Online, you must select an \nexisting Email treatment since it determines the content of the email to be sent.\n System uses these settings when the Deliver Online mode is enabled.", "source": "VODKB-200723-160306.pdf"} {"id": "074385493b8e-0", "text": "303\nStep 17: Click on Save.\nOther way to create an offer flow:\nWe can also create a new offer flow from the existing offer flow. Following are the steps to create an offer flow from existing offer flow.\n1. Switch to Pega Marketing Portal as shown above.\n2. In the search box,search for the existing offer flow and open it.\n3. Click on save as button to create a new copy of the offer flow.\n 4. Provide the new offer flow name in the label field and If required,Update the issue and group.\nWhen a new offer flow is created in a particular issue and group,the respective decision data gets updated with the new proposition. \nWe need to make sure that the decision data is updated correctly.", "source": "VODKB-200723-160306.pdf"} {"id": "150d0ad074e9-0", "text": "304\n 5. Make sure you\u2019ve selected the correct rule set and version and click on create and open.\n 6. Once the offer flow got created,checkout the rule and update the basic details according to the new one.\n 7. In the flow tab,You can find that the flow is already created.\n 8. Open the properties of Send Email shape and configure the treatment template.", "source": "VODKB-200723-160306.pdf"} {"id": "46cb745399c8-0", "text": "305\n 9. Save and Check-in the rule.", "source": "VODKB-200723-160306.pdf"} {"id": "7f8d7c288059-0", "text": "306\nSMS Offer Flows And SMS Treatment Template\nLet us consider ProcessEvent use case for SMS Offer Flow Creation\nSteps for Creating SMS Offer Flow: There are two ways to create an offer flow.\nStep 1: First Switch to the PegaMarketing Portal.\nStep 2: Select the content tab on left hand side panel.\nStep 3: Click on the Create button.\nStep 4: Enter the name of the offer flow.\nStep 5: Select the issue and Group.\nStep 6: Select the Application and Relevent Ruleset Version.\nStep 7: After perfoming Step 4,5,6 click on the Create button.\nStep 8: Now it will redirect to the Offer Flow Screen.\nStep 9: On the Details tab Enter the basic details and click on Flow tab .", "source": "VODKB-200723-160306.pdf"} {"id": "91fbb2f23586-0", "text": "307\nStep 10: Click on the \u2018+\u2019 icon and select the Send SMS.\nStep 11: Connect the startShape to Send SMS shape and Send SMS shape to End Shape.\nStep 12: Open the send SMS shape and Select Specify Treatment and Enter the SMS Template.\nStep 13: Select the Deliver Online and select Use Existing SMS\nStep 14: Go to the Adavnce setting and select SMS Account.\nStep 15: Select Specify SMS Account and Enter the AOM SMS Account as SMS Account.\nEnter SMS Template which holds the name of the SMS treatment to be sent.\nThe system uses these setting when the Deliver Online mode is enabled.", "source": "VODKB-200723-160306.pdf"} {"id": "005ef1d37236-0", "text": "308\nStep 16: Click on Save.\n \nSteps for Creating SMS Treatment Template\nStep 1: Click on Content and Treatments.\nStep 2: Click on Create button and select SMS.\nStep 3: Enter the name of Template.\nStep 4: Select the Application and Relevent Ruleset Version.\nStep 5: After perfoming Step 3,4 click on the Create and open button.", "source": "VODKB-200723-160306.pdf"} {"id": "9e029c49258f-0", "text": "309\nStep 6: Enter the Body of the SMS ,in ProcessEvent use case ,we will pass SMS Body in a property and use it in the Body section.\nStep 7: Click on Save.\nOther way to create an offer flow:\nWe can also create a new offer flow from the existing offer flow. Following are the steps to create an offer flow from existing offer flow.\n1. Switch to Pega Marketing Portal as shown above.\n2. In the search box,search for the existing offer flow and open it.\n3. Click on save as button to create a new copy of the offer flow.\nWhen a new offer flow is created in a particular issue and group,the respective decision data gets updated with the new proposition. \nWe need to make sure that the decision data is updated correctly.", "source": "VODKB-200723-160306.pdf"} {"id": "2bb769417484-0", "text": "310\n4. Provide the new offer flow name in the label field and If required,Update the issue and group.\n5. Make sure you\u2019ve selected the correct rule set and version and click on create and open.\n6. Once the offer flow got created, checkout the rule and update the basic details in the details tab.\n7. Save & Check-In the rule.\n \n \nIn the flow tab,You can find that the flow is already created. Open the properties of Send SMS shape and verify the SMS account \nand Treatment template.", "source": "VODKB-200723-160306.pdf"} {"id": "15c3dc94bb0b-0", "text": "311\nApp-Push Templates and App-Push Data Tokens\nApp-Push Templates\nStep 1: App-Push Templates are updated in the TreatmentToTreatmentVariation screen in the PmTool. \nStep 2: App-Push Templates are updated in below properties in Pm tool screen.\n a)InApp Notification JSON\n b)Inbox Notification JSON\n c)Push Notification JSON\n \nStep 3 : Updates in the TreatmentToTreatmentVariation screen are pushed to the TreatmentToTreatmentVariation \nDecision data .", "source": "VODKB-200723-160306.pdf"} {"id": "ff80fd4f19e1-0", "text": "312\nExample : { \"HTMLTemplate\": { \"template_id\": \"BASE_TEMPLATE_WH\", \"values\": { \"background_color\": \"#E60000\", \n\"button_color\": \"#FFFFFF\", \"text_color\": \"#FFFFFF\", \"title_color\": \"#FFFFFF\", \"button_text_color\": \"#E60000\", \"run_action\": \n\"deep_link_action\", \"custom_url\": \"myvodafone://TARIFF_MIGRATION\", \"click_tag_name\": \n\"$[SR.pxInteractionID]_CLICKED_BUTTON\", \"template_image\": \n\"https://assets.vodafone.co.uk/cs/groups/public/documents/images/vfcon105149.jpg\", \"body_title\": \"$[SR.FirstName], you're running low \non data this month\", \"body_content\": \"Why not change your plan to avoid running low again? Switch to our $[SR.ProductDescription3] \nplan and you'll enjoy $[SR.MobileDataDescription] of data, unlimited minutes and unlimited texts for just \u00a3$[SR.RecCostText] a month.
\n
Your contract end date will stay the same and if you change your mind you have 14 days to move back.\", \"button_text\": \"Change \nmy plan\" } }, \"message\": { \"title\": \"You're running low on data\", \"expiry\": \"$[SR.TreatmentDynamicExpiry]\" }}\n \nApp-Push Data Token\nStep 1: Let us consider below Example for AppPush Data Tokens which is used for MVP.\nExample : { \"HTMLTemplate\": { \"template_id\": \"BASE_TEMPLATE_WH\", \"values\": { \"background_color\": \"#E60000\",", "source": "VODKB-200723-160306.pdf"} {"id": "ff80fd4f19e1-1", "text": "\"button_color\": \"#FFFFFF\", \"text_color\": \"#FFFFFF\", \"title_color\": \"#FFFFFF\", \"button_text_color\": \"#E60000\", \"run_action\": \n\"deep_link_action\", \"custom_url\": \"myvodafone://TARIFF_MIGRATION\", \"click_tag_name\": \n\"$[SR.pxInteractionID]_CLICKED_BUTTON\", \"template_image\": \n\"https://assets.vodafone.co.uk/cs/groups/public/documents/images/vfcon105149.jpg\", \"body_title\": \"$[SR.FirstName], you're running low \non data this month\", \"body_content\": \"Why not change your plan to avoid running low again? Switch to our $[SR.ProductDescription3] \nplan and you'll enjoy $[SR.MobileDataDescription] of data, unlimited minutes and unlimited texts for just \u00a3$[SR.RecCostText] a month.\n
Your contract end date will stay the same and if you change your mind you have 14 days to move back.\", \"button_text\": \n\"Change my plan\" } }, \"message\": { \"title\": \"You're running low on data\", \"expiry\": \"$[SR.TreatmentDynamicExpiry]\" }}\nStep 2: From the above example below are Data tokens\n a)$[SR.FirstName]\n b)$[SR.ProductDescription3] \n c)$[SR.MobileDataDescription] \n d)$[SR.RecCostText]\nStep 3 : We use PopulateOutputPropertiesForAppPushByTrigger strategy to populate data for Data Tokens.", "source": "VODKB-200723-160306.pdf"} {"id": "702b57000174-0", "text": "313\n \nStep 4: After populating the Data Tokens we will pass these data to End .\nStep 5: Platform Team use above data and Replace the Data tokens in the Appush Body Text.", "source": "VODKB-200723-160306.pdf"} {"id": "51b3723cbb70-0", "text": "314\nOBCC Output property mapping & file format :\nOutput file : Output file is a file that is used to write the output of the extractor case. At the end of every extractor run, an output file gets \ngenerated for each channel (OB CC, DM) and placed in a location specified in the AOMConfig datatype.\n <
tag with height and width. .e.g. \n Format :pega.web.api.doAction(\"\",\"\")\n1pega.web.api.doAction (\"VADRNewUpgrade\" ,\"load\");\n1\n2\n3\n4", "source": "VODKB-200723-160306.pdf"}
{"id": "0ecf5d395200-0", "text": "2357\n \nMashup Attributes\n \nPlease refer Mashup attributes for more details\nUpgrade Order\nWe created a mashup for creating a new Upgrade case in VADR and this mashup code(script) can be embedded in the host page. As per the Upgrade mashup code, it expects parameters defined in the \nd a t a - p e g a - a c t i o n - p a r a m - p a r a m e t e r s attribute, please refer Handoff Parameters for attributes needs to be passed for New Upgrade order. The below table specifies the mashup attribute values that need \nto be used for upgrade order and remaining attributes needs to be set based on external system requirement. \nRenegotiation Order\nWe created a mashup for creating a Renegotiation case in VADR and this mashup code(script) can be embedded in the host page. As per the Renegotiation mashup code, it expects parameters defined \nin the d a t a - p e g a - a c t i o n - p a r a m - p a r a m e t e r s attribute, please refer Handoff Parameters for attributes needs to be passed for Renegotiation.. The below table specifies the mashup attribute values that need \nto be used for Renegotiationorder and remaining attributes needs to be set based on external system requirement. \nHandoff Parameters data-pega-gadgetname Name for the mashup gadget which can be used to perform actions VADRNewUpgrade OR VADRRenegotiation\ndata-pega-action Action for the mashup createNewWork \ndata-pega-action-param-classname Case class VFUK-VADR-Work-Upgrade\ndata-pega-isretained To retain the state of the case after the user refreshes the browser that displays the mashup true OR false", "source": "VODKB-200723-160306.pdf"}
{"id": "0ecf5d395200-1", "text": "data-pega-isdeferloaded Specifies whether the action occurs when the Gadget Manager first loads the page or whether the action \nwaits until action invoked manuallytrue OR false\ndata-pega-applicationname Name of the Application VADR\ndata-pega-threadname The name of a thread in which the mashup action takes place Upgrade OR Renegotiation\ndata-pega-channelID This is the channel identifier. Please use the value provided. MASHUPaf9c64a149264e6daaa7a517119d8544\ndata-pega-resizetype Resize mode for the mashup.The attribute determines whether the mashup gadget fits into a fixed space \nor expands to fill the available space on the web page.stretch OR fixed\ndata-pega-url URL of the mashup application in the system https:///prweb/app/\nvadr/\ndata-pega-action-param-parameters JSON object for passing additional parameters such as user-defined parameters '{\"\":\u201d\u201d,\n\"\":\u201d\u201d,\"\n\":\u201d\u201d}'Attribute Purpose Values\nThe values enclosed within <> needs to be replaced with attribute-specific values.\ndata-pega-gadgetname VADRNewUpgrade\ndata-pega-threadname Upgrade\ndata-pega-action createNewWork\ndata-pega-action-param-classname VFUK-VADR-Work-Upgrade\ndata-pega-channelID MASHUPaf9c64a149264e6daaa7a517119d8544\ndata-pega-applicationname VADRAttribute Value\ndata-pega-gadgetname VADRRenegotiation\ndata-pega-threadname Renegotiation\ndata-pega-action createNewWork\ndata-pega-action-param-classname VFUK-VADR-Work-Upgrade", "source": "VODKB-200723-160306.pdf"}
{"id": "0ecf5d395200-2", "text": "data-pega-action createNewWork\ndata-pega-action-param-classname VFUK-VADR-Work-Upgrade\ndata-pega-channelID MASHUPaf9c64a149264e6daaa7a517119d8544\ndata-pega-applicationname VADRAttribute Value", "source": "VODKB-200723-160306.pdf"}
{"id": "c4bc05623a73-0", "text": "2358\nSample Mashup\nUpgrade Mashup code\nThe below is actual upgrade mashup code with place holders for all the parameters.\n Agent Data AgentId This is the Siebel User id of the agent New upgrade order & Renegotiation Yes Yes \nAgent Data Division This is the Siebel division for the pilot agent New upgrade order & Renegotiation Yes Yes \nAgent Data ParentDivision This is the Siebel parent division for the pilot agent New upgrade order & Renegotiation Yes Yes \nAgent Data ParentPosition This is the Siebel position for the pilot agent New upgrade order & Renegotiation Yes Yes \nSubscription \nDataUpgradingService\nNumberThis is the CTN of the mobile service that is being \ntaken through upgradeNew upgrade order & Renegotiation Yes Yes \nAccount Data OwnerAccountNu\nmberThis is the Owner Account Number associated with \nthe mobile serviceNew upgrade order & Renegotiation Yes Yes \nCustomer \nDataContactId This is the contact Id for the DPA'd contact New upgrade order & Renegotiation Yes Yes \nOrder Data DealId This is only used within the renegotiation flow and \nprovide the previous Deal IdRenegotiation No No The Number element of the \nAOM Upgrade CaseId\nSubscription \nDataAssetId This is the AssetId for the mobile subscription being \ntaken through upgradeNew upgrade order & Renegotiation Yes Yes This will be the row id of the \nroot service selected for \nupgrade\nAgent Data StoreId This is the Store Id associated with the agent New upgrade order & Renegotiation Yes No Future proofing for Retail\nOrder Data Action This denotes whether the handoff is a new upgrade \norder or re-negotiation\norderNew upgrade order & Renegotiation No Yes \nOrder Data OrderId This provides the order number of the order being", "source": "VODKB-200723-160306.pdf"}
{"id": "c4bc05623a73-1", "text": "Order Data OrderId This provides the order number of the order being \nrenegotiatedRenegotiation No No This will be provided to AOM on \nrenegotiation launch so that the \nnew renegotiated order can \ninclude the previous order. This \nwill allow Siebel to extract \nrelevant order details from the \nprevious order e.g. answers to \nthe affordability questions.\nCustomer \nDataAccountType This is the account type of the customer e.g. Small- \nBusiness/Consumer /Sole-Trader/Small-\nSME/Partner-Managed/CorporateNew upgrade order & Renegotiation Yes Yes \nChannel DataChannel This provides the channelfor the upgrade e.g. \ncallcentre/ retailNew upgrade order & Renegotiation Yes Yes \nOrder Data OrderType This is provided to inform AOM that this is a Flexi \nUpgradeNew upgrade order & Renegotiation Yes Yes \nLoan Lending \nDataLoanEligibilityStatu\nsThis details if the customer is eligible for a loan - \nValues = ELIGIBLE, INELIGIBLENew upgrade order & Renegotiation Yes Yes \nLoan Lending \nDataMaxOpenLoans Provides the maximumnumber of open loans forthe \nAccount Type &Account Categorycombination.New upgrade order & Renegotiation Yes No \nLoan Lending \nDataOpenLoans Count of all open loans for the customer. New upgrade order & Renegotiation Yes No \nLoan Lending \nDataProblemLoans Count of all open loans that has been in arrears. New upgrade order & Renegotiation Yes No \nLoan Lending \nDataConcurrentLoans Count of all open concurrent loans New upgrade order & Renegotiation Yes No \nLoan Lending \nDataConcurrentService\nLoansCount of loans with the Service Integration ID - If", "source": "VODKB-200723-160306.pdf"}
{"id": "c4bc05623a73-2", "text": "Loan Lending \nDataConcurrentService\nLoansCount of loans with the Service Integration ID - If \navailable.New upgrade order & Renegotiation Yes No Parameter \nTypeAOM Parameter \nName Parameter Description Upgrade Flow Encryption \nRequiredMandatory Notes\n1\n2\n3\n4\n5\n
\n
\n
\n
\n
\n
>\",\"Password\":btoa(\"<>\")\nAdd it to Mashup code under data-pega-action-param-parameters as shown below\nThis mashup code loads directly without asking user credentials.\n1\n2\n3\n4\n5\n6\n7\n8\n9\n10\n11\n12\n13\n14\n15\n16\n\n
>/MS/i\nndex.html?\nSite=Static&Section=TimeoutURL to redirect to on VADR timeout R3.01C o n f i g T y p e C o n f i g N a m e C o n f i g V a l u e N o t e s R e l e a\ns e\nAPIEndpoint GetCustom\nerhttps://<>/prweb/PRRestService/aom/v1/\ncustomerEnd point URL for external Api R2.4\nAPIEndpoint GetProduct\nListhttps://<>/prweb/PRRestService/aom/v1/\nproductlistEnd point URL for external Api R2.5\nAPIEndpoint GetRecom\nmendationshttps://<>/prweb/PRRestService/aom/v1/\nrecommendationsEnd point URL for external Api R2.5\nAPIEndpoint SubmitBask\nethttps://<>/prweb/PRRestService/aom/v1/\nbasket/submitEnd point URL for external Api R2.7\nAPIEndpoint ValidateBas\nkethttps://<>/prweb/PRRestService/aom/v1/\nbasket/validateEnd point URL for external Api R2.7\nAPIEndpoint ValidateDel\netehttps://<>/prweb/PRRestService/aom/v1/", "source": "VODKB-200723-160306.pdf"}
{"id": "3ac9faa9fa36-1", "text": "etehttps://<>/prweb/PRRestService/aom/v1/\nbasket/deleteEnd point URL for external API \n(new in R2.8)R2.8\nAPIEndpoint StockAvaila\nbilityhttps://<> End point URL for external Api R2.8\nAPIEndpoint GetNotificat\nionMessag\neshttps://<>/prweb/PRRestService/aom/v1/\ncustomer/notificationsEnd point URL for external API R2.12\nAPIEndpoint GetCustom\nerUsagehttps://<>/prweb/PRRestService/aom/v1/\ncustomer/usageEnd point URL for external API R2.12C o n f i g T y p e C o n f i g N a\nm eC o n f i g V a l u e N o t e s R e l e a\ns e", "source": "VODKB-200723-160306.pdf"}
{"id": "777399da6fe5-0", "text": "2564\nMashup\n APIEndpoint GetInvoiceL\nisthttps://<>/prweb/PRRestService/custome\nr/v2/invoice/list/queryEnd point URL for external API R3.01\nTimeToLive HandsetPro\nductList3600 Time to live in seconds for \nHandsetProductList data setR2.5\nTimeToLive TariffProduc\ntList3600 Time to live in seconds for \nTariffProductList data setR2.5\nTimeToLive InsuranceP\nroductList3600 Time to live in seconds for \nInsuranceProductList data setR2.6\nUpgradeMashupEn\ncryptionSecretKey tbAjBEtdzBD9xSBDCxL1JQBvaPZ5lCSvNNZGPT7UrjE=Secret key for Mashup encryptionR2.6\nUpgradeMashupEn\ncryptionSalt 3c2a27ab2ea59bc4 Salt for Mashup encryption R2.6\nUpgradeMashupEn\ncryptionInitialization\nVector717fe1d8ec6b105d Initialization vector for Mashup \nencryptionR2.6\nSecretsManger Region eu-west-1 The region to use for signing of \nrequestsR2.8\nSecretsManger Endpoint secretsmanager.eu-west-1.amazonaws.com The service endpoint R2.8\nUpgradeCase ActiveSecre\ntId AOM-DEV-ENCRYPTION-DETAILS Active SecretId to store / retrieve \nvalues from AWS using \nSecretsManagerR2.8\nUpgradeCase InactiveSec\nretId AOM-DEV-ENCRYPTION-DETAILS-2ndSet Inactive SecretId to store / \nretrieve values from AWS using", "source": "VODKB-200723-160306.pdf"}
{"id": "777399da6fe5-1", "text": "retrieve values from AWS using \nSecretsManagerR2.8C o n f i g T y p e C o n f i g N a\nm eC o n f i g V a l u e N o t e s R e l e a\ns e", "source": "VODKB-200723-160306.pdf"}
{"id": "da180a88cb1d-0", "text": "2565\nVADR Common Case Flows\nNotifySupport\nIf the error email details are populated, calls HandleAlerts flow and NotifySupportQueue flow sequentially\nElse calls NotifySupportQueue flow\nRoutes the case into Support work queue\nHandleAlerts\n \nSends email message to SupportEmail with SupportEmailSubject\nNotifySupportQueue\n \nRoutes the case into Support work queue\nResets ErrorStackTrace property\nCalls ResumeCase flow action \u2013 TBD?", "source": "VODKB-200723-160306.pdf"}
{"id": "1b0bbd426af6-0", "text": "2566\nFinalise\nThis will de-initialise and close the case\nPopulates case level CaseEndTime property with currentTimeStamp", "source": "VODKB-200723-160306.pdf"}
{"id": "b08fe687f924-0", "text": "2567\nVADR API Simulation\nBelow is the list of API\u2019s Consumed by VADR which need to be stubbed in a non-integrated environment.\nBelow Data transforms would helpful to set up the required data from the API as part of the Simulation Response\n GetCustomer AOM REST GetCustomerSimulatio\nnResponseSimulationResponse VFUK-VADR-Int-GC-API\nGetProductList AOM REST GetProductListSimulat\nionResponseSimulationResponse VFUK-VADR-Int-GPL-API\nGetRecommendation\nsAOM REST GetRecommendations\nSimulationResponseSimulationResponse VFUK-VADR-Int-GR-API\nValidateBasket AOM REST ValidateBasketSimulat\nionResponseSimulationResponse VFUK-VADR-Int-VB-API\nSubmitBasket AOM REST SubmitBasketSimulati\nonResponseSimulationResponse VFUK-VADR-Int-SB-API\nValidateDelete AOM REST ValidateDeleteSimulati\nonResponseSimulationResponse VFUK-VADR-Int-VD-API\nStockAvailability TIL SOAP GetStockAvailabilitySi\nmulationResponseGSASimulationResponse VFUK-VADR-Int-GSA-APIService API SourceAPI \nTypeActivity Name Data Transform Name Data Transform & Activity \nApplies To Class", "source": "VODKB-200723-160306.pdf"}
{"id": "1fd77eb02c9b-0", "text": "2568\nHandset Manufacturer Model Map\nData Model\nSources\nD_HandsetManufacturers\nGetUniqueManufacturers Report Definition\nD_HandsetModelsByManufacturer\nGetUniqueHandsetModels Report Definition\nData Model\nSourcesDeviceType Text (single line) N/A\nManufacturer Text (single line) Key, Read-only\nModel Text (single line) Key, Read-onlyName Type Options\nThis data page returns the different unique manufacturers that are part of the HandsetManufacturerModelMap data type for a particular \ndevice type.\nStructure List\nObject Type VFUK-VADR-Data-HandsetManufacturerModelMap\nMode Read-Only\nRuleset VADR-Rules\nScope Node\nData Source GetUniqueHandsetManufacturer\nInput Parameters DeviceType\nLoad Management - Reload \nif older than8 HoursD_HandsetManufacturers\nThis report definition searches the HandsetManufacturerModelMap data type and returns each different manufacturer from the data type \nfiltered by a specific device type, not returning duplicate manufacturers.\nObject Type VFUK-VADR-Data-HandsetManufacturerModelMap\nRuleset VADR-Rules\nFilterable by DeviceTypeGetUniqueManufacturers Report Definition", "source": "VODKB-200723-160306.pdf"}
{"id": "80e4469131e0-0", "text": "2569\nFilter options Use null if empty\nOutput Parameters Manufacturer\nThis data page returns the different models that are part of the HandsetManufacturerModelMap data type for a particular combination of \nmanufacturer and device type.\nStructure List\nObject Type VFUK-VADR-Data-HandsetManufacturerModelMap\nMode Read-Only\nRuleset VADR-Rules\nScope Node\nData Source GetUniqueHandsetModels\nInput Parameters Manufacturer\nDeviceType\nLoad Management - Reload \nif older than8 HoursD_HandsetModelsByManufacturer\nThis report definition searches the HandsetManufacturerModelMap data type and returns each different model from the data type filtered by \na specific combination of manufacturer and device type, not returning duplicate models.\nObject Type VFUK-VADR-Data-HandsetManufacturerModelMap\nRuleset VADR-Rules\nFilterable by Manufacturer AND DeviceType\nFilter options Manufacturer: Use null if empty\nDeviceType: Use null if empty\nOutput Parameters ModelGetUniqueHandsetModels Report Definition", "source": "VODKB-200723-160306.pdf"}
{"id": "2fa4e75f4d01-0", "text": "2570\nTariffMetadata\nData Model\nSources\nD_TariffMetadata\nGetT enureByT ariffType Report Definition\nData Model\nSources\n TariffType Text (single line) Key, Read-only\nTenure Text (single line) Key, Read-onlyName Type Options\nThis data page returns the different unique tenures that are part of the TariffMetadata data type for a particular tariff type.\nStructure List\nObject Type VFUK-VADR-Data-TariffMetadata\nMode Read-Only\nRuleset VADR-Rules\nScope Node\nData Source GetTenureByTariffType\nInput Parameters TariffType\nLoad Management - Reload \nif older than8 HoursD_TariffMetadata\nThis report definition searches theTariffMetadata data type and returns each different tenure from the data type filtered by a specific tariff \ntype, not returning duplicate tenures.\nObject Type VFUK-VADR-Data-TariffMetadata\nRuleset VADR-Rules\nFilterable by TariffType\nFilter options Use null if emptyGetTenureByTariffType Report Definition", "source": "VODKB-200723-160306.pdf"}
{"id": "d84763a3bef2-0", "text": "2571\nVADR Timeout\nVADR will timeout when the browser has been inactive for a set period of time. Upon timeout, the browser should redirect to a URL.\nThe timeout time is set in VADRConfig.\nThe timeout URL is set in VADRConfig.\nRecords in VADRConfig\nTimeoutInMilliseconds - UpgradeCase- value example for testing: 15000\nTimeoutURL - UpgradeCase- https:///MS/index.html?Site=Static&Section=Timeout \nProperties on VFUK-VADR-Work-Upgrade\nTimeoutInMilliseconds (text)\nTimeoutURL (text)\nInitialiseUpgrade activity (VFUK-VADR-Work-Upgrade)\nProperties are set from VADRConfig records:\nset .TimeoutInMilliseconds from VADRConfig\nset .TimeoutURL from VADRConfig\nJavascript in Section rule AccountHeaderCustom (VFUK-VADR-Work-Upgrade)\nJavascript functions on the HTML tab:\np e g a : r e f e r e n c e tags retrieve values of case level properties TimeoutInMilliseconds and TimeoutURL.\nfunction setListeners() - Registers user event listeners. This registers the events in the body of the page. The body is referenced in the \nSection html as in the following: $('body').on('mousemove', resetTimer); \nfunction startTimer() - This is called when VADR is started and will start a timer.\nfunction resetTimer() - This is called whenever the user is active (i.e. mouse movement or key strokes). It will reset the timer.\nfunction timeoutAction() - If set time is reached, then this function is called. This should redirect to the specified url.\nThe setListeners and startTimer functions are called from the $(document).ready function. This is called when the page is loaded.\nStatic Pages Microsite", "source": "VODKB-200723-160306.pdf"}
{"id": "d84763a3bef2-1", "text": "Static Pages Microsite\n New Microsite Case that will use the Section request parameter to determine the section to be displayed.The time to be consider for session timeout can be configured on VADRConfig Datatype with ConfigName TimeoutInMilliseconds. \nTime should be in milliseconds. To Reflect the update values,flush datapage D_VADRConfig.\nMicrosite Case that displays the Timeout Section. \u2018Timeout\u2019 is passed as the Section parameter.\nApplies To PegaMKT-Work-Microsite-StaticMicrosite Case - Static", "source": "VODKB-200723-160306.pdf"}
{"id": "402ed309630a-0", "text": "2572\nRuleset AOMFW\nParameters Section - This parameter will determine the Section rule to display\nChecks if the Section parameter passed to the Microsite is a valid Section rule.\nIf Section parameter is null or empty or is not an existing Section rule, then ErrorStackTrace and ErrorMessage are set. Record is written to \nAOM Error table.\nApplies To VFUK-FW-AOMFW-UI-Microsite-Static\nRuleset AOMFW\nThrows Primary Catch-all Error Handler: Catches error if Section paramater is null or empty or an invalid rule name.Activity - InitialiseStatic\nDisplays message to inform user of application timeout.\nOK button closes the browser and sets Case to Resolved-Completed.\nApplies To VFUK-FW-AOMFW-UI-Microsite-Static\nRuleset AOMFW-UI \n \n Section - Timeout\nDisplays message to inform user of application timeout.\nOK button closes the browser and sets Case to Resolved-Completed.\nApplies To VFUK-FW-AOMFW-UI-Microsite-Static\nRuleset AOMFW-UI Section - Exception", "source": "VODKB-200723-160306.pdf"}
{"id": "fc2e0ec72c83-0", "text": "2573", "source": "VODKB-200723-160306.pdf"}
{"id": "423ecdfc6df1-0", "text": "2574", "source": "VODKB-200723-160306.pdf"}
{"id": "efae20da3937-0", "text": "2575\nVADR UI solution design\nTime Out Design\n \n1. Reuse html created by Simon. Instead of calling for URL. It will perform \u2018Click\u2019 action on the button \n \n2. Create an invisible button to trigger an action on click", "source": "VODKB-200723-160306.pdf"}
{"id": "3751fcdd0c4d-0", "text": "2576\n \n \n3. On click, Timeout property will be set to true, and assignment will finish.\n4. Layout flow: Decision will be added to check timeout flag, if true Change stage to \u2018Abort\u2019", "source": "VODKB-200723-160306.pdf"}
{"id": "cd141ed7381c-0", "text": "2577\nIssue Trouble Shooting\nError while Encrypting Mashup Parameters\nIssue:\nError while Decrypting using AES256\nRoot Cause:\nKeys required for encrypting Mashup Parameters are not configured correctly.\nSolution:\nRaise with Siebel team to get correct encrypting secret keys by sharing the secret keys configured on VADR\nCheck the below key \nInitializationVector\nSalt\nSecretKey\nReference ADO: 496447\n \nCustomer Address Not Visible \nIssue:\nCustomer Address details not visible on VADR screen, even though TIL is sending Address details for the Customer.\nRoot Cause:\nIdentified there is difference in structure for the response coming on TIL and Spec shared with AOM\nSolution:\nGet the latest spec details from TIL and implemented as new Technical User Story.\nReference ADO: 570105\n \nError: Property is in withdrawn state \nIssue:\nGet Recommendations getting failed with property is in withdrawn state\nRoot Cause:\nAs part of Performance test one of the strategies moved to Local ruleset and that strategy in Local ruleset causing the issue.\nGenerally, strategies will not be in Local ruleset. \nSolution:\nRemove the rule (Strategy) from local ruleset.\nReference ADO: 580253", "source": "VODKB-200723-160306.pdf"}
{"id": "a3b222ae77ca-0", "text": "2578\nGetCustomer API Testing failing with Internal Server Error\nIssue:\nGetting 500 error code {\"Error\u201d: \u201cInternal Server Error\"} while performing GET Customer API Testing\nRoot Cause:\nFound Data gap on Product Catalogue tables. Products are missing from tables\nSolution:\nMaintaining an exception list of products that can be filtered from GPSL to ensure Get Customer and logic processing are not impacted.\nReference ADO: 590292/ 591689\n \nRequest/Response Validation Failing on API calls\nIssue:\nRequest/Response validation will be failed either with Invalid values or Mandatory fields missing from the request.\nRoot Cause:\nAOM will check both request and response for any API call with Mandatory and LOVs which are provide for the respective API Spec \nSolution:\nPlease check for logs on aom_error and audit_log tables of AOM for the specific API call which have information on invalid value\nReference ADO:592846/631636\n \nData Available in Staging table but not in View\nIssue:\nData is available in Statging Table(Product_holding) but missed from View.\nRootCause:\nThe data was not merge on to the main table because the product holding file had the same record_ts value as the previous product \nholding file.\nIf the record_ts is the same between files, then the file is considered the same and the data is not merged to main files. This is for \nperformance reasons.\nSolution:\nUpdate the file and run the Loader case.\n \nNo Products Available Response on the GetProductList API\nIssue:\nNo product are turned as response for GetProductList API while editing the deal.\nRootCause:\nWhile editing the deal,on selecting the handset, and then switching to tariff as there are no compatible tariffs for for given handset", "source": "VODKB-200723-160306.pdf"}
{"id": "b3387420753b-0", "text": "2579\nSolution:\nWorking as expected.\nReference ADO:610097\n \ndata-pega-isretained attribute\nIssue:\nWhile Agent launching VADR Upgrade case,getting Error with Recommendations for all cases \nRootCause:\nIf data-pega-isretained is set to \"true\" then an agent will not be able to perform upgrades for different subscriptions as the browser will \nmaintain the state and relaunch the same case for the original subscription \nSolution:\nUpdate the data-pega-isretained attribute value from true to false on HTML for launching the Upgrade.\nReference ADO:619557\n \nVADR Connectors\n \nGetCustomer TIL Services\nGPSL(SEIBEL),GCPL(SEIBEL),\nCRE(Chordiant)\nSpines\nSubscription, Account, Device, \nProductHolding, \nProductReferences \nGetRecommendations CatalogueData\nProduct(Handset,Tariff,Service,A\nccessory),Offer(VFT_Offers)\nSpines\nBDCModelScore(UniversalTariff\nRecommendation,Device/Conver\ngenceRecommendations),SubFl\nexAttributes \nGetProductList CatalogueData\nProduct(Handset,Tariff,Service,A\nccessory),Offer(VFT_Offers) and \nProductattributes-PMTool\nConfig\nAOMConfig,AOMBUSinesssConf\nig \nGetNotificationMessage STAC,PAC Events, \nSubFlexAttributesAPI Name Pre-Requiste Data Model Sample Request Sample Response\nGC_Requ\n28 Apr 2022, 07:10 AMest.txt GC_Respo\n28 Apr 2022, 07:10 AMnse.txt\nGR_Requ\n28 Apr 2022, 07:14 AMest.txt GR_Respon\n28 Apr 2022, 07:14 AMse.json\nGPL_Requ", "source": "VODKB-200723-160306.pdf"}
{"id": "b3387420753b-1", "text": "28 Apr 2022, 07:14 AMse.json\nGPL_Requ\n28 Apr 2022, 07:25 AMest.txt GPL_Respo\n28 Apr 2022, 07:25 AMnse.txt", "source": "VODKB-200723-160306.pdf"}
{"id": "173216c9b768-0", "text": "2580\n \n \n \n \nValidateBasketTIL service\nGetStockAvailabilty\n(SEIBEL)\n \nSubmitBasket TIL service\nCreateSalesOrder(SEIBEL)\n GetNotifcation_\u2026\n28 Apr 2022, 07:38 AMest.txt GetNotifcation_\u2026\n28 Apr 2022, 07:39 AMnse.txt\nVB_Requ\n28 Apr 2022, 07:39 AMest.txt GSA_R\n28 Apr VB_Respo\n28 Apr 2022, 07:40 AMnse.txt GSA_R\n28 Apr \nSB_Requ\n28 Apr 2022, 07:40 AMest.txt CSO_R\n28 Apr SB_Respo\n28 Apr 2022, 07:41 AMnse.txt CSO_R\n28 Apr", "source": "VODKB-200723-160306.pdf"}
{"id": "89458beb902e-0", "text": "2581\n914083: Provide the ability to switch the access controls/groups of agents in bulk\nDatabase Table\noperator_access_group\nClass Mapping\nClass : VFUK-VADR-Data-OperatorAccessGroup\nProperties : \nOperatorId - Text\nAccessGroup - Text\nData Type\nCreate OperatorAccessGroup Data Type on VFUK-VADR-Data-OperatorAccessGroup class with OperatorId and AccessGroup columns.\nActivityoperator_id varchar(255) yes yes\naccess_group varchar(255) yes yesColumns Type Not Null Primary Key\nReads data records from OperatorAccessGroup datatype and update Operator ID rule with given access group.\nApplies To VFUK-VADR-Data-OperatorAccessGroup\nRuleset VADR-Rules\nInput \nParametersNA\nOutput \nParametersNA\nError \nHandlingPrimary Catch-all Error Handler: Catches all the unhandled Exceptions or Errors in the activity\nObj-Open Failure Error Handler: Captures the records which were not found from the Data type\nLogic If the Data Type is empty, exit the activity\nLoop through the list of Data Type records\nValidation - Check whether the Access Group and Operator ID rule exists or not\nIf both exists then continue, otherwise append appropriate error message and continue with next records\nOpen Operator ID rule object and replace existing Access Group with new one given mentioned in datatype, make the \nnew Access Group as default in the operator rule and Save it\nTruncate OperatorAccessGroup Data Type records\nIf error message is not empty, write it to error logActivity Name: ReplaceOperatorAccessGroup", "source": "VODKB-200723-160306.pdf"}
{"id": "9b3cf631a60b-0", "text": "2582\n \n Delete all records from operator_access_group table\nApplies To VFUK-VADR-Data-OperatorAccessGroup\nRuleset VADR-Rules\nCommand truncate table operator_access_groupConnect SQL Name: Truncate", "source": "VODKB-200723-160306.pdf"}
{"id": "b7232feab694-0", "text": "2583\nHow to switch access groups of agents in bulk\nCreate a CSV file with operators and access groups as below\nIn VADR, click on Data types explorer to open OperatorAccessGroup datatype\nClick on OperatorAccessGroup data type and go to Records tab to import the above created CSV file\nClick on import button to browse the CSV file and select Add only on the Purpose dropdown and click on next>next to go to 3rd page", "source": "VODKB-200723-160306.pdf"}
{"id": "790bd9fd225d-0", "text": "2584\nOn 3rd page, click on start validation button to validate the given records in CSV file.", "source": "VODKB-200723-160306.pdf"}
{"id": "3e857ac882f2-0", "text": "2585\nClick on Continue Import button after successful validation as shown below\nCheck the current import statistics and click on Finish button to complete the import", "source": "VODKB-200723-160306.pdf"}
{"id": "bb8434169faa-0", "text": "2586\nAfter clicking on Finish button, records are added to data type as shown below\nSearch for ReplaceOperatorAccessGroup activity in search box and open the activity\nOpen the activity and click on Action>Run", "source": "VODKB-200723-160306.pdf"}
{"id": "c4cf66fc02d4-0", "text": "2587\nNext click on Run button on the pop up screen to run the activity to change the operator rules with given access groups\n \nAfter completion of activity run, a status page will be shown as below\nOnce the activity is successful, you can check the operator rules with new access groups you specified in the CSV file.\nGo to Records explorer and expand Organization and click on Operator ID rule to see the latest updated operator rules with updated \ntime, name and access group", "source": "VODKB-200723-160306.pdf"}
{"id": "bcd3205fc25c-0", "text": "2588\nClick on the operator rule to check whether the operator rule is updated with given access group or not\nAll the access groups for the given operators in the CSV file are updated correctly.", "source": "VODKB-200723-160306.pdf"}
{"id": "646b07963a6f-0", "text": "2589\n1063194 - VADR Performance - AWS Secret Cache\nRetrieving the secret key from AWS, which is used to decrypt the context data when launching VADR, takes almost 0.8 seconds (in DEV) \nbecause there is a cost for calling the Secrets Manager API. As a best practice, it is suggested to cache the secret key to speed up the \nVADR start-up.\nOne suggested approach is to store it at a node level to improve the performance of all the processes that will run on that node. It may also \nbe possible to pre-load the key to avoid the slow response of the first call (the one without a cache). \nIt is also required to implement an appropriate retention strategy to update the cache.\nDevelopment phase:\nThe old function GetAWSSecretString is replaced with GetCachedAWSSecretString (New function) \nA jar file was imported and com.amazonaws.secretsmanager.caching.SecretCache, \ncom.amazonaws.secretsmanager.caching.SecretCacheConfiguration were added to the VADRUtilities library \nAWS_SECRET_CACHE - Static variable which contains a TimeToLive in which the cache remains for a period of 1 day and contains the \nbuilder configuration as well as the endpoint and region\nThe new function GetCachedAWSSecretString takes in the SecretId - specified in the VADRConfig - provided via the Initialise Upgrade \nactivity and uses the static variable to get the SecretString.\nThe region and endpoint have been removed from Config as now they are being hardcoded in the AWS_SECRET_CACHE static \nvariable\nInitially the amount of time taken to retrieve the SecretString is longer since it is not cached; it then is cached and therefore the launches \nafter would take less time.\nTesting phase:\nBelow is screenshot of how long it takes for the old function to retrieve the SecretString each time VADR is launched", "source": "VODKB-200723-160306.pdf"}
{"id": "646b07963a6f-1", "text": "Below is screenshot of how long it takes for the old function to retrieve the SecretString each time VADR is launched\nBelow is screenshot of how long it takes for the new function to retrieve the cached SecretString each time VADR is launched", "source": "VODKB-200723-160306.pdf"}
{"id": "50348196e271-0", "text": "2590\n4.4 Sprint Tasks", "source": "VODKB-200723-160306.pdf"}
{"id": "323820cc706a-0", "text": "2591\n1083261 - Display the Tiers in the Summary Screen\nDescription:\nThe Commission Tier should be displayed in the Basket Summary Screen near the TNR in TSAR, unfortunately, this is a requirement miss \nin the original user story (525234)\n \nAcceptance criteria:\nA TSAR Agent launches VADR with a Mobile, MBB CTN\nThe Recommendations loads as per 'As Is'\nThe Agent selects a card with a Commission Tier displayed (either straight from the Recommendation Card or via a Edited Card)\nThe Agent lands on the Summary Basket as per 'As Is'\nIn the summary section in the 'For Agent only' section , the Tier is displayed near the TNR ('Tier: 1' or 'Tier: 2')\nIf the deal did not yield any Tiers, then nothing is displayed (as per 'As Is' for other part of the application)\n \nThis Section displays Basket screen footer\nApplies To VFUK-VADR-Work-Upgrade\nRuleset VADR-UI\n Add tier label & property\nAdd visibly condition to display when populated else do not display \nCorrect paddings according to InvisionSection - EditBasketDeal", "source": "VODKB-200723-160306.pdf"}
{"id": "f772045d95be-0", "text": "2592", "source": "VODKB-200723-160306.pdf"}
{"id": "1c7b6188ff6a-0", "text": "2593\n1083193 - Summary Screen Benefit Revamp to remove the pictures/Icons\nDescription:\nThe Management of the Summary Screen Benefit pictures is difficult to manage in BAU as they require a code release and can only be \nmanaged via string matching - which leads to issues when the CMT team updates the tariff or device benefits in the source data\nAs result, we have agreed we will remove the pictures/Icons in order to simply the BAU management and to ensure we do not dilute the \ninformation displayed on screen\nAcceptance criteria:\nAn Agent navigates to the Summary Screen\nIn the Airtime Benefits section, the Benefits Icons are not longer displayed. Instead the 'As Is' benefit titles are displayed within a box with a \n'+'(see invision for look and feel)\nThe Plan name and the green Info box are displayed as per 'As Is'\nIn the Device Benefits section, the Benefits Icons are not longer displayed. Instead the 'As Is' benefit titles are displayed within a box with a \n'+'(see invision for look and feel)\n \nTask ADO - 1236294\nAn Agent navigates to the Summary Screen\nIn the Airtime Benefits section, the Benefits Icons are not longer displayed. Instead the 'As Is' benefit titles are displayed within a box \nwith a '+'(see invision for look and feel)\nThe Plan name and the green Info box are displayed as per 'As Is'\nIn the Device Benefits section, the Benefits Icons are not longer displayed. Instead the 'As Is' benefit titles are displayed within a box \nwith a '+'(see invision for look and feel)", "source": "VODKB-200723-160306.pdf"}
{"id": "9f7478239840-0", "text": "2594\nThis Section displays Basket screen\nApplies To VFUK-VADR-UI-Deal\nRuleset VADR-UI\n \n \n Change layout\n \nRemove max_width and add new container.Section - DisplayBasketBundles", "source": "VODKB-200723-160306.pdf"}
{"id": "61e0fb8952bf-0", "text": "2595\n \nThis Skin used thought out VADR system.\nApplies To VFUK-VADR-UI-Deal\nRuleset VADR-UI\n Remove following width. change it to 3 proportional column\nAdd new containerSkin - UpgradeSkin", "source": "VODKB-200723-160306.pdf"}
{"id": "d470d3fae7b8-0", "text": "2596\n \nDisable following layout\nAdd padding according to invisions\nAdd border\n \nThis Section displays benefit Icon and name\nApplies To VFUK-VADR-UI-ProductBenefit\nRuleset VADR-UI\n Remove dynamic layout to display icon \nAdd static + icon\nRemove visibility condition & Keep only one section\ndefine class to control width in each breakpointSection - DisplayBenefit", "source": "VODKB-200723-160306.pdf"}
{"id": "dcdae428c396-0", "text": "2597\n \n \n \nThis activity adds icon file to TariffBenefitsList, DeviceBenefitsList, TariffComplimentaryBenefitsList\nApplies To VFUK-VADR-UI-ProductBenefit\nRuleset VADR-UI\n Remove code which adds icons to above list Activity - ProcessBaketDeal\nCSS file to override Pega OOTB elements\nApplies To N/A\nRuleset VADR-UI\n Add width for benefit text as per each resolution to fit in the box.\n Text file - vf-custom-style-breakpoints-css", "source": "VODKB-200723-160306.pdf"}
{"id": "2c8b7d237b5e-0", "text": "2598\n1083201 - TSAR - Update the stock display in TSAR to be inline with Retail look\nand feel\nDescription:\nDuring Pilot, we got feedback that the hover to see the stock level was hard to use. As a result, we would like to display the stock level \nwithout an hover similar than in Retail\n \nAcceptance criteria:\nA TSAR Agent launches VADR for Mobile, MBB or watch CTN\nThe Recommendation screen loads as per 'As Is'\nThe Agent navigates to the Edit Tab and lands on the Device Tab as per 'As Is'\nThe stock for the top 5 devices (MBB, Mobile) is automatically checked as per 'As Is'\nThe stock display is updated as per below:\nIf the device is in stock then display the quantity followed by 'in stock' (for example '10 in stock') in green\nIf the device is on pre order, then display 'Pre order' in red (Pre order stock level are not displayed)\nIf the device is in backorder, then display 'Back order' in black (back order stock level are not displayed)\nIf the stock level is unknown, then display 'unknown' in red (i.e. if GSA is down)\nIf a Top device is out of stock, then recommend the next device in stock as provided by Big Data (mobile) or ADM (MBB) as per 'As Is' \n(see ADO 966558) i.e. Top 5 will never have an out of stock status\nFor all devices except top 5 devices, the following information is displayed in the \"Stock level' column:\nA 'Check' button is displayed\nThe Agent clicks on the 'Check' button\nVADR calls GetStockAvailability\nThe stock is displayed as per above", "source": "VODKB-200723-160306.pdf"}
{"id": "2c8b7d237b5e-1", "text": "VADR calls GetStockAvailability\nThe stock is displayed as per above\nIn addition, If the device is not in stock, then display 'Not in stock' in red\nStart (invisionapp.com)", "source": "VODKB-200723-160306.pdf"}
{"id": "b3974b38bc15-0", "text": "2599\n \nThis data transform sets stock status \nApplies To VFUK-VADR-UI-Device\nRuleset VADR-UI\n replaced with decetion table \n Data transform - SetStockDetails\n \nApplies To VFUK-VADR-UI-Device\nRuleset VADR-UI\n Change condition from \u2018In stock\u2019 to \u2018in stock\u2019 \n when - IsInStock\nThis sections are for device table for handset, MBB & watch\nApplies To VFUK-VADR-UI-Deal\nRuleset VADR-UI\n Added new section \u2018Stock Level\u2019Section - RefineDeviceResults, RefineDeviceResultsForMBB, RefineDeviceResultsForWatch", "source": "VODKB-200723-160306.pdf"}
{"id": "2584b1fb5a92-0", "text": "2600\n \n \n \n \nThis section to display Stock status and stock level\nApplies To VFUK-VADR-UI-Deal\nRuleset VADR-UI\n \n \nChange visibility conditionsSection - StockLevelCheckForInbound\nData transform ClearDeviceCurrentSelection\n SetSelectedDevice\n SetStockDetails ( covered above)\nWhen IsOutofStock\n IsPreOrder\n Activity EditDealDeviceSelected\n ManageSelectionsInTabsChange following artifact for Change wording \u2018Out of stock\u2019 to 'Not in stock'", "source": "VODKB-200723-160306.pdf"}
{"id": "e1db102c4aac-0", "text": "2601", "source": "VODKB-200723-160306.pdf"}
{"id": "5e789039b20f-0", "text": "2602\n1082376 - Being able to change CTN\nDescription:\nWe would like to be able to see the following information easily in VADR:\nSpend manager for other CTNs on the Account\nBilling information for other CTNs on the Account\nUsage information for other CTNs on the Account\nAs a result, this US details the need a for a drop down listing PAYM Mobile and PAYM MBB CTNs so we are able to see their Usage/Billing \nwithout having to relaunch VADR\nPlease note, home will not be able to able to be selected. To be get more info on these lines , the Agent can continue to view the info in the \nAccount Opened Lines\nAcceptance criteria:\nAn Agent (Retail or TSAR) launches VARD for CTN (Mobile, Watch, MBB) that belongs to an account with several Mobile and/or MBB \nsubscription\nThe Recommendations screen loads as per 'As Is'\nAt the top of the screen, the CTN in context is displayed in a larger box with a title: Upgrade for. Before the CTN number, the CTN type i.e. \nPAYM (Mobile/Watch), MBB is displayed followed by a dash\nThe Customer Billing and Usage information is displayed in a larger section delimited by a box\nAbove the Billing and Usage Tabs a new section is presented with a drop down\nPrior to the drop down a title is presented 'Customer details for:'\nWhen 1st loading the application the ' Customer details for ' drop down defaults the CTN used when launching the application from Halo\nThe Agent selects the drop down. PAYM Mobile and watch and PAYM MBB CTNs are listed in the same order than in the Account opened", "source": "VODKB-200723-160306.pdf"}
{"id": "5e789039b20f-1", "text": "line (i.e. PAYG and Home Subscriptions are not displayed). The CTNs are displayed using the 44 format as per 'As Is' in the application\nFollowing the drop down, an 'i' icon is presented with the following message 'Switching numbers for customer details does not change the \nnumber being upgraded.'. The message is always displayed (Please see Invision for look and feel)\nAlongside the CTN numbers in the drop down, an indication of the CTN Type is displayed (PAYM/MBB) followed by a dash\nBelow the new drop down, a new divider line is presented\nThe Billing and Usage tabs (and spaces for other info tabs) are presented as per 'As Is' with the tab titles being aligned to the left\nThe Agent selects another CTN from the drop down list whilst in the Billing Tab\nThe Billing (including Spend manager) information is refreshed using the new CTN in context. The Agent navigates to the Usage Tab. The \nUsage displayed is for the 'Customer details for' selected CTN (or vice versa, if the agent is in the Usage tab and changes the' Customer \ndetails for' CTN, then the Usage Tab is updated and the Agent is able to navigate to the Billing Tab to see the relevant billing info)\nThe newly selected CTN is now shown as selected in the 'Customer details for' (so they Agent can easily identify that Billing and the Usage \nare related to the CTN selected by the 'Customer details for' drop down)\nThe Recommendations, 'Existing Products', 'Airtime end date', 'Upgrade today fee's' do not change and still display the data linked to the \nCTN used to launch the application from Halo\nThe Agent is able to select another CTN in the 'Customer details for' drop down or selects back the upgrading CTN in context as relevant", "source": "VODKB-200723-160306.pdf"}
{"id": "573e01661b79-0", "text": "2603\nThe Agent navigates to the Customer information panel and returns to the Recommendations screen. The Usage and Billing information \ndisplayed is for the CTN that was last selected in the ''Customer details for' is still displayed\nThe Agent navigates to the Edit Screens and returns to the Recommendations screen. The Usage and Billing information displayed is for \nthe CTN that was last selected in the ''Customer details for' is still displayed\nIf the Account has only one PAYM MBB or one PAYM Mobile, then the ''Customer details for' contains only one CTN\nStart (invisionapp.com)\nInvision extract:\n \nThis new section is for CTN dropdown & CTN details\nApplies To VFUK-VADR-Work-Upgrade\nRuleset VADR-UI\n create dropdown with CTN list\ncreate lable for fix text\nin Dropdown action call Following activities\nrefresh current section\non refresh it will trigger DisplayMenu section\n Section - DisplayCustomerProfile \nThis new section is for to display menu. It is HTML section\nApplies To VFUK-VADR-Work-Upgrade\nRuleset VADR-UI\n create new ready function ( this will trigger by default)\nThis function have a when rule to decide which section to be display.\nif user control is in Usage, the usage section will refresh with selected CTN data.\nif user control is in billing, the billing section will refresh with selected CTN data.Section - DisplayMenu", "source": "VODKB-200723-160306.pdf"}
{"id": "77513f39fa8f-0", "text": "2604\n \nThis new class to store CTN list & require property to pass to other API\n Property List:\nDisplayCTN - to display in dropdown\nServiceNumber - to pass to GetInvoiceList API\nSpendManagerValue - to display on screen\nSubscriptionId - to pass to GetCustomerUsage API\nUniqueKey - subscriptClass - VFUK-VADR-UI-CustomerDetails (New)\nThis new data tranform to to store data in CustomerDetails (page group)\nApplies To VFUK-VADR-Work-Upgrade\nRuleset VADR-UI\n Page defination : VFUK-VADR-UI-CustomerDetailsPage Group - CustomerDetails (New)\nActivity to get customer detail\nApplies To VFUK-VADR-Work-Upgrade\nRuleset VADR-UI\n Updated to call SetCustomerDetails Data transformActivity - GetCustomer\nThis new data tranform to to store data in CustomerDetails (page group)\nApplies To VFUK-VADR-Work-Upgrade\nRuleset VADR-UI\n data is populated form customer subscription.Data transform - SetCustomerDetails (New)\nActivity to get customer billing detail\nApplies To VFUK-VADR-Work-Upgrade\nRuleset VADR-UI\n populate initial selectedCTNtype to determine which usage table to display before selecting CTN from dropdwn.Activity - MapDataForUI", "source": "VODKB-200723-160306.pdf"}
{"id": "e2a6b53d5d7c-0", "text": "2605\nActivity to get customer billing detail\nApplies To VFUK-VADR-Work-Upgrade\nRuleset VADR-UI\n Updated to Set the Request Values - set msisdn, Default it will be UpgradingServiceNumber and in case \nMISDN selected by dropdown then selected MISDNActivity - GetInvoiceList\nActivity to get customer billing detail\nApplies To VFUK-VADR-Work-Upgrade\nRuleset VADR-UI\n Updated to Set the Request Values - Set the Request Values : Default it will be SubscriptionId and incase \nMISDN selected by dropdown, then selected SubscriptionIdActivity - GetCustomerUsage\nActivity to get customer billing detail\nApplies To VFUK-VADR-Work-Upgrade\nRuleset VADR-UI\n Updated to Populate the SpendManagerValue and Selected CTN type for CTN selectedActivity - CustomerProfileBillingClicked\nActivity to get customer billing detail\nApplies To VFUK-VADR-Work-Upgrade\nRuleset VADR-UI\n populate initial selectedCTNtype to determine which usage table to display before selecting CTN from dropdwn.Activity - MapDataForUI", "source": "VODKB-200723-160306.pdf"}
{"id": "1fac90473d4c-0", "text": "2606\nRetail", "source": "VODKB-200723-160306.pdf"}
{"id": "6f69e68eee6c-0", "text": "2607\n1082203 - Retail: Remove Tiers\nRecommendation -Retail Copy 3 (invisionapp.com)\nTask ADO - 1231372 \nDisable Tier column in Tariff and Accessories Edit Screen/tab\nOn the tariff tab, Tiers should not be displayed on the hover of the tariff name. Update RefineTariffResults and \nRefineTariffResultsForMBB sections\nUpdate RefineDiscountsResults section to include a new dynamic layout specific to Retail agent\nDisable Tier information on the selected basket and selected products\nImpacted Screens\nRecommendation Screen (VFUK-VADR-UI-Deal.DisplaySubscriptionBundles)\nSelected Basket (VFUK-VADR-UI-Deal. EditDealSelectedDeal)\nBasket Summary Screen (VFUK-VADR-UI-Deal.DisplayBasketBundles)\nDifference between TSAR and Retail\nThis is mainly dependent on the Channel\nIn the Mashup DT, there is Channel parameter - for a TSAR agent launch screen, Channel will be InboundCC and for Retail agent Launch \nscreen, Channel will be Retail\nFor conditions on visibility etc. use function String.EqualsIgnoreCase - since it is not clear how the word Retail will be presented to us.\n \n \nThis section to display selected products\nApplies To VFUK-VADR-UI-Deal\nRuleset VADR-UI\n Update the visibility condition of the Tier to check if the Channel is RetailSection - DisplaySubscriptionBundles", "source": "VODKB-200723-160306.pdf"}
{"id": "1ceff9c03008-0", "text": "2608\nThis screen is used to edit the selected products\nApplies To VFUK-VADR-UI-Deal\nRuleset VADR-UI\n Update the visibility condition of the Tier to check if the Channel is RetailSection - EditDealSelectedDealFooter\nThis Section displays Basket screen footer\nApplies To VFUK-VADR-Work-Upgrade\nRuleset VADR-UI\n Update the visibility condition of the Tier to check if the Channel is RetailSection - EditBasketDeal\nThis section is used to display Discounts tab\nApplies To VFUK-VADR-UI-Deal\nRuleset VADR-UI\n Add new dynamic layout specific to Retail agent in which Tier column will be removedSection - RefineDiscountsResults\nThis section is used to display Tariffs tab\nApplies To VFUK-VADR-UI-Deal\nRuleset VADR-UI\n Update visibility condition of the smart tip of Tariff Name to check if Channel is RetailSection - RefineTariffResults", "source": "VODKB-200723-160306.pdf"}
{"id": "c6c875ed36c2-0", "text": "2609\n1079501 - Retail: Renegotiation\nAcceptance Criteria\nThe Renegotiation functionality is available in Retail and works as per 'As Is' (see feature 781015)\nAn upgrade deal placed into a Pending state in Halo by a TSAR Agent may be re-opened by a Retail Agent and vice versa\nThe validation rules applies as per 'As Is' \nIf a Retail pending deal is renegotiated in a different store, the stock is checked for the Renegotiation Agent \u2018store. If the device is not in \nstock in the new store and not in pre/back order in the warehouse, then the stock error message is displayed\nIf a Retail pending deal is renegotiated in TSAR, the stock check is checked for the Warehouse only. If the device is not in stock/ in \npre/back order in the warehouse, then the stock error message is displayed. The TNR is recalculated and the TSAR TNR is displayed \ninstead of the Retail TNR. The TNR Slider is not displayed in TSAR as per 'As Is'\nIf a TSAR pending deal is renegotiated in Retail, the stock check is checked for the renegotiating Agent's store and for back order/pre \norder in the Warehouse. The TNR is recalculated and the Retail TNR is displayed instead of the TSAR TNR. The TSAR Slider is \ndisplayed and set to hide the TNR as per 'As Is' when 1st launching VADR\nWhilst VADR and Accord are dual running, it is not possible to renegotiate an Accord originated deal in VADR and vice versa. The 'As Is' \nerror message is displayed in Halo to prevent a pending order to be launched in a different system than the originating system", "source": "VODKB-200723-160306.pdf"}
{"id": "1b346f8e7487-0", "text": "2610\n1079515 - Retail: Hand back a Retail deal to Halo\nTask ADO - 1235437\nNeed to check the channel name case if its (upper or lower ) which would be part of the VADR Mashup parameters\nConvertCommonChannelToAOMChannel DT needs to be updated\nAOM Changes\nNeed to update the Connect SQL in the below Datapages \nUpdate condition as:\nwhen ('{ASIS:Channel}' in ('InboundCC', 'Retail') to the following data page connect SQLs : \nD_SellablePaymHandsetBySKU(ConnectSQL :GetSellablePaymHandsetBySKU)\nD_SellablePaymHandsets ( ConnectSQL : GetSellablePayMHandsets)\nD_SellableBars(ConnectSQL :GetSellableBars)\nD_SellableAccessories(ConnectSQL :GetSellableAccessories)\nD_DiscountsForTariff(ConnectSQL :GetDiscountsForTariff)\nD_EligibleTariffs (ConnectSQL: GetTariffsForDept)\nD_ServicesForTariff (ConnectSQL :GetServicesForTariff)\nD_EligibleTariffsForHandset ( ConnectSQL :GetTariffsForHandset\nThis datatransform is called in InitialiseUpgrade activity which sets the Channel to InboundCC automatically regardless of any other channel\nApplies To VFUK-VADR-Work-Upgrade\nRuleset VADR-Rules\n Addition Info: Need to add an otherwise when rule to check if Channel is equal to Retail, using IgnoreCase function and \nset the Channel to \u2018Retail\u2019\nKeep the existing otherwise condition so it sets to InboundCC in all other casesUpdated data transform : ConvertCommonChannelToAOMChannel", "source": "VODKB-200723-160306.pdf"}
{"id": "38f3bed8d32a-0", "text": "2611\nD_EligibleHandsetsForTariff(ConnectSQL :GetHandsetsForTariff)\nD_InsurancesForHandset(ConnectSQL :GetInsurancesForHandset)\nD_SellableAccessoriesByIdentifier(ConnectSQL :GetSellableAccessoriesByIdentifier)\nChanges were also made to the validation data transforms in each of the activity for the data pages : \nRetail channel was added as a mandatory parameter check.\nD_SellablePaymHandsetBySKU(GetSellablePaymHandsetBySKUValidation)\nD_SellablePaymHandsets (GetSellablePaymHandsetsValidation)\nD_SellableBars (GetSellableBarsValidation)\nD_SellableAccessories (GetSellableAccessoriesValidation)\nD_DiscountsForTariff (GetDiscountsForTariffValidation)\nD_EligibleTariffs (GetTariffsForDeptValidation)\nD_ServicesForTariff (GetServicesForTariffValidation)\nD_EligibleTariffsForHandset (GetTariffsForHandsetValidation)\nD_EligibleHandsetsForTariff (GetHandsetsForTariffValidation)\nD_InsurancesForHandset (GetInsuranceServicesForHandset)\nD_SellableAccessoriesByIdentifier (GetSellableAccessoriesByIdentifier)This activity calls the GPSL data page (D_ProcessedServiceList) and retrieves the tariffIds for root products of PAYM and HBB, invoke the \nactivity GetCombiOffersForTariff to get the offers for given tariffid, department, channel\nApplies To Code-Pega-List\nRuleset AOMFW-Database\n Addition Info: Add new condition in the activity.\nIf the Channel =Retail, then convert to Upper Case ( RETAIL)\nDatabase contain Retail channel name as Upper CaseGetCombiOffersForTariff activity", "source": "VODKB-200723-160306.pdf"}
{"id": "39fc4a2d4525-0", "text": "2612\n938334 - Retail: Edit Device screen- New UI to Display both In Store Stock\ncheck and Warehouse for Retail Agent\nAcceptance Criteria: \n1. On the device tab, display the stock level as a column as per AS IS for PAYM - done\n2. 2 new labels called 'Store' and 'Warehouse' are displayed in a list below the stock column (See artefact - done \n3. For both 'Store' and 'Warehouse' stock, display the text response if 'in stock', 'Pre order' or 'Back order', followed by a column with the \nstock quantity for the top 5 devices (see artefact for examples) In future sprint 'Store' is displayed first in the row, followed by the stock \nicon for in stock, pre order or back order in second line of the same row as text (See design). - Done\n4. Below the icon for Store' response of 'In stock' 'Pre order' or 'Back order' display the label 'Warehouse' in the third line on the same row. \nThis is followed by the icon for stock check response on the 4th line in the same row as 'In stock', 'Pre order', or 'Back order'(See \ndesign).- Done\n5. The label for 'Store' and 'Warehouse' must fit the line as shown in the artefact i.e. The labels 'Store' or 'Warehouse' cannot go into the \nnext line and differ from what is shown in the UI - No required\n6. The label for 'Pre order' or 'Back order' must fit the line as shown in the UI below and cannot be wrapped into another line\n7. The colour for the 'Pre order'- (red) or 'Back order'- (black) must be used as shown in the artefact below - Done", "source": "VODKB-200723-160306.pdf"}
{"id": "39fc4a2d4525-1", "text": "8. For Store stock - a positive stock tick should be shown if there is at least 1 device in stock - not required\n9. Store stock are shown to Agent in real time - Not required\n10. We will not display out of stock in the top 5 recommendation for both In store or warehouse (ADO-938564,966558)\n11. For both 'Store' and 'Warehouse' stock after the top 5, if Agent clicks on the 'CHECK' button for stock, then display the text response of \n'In stock', 'Out of stock', 'Pre order' or 'Back order' followed by a column and the stock quantity as per UI the rules of a positive stock \ntick should not be changed \n12. Display ordering and other edit device tab functionality is not affected by this story\n13. Display the scroll bar as per AS IS\n14. For all other devices displayed after the top 5, then a 'Check' box is presented to the Retail Agent to click for stock availability for both In \nstore or warehouse (see detail functionalities in ID-353431)\n15. If Retail Agent uses the refine by to filter the list of device, if the return device is in the top 5 recommended devices, then display stock \navailability, else Retail Agent will need to click the Check box to check the stock availability for both In 'Store' or 'Warehouse'\n16. Stock check validation remains as per AS IS for PAYM for warehouse stock in basket summary i.e. if stock is not checked first before \nproceeding to basket summary then stock check is performed in the basket summary\n17. The stock level is sourced from GSA (AOM-2728)\nThe Stock in Store and Warehouse is displayed for all journeys supported in Retail: Mobile, Watch, MBB. The TSAR journeys are not \nimpacted by this change", "source": "VODKB-200723-160306.pdf"}
{"id": "39fc4a2d4525-2", "text": "impacted by this change\nStart (invisionapp.com)\nUpdate sectios : \nRefineDeviceResults, RefineDeviceResultsForMBB, RefineDeviceResultsForWatch", "source": "VODKB-200723-160306.pdf"}
{"id": "521c68aea7a1-0", "text": "2613\nUpdate Stock Level to use a section - this will have the new section embedded : StockLevelCheck\nNew class : VFUK-VADR-UI-Stock\nLocation Text \nQuantity Integer \nQuantityStatus Text \nTempStockStatus Text Property Name Type Notes\nThis section are for device table for handset, MBB & Watch for Retail agent and is embedded in the Stock Level column \nApplies To VFUK-VADR-UI-Device\nRuleset VADR-UI\n Addition Info: GPL will be automatically coming with most recommended device list\nUse repeating dynamic layout to loop through the stock lineitem - has an embedded section \nStockLevelForRetail to display the stock information\nProperty value will be coming from GSA API - QuantityStatus for stock status and StockQuantity for amount\nUse BigDataRecommended property = true to display the stock on launch\nOtherwise when BigDataRecommended property = false, display check button first\nThe check button calls CallStockCheck activity to get stock results from GSA and populate the stock \npageNew Section : StockLevelCheck\nThis section are for device table for handset, MBB & Watch for Retail agent and is embedded in the StockLevelCheck section\nApplies To VFUK-VADR-UI-Stock\nRuleset VADR-UI\n Addition Info: Contains information such as the location, quantity and the quantity status\nHave a dynamic layout for each QuantityStatus so the colour of the word is different when the status is \u201cPre \norder\u201d, \u201cBack order\u201d etc..New Section : StockLevelForRetail\nUpdate DT : SetDevices", "source": "VODKB-200723-160306.pdf"}
{"id": "d9e96115494c-0", "text": "2614\nThis Data transform is called when the edit pencil icon is clicked to populate the DevicesForUI.Stock page\nApplies To VFUK-VADR-Work-Upgrade\nRuleset VADR-UI\n Addition Info: Copy each stock page coming from HandsetProductList when GPL is triggered into TempDevice.Stock page\nManually set location to \u2018Warehouse\u2019 and \u2018Store\u2019 when channel is retail otherwise location is vfwarehouse\nLoop through TempDevice.Stock page to set the quantity status as per invision using the SetStockDetails \ndecision table\nAppend the TempDevice page to DevicesForUI page\nSort the order so store stock details are on top and warehouse below\nThis activity calls GSA to get stock information to populate the device with stock level when the \u201cCheck\u201d button is clicked\nApplies To VFUK-VADR-UI-Device\nRuleset VADR-UI\n Addition Info: Loop through each stock page in DevicesForUI to set the quantity status as per invision using the \nSetStockDetails decision table\nManually set location to \u2018Warehouse\u2019 and \u2018Store\u2019 when channel is retail otherwise location is vfwarehouse\nSort the order so store stock details are on top and warehouse belowUpdate Activity: CallStockCheck\nThis table sets the QuantityStatus as per invision depending on what is returned by the GSA response\nApplies To VFUK-VADR-UI\nRuleset VADR-UI\n Addition Info: Depending on the stock quantity and stock status returned by GSA response, set the quantity statusNew Decision Table: SetStockDetails", "source": "VODKB-200723-160306.pdf"}
{"id": "86b11ce8a940-0", "text": "2615\nRetail - Test Only Stories\n1079519 - Retail: Existing Product holding and Contract details\nA Retail Agent launches VADR with a Mobile or MBB or Watch Subscription\nThe Recommendations screen loads as per 'As Is'\nThe 'Existing Products'' are displayed on the left hand side with the customer's current product holding (see Feature 488339 for further info) \nas per design for TSAR for all product types (Mobile, MBB, Watch, SIMO) (if the customer is on 5G ultra device, then the 5G ultra logo is \ndisplayed)\nThe customer name is displayed on the Top left hand side of the screen as per 'As Is'\nThe CTN in context, the 'Airtime end date' and the 'Upgrade fee today' (if relevant) are displayed alongside the 'i' icon. The 'i' icon hover \nlogic is as per 'As Is' (See ADO 336834 and ADO 478008)\nRecommendation -Retail (invisionapp.com)\n \n1079526 - Retail: Customer Profile information\nA Retail Agent launches VADR with a Mobile or MBB or Watch Subscription\nThe Recommendations screen loads as per 'As Is'\nThe customer name is displayed on the Top left hand-side of the screen as per 'As Is'\nThe Agent clicks on the customer's name\nThe 'Customer Profile' panel loads as per 'As Is'\nThe Customer's Address is displayed as per 'As Is'\nIn the 'Background information' section, the Customer's confidence indicator (Karma), STAC/PAC (if relevant), Regulatory offers \n(Blackstone) (if relevant) are displayed as per 'As Is'\nThe 'Account open lines section' is displays as per 'As Is'\nInvisions: \nMaster Customer Panel 01 (invisionapp.com)", "source": "VODKB-200723-160306.pdf"}
{"id": "3fff73cda4f5-0", "text": "2616\n1079535 - Retail: Customer has opted out of personalised offer\nA Retail/TSAR Agent launches VADR for a customer that has opted out of data profiling\nThe 'As Is' warning Message is displayed to let the Agent know that the customer has opted out of profiling\nMobile Journeys\nThe Recommendations are not displayed as per 'As Is'\nIf the Agent use refine by the recommendations using the Big Data Models are displayed as per 'As Is'\nIn the Device and Tariff Edit Screen, the Top 5 Devices or Tariffs as sourced from the Big Data Model are not displayed at the top the \nproducts list 'as per 'As Is'\nWatch Journeys:\nThe Recommendations are not displayed as per 'As Is'\nIf the Agent use refine by the recommendations are displayed as per 'As Is'\nNo top propensity product in the Edit Screens as per 'As Is'\nMBB Journeys\nThe Recommendations are displayed as per 'As Is' using AOM ADM\nIf the Agent use refine by the recommendations are displayed as per 'As Is'\nTop propensity products are displayed using AOM ADM as per 'As Is' \nPlease ensure that warning message is also displayed for MBB Journeys in TSAR\n \n1081157 - Retail: Usage Panel\nA Retail Agent launches VADR with a Mobile or MBB or Watch Subscription\nThe Recommendations screen loads as per 'As Is'\nThe Agent navigates to the Usage Panel\nThe Usage for the CTN in context is displayed as per 'As Is'\nRecommendation -Retail Copy 3 (invisionapp.com)\n \n1081162 - Retail: Billing\nA Retail Agent launches VADR with a Mobile or MBB or Watch Subscription\nThe Recommendations screen loads as per 'As Is'", "source": "VODKB-200723-160306.pdf"}
{"id": "2708b83bd692-0", "text": "2617\nThe Agent navigates to the Billing Panel\nThe Bills for the CTN in context is displayed as per 'As Is'\nStart (invisionapp.com) (please use invision but below is an extract for ease)\n \n1081169 - Retail: Refine by\nThe Recommendation screen loads as per 'As Is' and up to 3 recommendations are displayed using the relevant Logic or Commercial Rec \nlogic\nThe 'Refine by' criteria are displayed based on the CRE result and the journey type (Mobile, watch or MBB)\nAn Agent selects some 'Refine by' criteria and the select 'Refine' button\nThe logic recommendations are rerun as per 'As Is' based on the relevant journey type as per 'As Is'. If there is a Commercial \nRecommendation available, then the Commercial Rec replace the Logic Rec as per 'As Is'\nThe 'Clear' button is presented as per 'As Is'. If the Agent selects the 'Clear' button, then any Refine by criteria(s) previously selected are no \nlonger selected\nThe 'Refresh' button is presented as per 'As Is'. If the Agent selects the 'Refresh' button, then the original recommendations are displayed \nagain \nInvision link for PAYM - please refer to watch or MBB for specifics for these journeys\nRecommendation -Retail (invisionapp.com)\n \n1082039 - Retail: Edit Tabs\nA Retail Agent launches VADR with a Mobile, MBB or Watch CTN\nThe Recommendations screen loads as per 'As Is'\nThe Agent select the Edit screens either by selecting the 'Pencil' Icon or by selected the '+ Add new products to compare'\nThe Edit Screen loads and the Agent lands on the Device Tab as per 'As Is'", "source": "VODKB-200723-160306.pdf"}
{"id": "2708b83bd692-1", "text": "The Edit Screen loads and the Agent lands on the Device Tab as per 'As Is'\n'As Is' Tabs are available i.e. Device, Tariff, Discounts, Add ons, Insurance, Accessories, Bars\nThe Agent is able to navigates between the Tabs as per 'As Is' and the relevant information messages are displayed if the Tab is not yet \nenable (for example, the device needs to be selected before seeing Insurance products etc..)\nDevice Tab\nThe Device Tab is populated with devices based on the journey type (Mobile, MBB, Watch) and eligible with the Agent's division (if the \ndevice is a 5G Ultra device then the 5G Ultra logo is displayed)\nFor Stock Display please see ADO - 938334 and ADO - 938564", "source": "VODKB-200723-160306.pdf"}
{"id": "22acd6b8b0a0-0", "text": "2618\nTariff Tab\nThe Tariff Tab is populated with Plans based on the journey type (Mobile, MBB, Watch), eligible with the Agent's division , eligible according \nthe CRE and S15 Very Early Rules\nDiscounts Tab\nThe Discount Tab is populated with discount based on the journey type (Mobile, MBB, Watch), the customer discount eligibility, the Agent's \ntool kit, Fix or Flex Rules (if relevant) and eligible for the Agent's division\n \nAdd ons Tab\nThe Add On Tab is populated with add on that are compatible with the Plan in the basket and eligible with the Agent's division\nInsurance Tab\nThe Insurance Tab is populated with Insurance compatible with the Device in the basket and compatible with the Agent's division \nAccessory Tab\nThe Accessories Tab is populated with Devices that are compatible the Agent's division\nStock is not displayed in accessory tab\nBars Tab\nThe Bars displayed in TSARs are also displayed in Retail based on the Journey (no Bars in Watch for example - display 'As Is' information \nmessage instead) K16\n \nThe Filter/Sort functionality works as per 'As Is'\nAll products maybe made sellable or non sellable for Retail in PM Tool as per 'As Is'+J16\nThe 'Selected Basket' is displayed as per 'As Is' and the validations rules detailed for TSAR are as per 'As Is' (i.e. delete Device, Swap \nTariff, Incompatible Tariff etc..)\nEdit - Retail Expanded Copy (invisionapp.com) \nPlease see link for screen details\n \n1082190 - Retail: System Errors\nThe error message as presented in feature 483685 are also displayed in Retail for example ( but please refer to the Systems error message \nfeature for full list)\nUser Authentication Error\nVADR time out\nCustomer Info when launching application fails", "source": "VODKB-200723-160306.pdf"}
{"id": "22acd6b8b0a0-1", "text": "feature for full list)\nUser Authentication Error\nVADR time out\nCustomer Info when launching application fails\nGet Recommendation fails when loading the application or when doing a 'Refine by'\nValidateDeal or/and ValidateOperation in Edit fails\nGetStockAvailability fails in Recommendations, Device Tab, Accessory Tab, Summary Screen or for a SKU not ranged in the warehouse \nerror", "source": "VODKB-200723-160306.pdf"}
{"id": "12dd49707807-0", "text": "2619\nGetProduct in Edit fails\nGetRecentEvent fails in the customer information panel\nGetUsage fails\nBilling table and/or the Billing PDF are unable to load\nCase failure error\n \n1082343 - Retail: being able to Deliver to another store\nA Retail Agent launches VADR with a CTN (Mobile, MBB, Watch)\nThe Recommendations screens loads as per 'As Is' and the Agent navigates to the Device Tab\nThe Agent performs (or do not perform) a stock check and selects a device that is out of stock in his/her store or/and in the warehouse\nThe Device is in stock in another store (the Agent knows this via Business process outside of VADR)\nThe Agent is able to continue with the deal and fulfil the deal in Halo by selecting an another delivery method\n \n1079491 - Retail: Selected Products\nA Retail Agent launches VADR for a Mobile, Watch or MBB CTN\nThe Recommendations screen loads as per 'As Is'\nThe 'Selected Products' are displayed as per 'As Is' using the relevant recommendations logic \nUp to 3 recommendations are presented as per 'As Is'\nThe information presented is a per 'As Is' in contact centre based on the CTN type (Mobile, MBB (Evo/Non Evo) or Watch), SIMO vs \nDevice, Logic vs Commercial Recommendation\nThe more info peach banner and the relevant Icon (VFT, Apple Lover, Enrichment Icon, Commercial Recommendation) are displayed as per \n'As Is'. If the Agent selected the 'More' the relevant info about why the deal was recommended, VFT info, Apple Lover Info etc.. are \ndisplayed as per 'As Is'\nIf the recommendation is an MBB Recommendation then the 'Type' Purple Banner is displayed as per 'As Is'", "source": "VODKB-200723-160306.pdf"}
{"id": "12dd49707807-1", "text": "If the recommendation is an MBB Recommendation then the 'Type' Purple Banner is displayed as per 'As Is'\nIf a device recommendation is presented then only products that are in stock in the store or in back or pre order in the warehouse are \npresented as detailed in ADO 938564\nIf a device recommendation is presented, then the Device speed's icon is also presented (4G, 5G, 5G ultra)\nIf there is an EUF, then the EUF is displayed as per 'As Is'\nIf the recommendation is a promo, the promo banner is displayed\nIf the recommendation is a renegotiation, then only the 'Saved' deal is presented as per 'As Is'\nIt is possible to 'Edit' the 'Selected Product' as per 'As Is'\nIt is possible to 'Select' the 'Selected Product' as per 'As Is'\nIf the 3 recommendations slots are not filled, the 'Add new products to compare' and the '+' sign are displayed as per 'As Is' and the Retail \nAgent is able to access the Edit tabs as per 'As Is'\nRecommendation -Retail (invisionapp.com) for PAYM\n]", "source": "VODKB-200723-160306.pdf"}
{"id": "47076daa3f59-0", "text": "2620", "source": "VODKB-200723-160306.pdf"}
{"id": "0e00c0336336-0", "text": "2621\nR4.05 Retail", "source": "VODKB-200723-160306.pdf"}
{"id": "a2bb81127cbc-0", "text": "2622\n1082218 - Retail: Total Net Revenue\nDescription:\nThe TNR display has been detailed in 938125. However, the calculation for Retail TNR is not the same as per TSAR. This US contains the \ncalculation for Retail TNR. TSAR's remain as per As Is\n \nAcceptance Criteria:\nThe Total Net Revenue for Retail is calculated as per attached artefact\nIt must be possible to change the TNR via an optimisation release as per 'As Is'\nIt must be possible to have different TNR for Retail and contact centre\nThe Net Revenue is available in AOM reporting as per 'As Is'\nThe TNR is presented as detailed in 938125 and is recalculated by the application if the Agent changes items of the deal (example, swap a \nplan, add a add on etc..)\n \nTask ADO - 1235267\nRecommendations Screen", "source": "VODKB-200723-160306.pdf"}
{"id": "1220b5a5a946-0", "text": "2623\n \nEdit Device Screen", "source": "VODKB-200723-160306.pdf"}
{"id": "676fd01ec38d-0", "text": "2624\n \nBasket Summary Screen", "source": "VODKB-200723-160306.pdf"}
{"id": "1a4d5cf1ff37-0", "text": "2625", "source": "VODKB-200723-160306.pdf"}
{"id": "e043cfa13a6d-0", "text": "2626\n938125 - Retail- TNR figure to display on click\nDescription - \nWe would like to update the design for retail agents in order to hide the TNR Value on screen. The required change is to not show the \namount of TNR by default (label should remain). The TNR figure should be displayed when the user clicks on the new TNR slider on \nscreen. This should be applied to all areas where TNR is shown in the Retail Journeys inc selected products, basket, checkout. \nAcceptance Criteria - \nA Retail Agent launches AOM with a CTN where the TNR is presented\nThe Total Net Revenue label is displayed as per 'AS IS' without the amount in \u00a3xx.xx shown for all cards but instead a slider is \ndisplayed. When 1st loading the Recommendation screen the Sliders default to not showing the TNR\nThe Agent clicks using the switch option on the TNR label to reveal the TNR amount in \u00a3xx.xx (See artefact) on card by card basis (for \nexample, the Agent slide the TNR in the1st card, the Card 2 and 3 TNRs are still hidden)\nThe slider is available in all areas where TNR is shown including Selected products, Selected basket and Basket summary for Retail \nAgents only (i.e, the change does not apply to TSAR agents where the TNR continues to be displayed without a slider as per 'As Is')\nThe TNR slider setting is remembered on card basis and displayed in all areas using the same setting. For example, an Agent slides the \nTNR slider in Card 1. The Agent navigates to the Edit Screen. The TNR value is visible in the 'Selected Basket'. The Agent hides the", "source": "VODKB-200723-160306.pdf"}
{"id": "e043cfa13a6d-1", "text": "TNR in the 'Selected Basket'. The Agent clicks 'selects and continue' and returns to the 'Selected Products'. The TNR value is not \ndisplayed. The Agent clicks 'Select' and lands on the 'Basket Summary', the TNR value is not displayed. The Agent slides the TNR \nbutton to reveal the TNR and selects insurance button. The TNR value is displayed in the 'Selected Basket'\nThe only action within the Edit screen that will change the TNR Display is the change the setting on the slider\nThe TNR Calculation is detailed in a separate US \nTask ADO - 1235267\nUs the new Boolean property to enable or disable the TNR slider at the recommendation level ( VFUK-VADR-UI-Deal)\nBy default the property is set to false when data is copied over from the service to the UI layer\nEnabling the side will display the TNR Value\nInvision link updated in the ADO - AOM 4.02 \nRules to Update : \nBoolean property name under VFUK-VADR-UI-Deal class - DisplayTNRValue \nAdd this new property in PopulateDealFromServiceData DT - Setting by default as false\nToggle button: \nCreated new toggle-checkbox class\nThis section to display recommendations\nApplies To VFUK-VADR-UI-Deal\nRuleset VADR-UI\n Update the TNR dynamic layout to include the toggle image \nSet visibility condition for TotalNetRevenue property based on new boolean propertyUpdate sections : RecommendationDealFooterForRetail, EditDealSelectedDealFooterForRetail, EditBasketDeal", "source": "VODKB-200723-160306.pdf"}
{"id": "e7fa5d534b15-0", "text": "2627", "source": "VODKB-200723-160306.pdf"}
{"id": "2fa6dc06e211-0", "text": "2628\n1082301 - Retail: Remove Accessory Stock Display\nStart (invisionapp.com)\nTask ADO - 1235273\nCreate new section - RefineAccessoryResultsForRetail\nNeed to hide the Stock Level button for Retail\nInvision link updated in the ADO AOM 4.02 \nFor conditions on visibility etc. use function String.EqualsIgnoreCase - since it is not clear how the word Retail will be presented to \nus.\nDifference between TSAR and Retail\nThis is mainly dependent on the Channel\nIn the Mashup DT, there is Channel parameter - for a TSAR agent launch screen, Channel will be InboundCC and for Retail agent Launch \nscreen, Channel will be Retail\nThis section is to display accessories tab for retail channel\nApplies To VFUK-VADR-UI-Deal\nRuleset VADR-UI\n This section is specific to Retail agent in which Stock Level column will be removedSection - RefineAccessoryResultsForRetail", "source": "VODKB-200723-160306.pdf"}
{"id": "4a3ab42566a3-0", "text": "2629\n1082338 - Retail: Remove the automatic Stock Check in the Basket Summary\nTask ADO - 1235967\nSkip the stock check if Channel = Retail\nProcessBaketDeal Activity skip all the stock checks if Channel = Retail ( add new when rule)\nChannel is available on the pyWorkPage.Channel (VFUK-VADR-Work-Upgrade)\nThis data transform sets stock status\nApplies To VFUK-VADR-Work-Upgrade\nRuleset VADR-UI\n Add when rule to skip Stock Check if the channel is RetailActivity - ProcessBaketDeal", "source": "VODKB-200723-160306.pdf"}
{"id": "33f31b4c9481-0", "text": "2630\n1082343 - Retail: being able to deliver to another store\nDescription:\nWe need to ensure that if a device is Out of Stock in one shop but In stock in another, AOM allows for the deal to be placed so that the \nagent can change the delivery address to the other store in Halo\n \nAcceptance Criteria:\nA Retail Agent launches VADR with a CTN (Mobile, MBB, Watch)\nThe Recommendations screens loads as per 'As Is' and the Agent navigates to the Device Tab\nThe Agent performs (or do not perform) a stock check and selects a device that is out of stock in his/her store or/and in the warehouse\nThe Device is in stock in another store (the Agent knows this via Business process outside of VADR)\nThe Agent is able to continue with the deal and fulfil the deal in Halo by selecting an another delivery method\nTask ADO - 1309136", "source": "VODKB-200723-160306.pdf"}
{"id": "d5cd9631eb1b-0", "text": "2631\nR4.05 Task", "source": "VODKB-200723-160306.pdf"}
{"id": "d3dbc65dd6a9-0", "text": "2632\n1242780 - TSAR - Update the stock display in TSAR to be inline with\naccessories Tab Look and Feel\nDescription:\nDuring Pilot, we got feedback that the hover to see the stock level was hard to use. As a result, we would like to display the stock level \nwithout an hover similar than in Retail\n \nAcceptance criteria:\nA TSAR Agent launches VADR for Mobile, MBB or watch CTN\n \nThe Recommendation screen loads as per 'As Is'\n \nThe Agent navigates to the Edit Tab and lands on the Device Tab as per 'As Is' and navigates to the 'Accessory Tab'\n \nThe 'Check button' is presented near the stock items as per 'As Is'\nThe Agent select 'Check' for one of the Accessory Product\nVADR calls GetStockAvailability\n \nThe stock display is updated as per below:\n \nIf the Accessory Product is in stock then display the quantity followed by 'in stock' (for example '10 in stock') in green\nIf the Accessory Product is on pre order, then display 'Pre order' in red (Pre order stock level are not displayed)\nIf the Accessory Product is in backorder, then display 'Back order' in black (back order stock level are not displayed)\nIf the stock level is unknown, then display 'unknown' in red (i.e. if GSA is down)\n-If the device is not in stock, then display 'Not in stock' in red\n \nSee invision link in the chat and a screen shot below:\n \nFrom : Start\" and \": End\u201d format\nApplies To VFUK-VADR-Int-GPL-API\nVFUK-VADR-Int-GC-API\nVFUK-VADR-Int-GCU-API\nRuleset VADR-IntGetProductList, GetCustomer, GetCustomerUsage Activities\nAdd new step APIErr after Fin step to jump from StepStatusFail on Connect-Rest step\nOn the property setup on APIErr step, jump to QEL\nLocal.ErrorCode = Set new error code and pass it to ErrorCode parameter in QEL step\nCheck if pyHTTPResponseCode is empty and then set to 504 and pass it to StatusCode parameter in QAL step\nLocal.ErrorMessage = getWorstMessage() and pass it to StatusMessage in QAL, ErrorMessage in QEL step\nUpdate ErrorCode local variable type as Int and remove \u201c \u201c from ErrorCode settings\nCorrect Message in Start and End steps\nUse \": Start\" and \": End\u201d format\nAdd Err handling to apply the DT", "source": "VODKB-200723-160306.pdf"}
{"id": "76dec8fd2594-1", "text": "Use \": Start\" and \": End\u201d format\nAdd Err handling to apply the DT\nApplies To VFUK-VADR-Int-VB-API\nVFUK-VADR-Int-VD-APIValidateBasket, ValidateDelete Activities", "source": "VODKB-200723-160306.pdf"}
{"id": "a64693ff1033-0", "text": "2659\nRuleset VADR-Int\nAdd new step APIErr after Fin step to jump from StepStatusFail on Connect-Rest step\nOn the property setup on APIErr step, jump to QEL\nLocal.ErrorCode = Set new error code and pass it to ErrorCode parameter in QEL step\nCheck if pyHTTPResponseCode is empty and then set to 504 and pass it to StatusCode parameter in QAL step\nLocal.ErrorMessage = getWorstMessage() and pass it to StatusMessage in QAL, ErrorMessage in QEL step\nUpdate ErrorCode local variable type as Int and remove \u201c \u201c from ErrorCode settings\nApplies To VFUK-VADR-Int-SB-API\nRuleset VADR-IntSubmitBasket Activity\nAdd new step APIErr after Fin step to jump from StepStatusFail on Connect-Rest step\nOn the property setup on APIErr step, jump to QEL\nLocal.ErrorCode = Set new error code and pass it to ErrorCode parameter in QEL step\nCheck if pyHTTPResponseCode is empty and then set to 504 and pass it to StatusCode parameter in QAL step\nLocal.ErrorMessage = getWorstMessage() and pass it to StatusMessage in QAL, ErrorMessage in QEL step\nUpdate ErrorCode local variable type as Int and remove \u201c \u201c from ErrorCode settings\nCorrect Message in Start and End steps\nUse \": Start\" and \": End\u201d format\nAdd descriptions to local variables\nApplies To VFUK-VADR-Int-GR-API\nRuleset VADR-IntGetRecommendations Activity\nAdd new step APIErr after Fin step to jump from StepStatusFail on Connect-Rest step\nOn the property setup on APIErr step, jump to QEL\nLocal.ErrorCode = Set new error code and pass it to ErrorCode parameter in QEL step\nCheck if pyHTTPResponseCode is empty and then set to 504 and pass it to StatusCode parameter in QAL step", "source": "VODKB-200723-160306.pdf"}
{"id": "a64693ff1033-1", "text": "Local.ErrorMessage = getWorstMessage() and pass it to StatusMessage in QAL, ErrorMessage in QEL step\nUpdate ErrorCode local variable type as Int and remove \u201c \u201c from ErrorCode settings\nAdd Err handling to apply the DT\nApplies To VFUK-VADR-Int-GNM-API\nRuleset VADR-IntGetNotificationMessages Activity\nAdd new step APIErr after Fin step to jump from StepStatusFail on Connect-Rest step\nOn the property setup on APIErr step, jump to QELGetInvoiceList Activity", "source": "VODKB-200723-160306.pdf"}
{"id": "129a686f8fd4-0", "text": "2660\nLocal.ErrorCode = Set new error code and pass it to ErrorCode parameter in QEL step\nCheck if pyHTTPResponseCode is empty and then set to 504 and pass it to StatusCode parameter in QAL step\nLocal.ErrorMessage = getWorstMessage() and pass it to StatusMessage in QAL, ErrorMessage in QEL step\nAdd ErrorCode local variable type as Int and populate it\nAdd descriptions to local variables\nCorrect Err step\nUpdate ErrorMessage to include activity name\nAdd Err handling to apply the DT on step 2\nRemove \u201cAPI\u201d from ProcessName parameter in QEL step\nApplies To VFUK-VADR-Int-GIL-API\nRuleset VADR-Int\nAdd new step APIErr after Fin step to jump from StepStatusFail on Connect-SOAP step \n \nOn the property setup on APIErr step, jump to QEL\nLocal.ErrorCode = Set new error code and pass it to ErrorCode parameter in QEL step\nCheck if pyHTTPResponseCode is empty and then set to 504 and pass it to StatusCode parameter in QAL step\nLocal.ErrorMessage = getWorstMessage() and pass it to StatusMessage in QAL, ErrorMessage in QEL step\nUpdate ErrorCode local variable type as Int and remove \u201c \u201c from ErrorCode settings\nStatusCode=Primary.response.body.ResultStatus.Code in QAL step \n \nApplies To VFUK-VADR-Int-GSA-API\nRuleset VADR-IntGetStockAvailability Activity", "source": "VODKB-200723-160306.pdf"}
{"id": "514cf9b5dfdf-0", "text": "2661\nPega Certification Readiness\nSystem Architect\nQuestion Dump v8.6\nSenior System Architect\nLinks\nQuestion Dump v8.6\nSystem Architect\nGeneral Pega exam advice: Preparing for a Pega certification exam | Pega Academy \nCheck out the exam specification for the areas to focus your study on. The main module for CSA is Case Management: Certified Peg\na System Architect | Pega Academy \nHere is a Youtube playlist that contains 120 question previously asked in the exam. Different kind of questions may appear than you \npreviously has been seen since the version of the exam these questions was retrivied from was 8.5. Additionally, take the answers with \na grain of salt: https://www.youtube.com/playlist?list=PLu9b0Z2CDRy5sztwdKMKlFPJ7xPuwvHh4 \nThere's no practical element to the exams, so it's all down to getting a good understanding on the theory in each module.\nThe pages that give step by step information on how to do something are useful for \"challenges\" but will not be graded.\nQuestions can sometimes ask about when to use specific features so look out for contextual examples for when to use things like data \npages or report definitions etc.\nIt's good to go through the module questions and mission tests a few times and get used to the sort of questions that are asked. In the \nexams, it's mostly multiple-choice questions - but some of them give you 4 options for the answer which are all very similar (almost like \nthey're trying to trick you!). Read them carefully!\n \nQuestion Dump v8.6\nUse the below questions and answers as a reference for question style and content. All answers are speculative, please research the \ncorrect answer.", "source": "VODKB-200723-160306.pdf"}
{"id": "514cf9b5dfdf-1", "text": "correct answer.\n1. When does the case status gets updated? Case status | Pega Academy \nOnce the stage is completed.\nOnce the stage has been started.\n2. ABCInc-Consumer-PolicyProcessing-Work-Quote class has direct inheritence to Work- class and pattern inheritence. Order the classes \nbelow for the inheritence search. Rule reuse through inheritance | Pega Academy \nABCInc-Consumer-PolicyProcessing-Work\nABCInc-Consumer-PolicyProcessing\nABCInc-Consumer\nABCInc\n@baseclass\nWork-\n3. When designing an app for users, which of the options below does the developer primarely think about?(Choose two)\nIf the fields needs external resource storage\nHow the fields are going to be entered by the user\nIf the fields are going to be entered by the user\n4. Which two steps are necessery to add an automated unit test? (Choose two) Unit tests | Pega Academy \nDefine an assertion with the expected result", "source": "VODKB-200723-160306.pdf"}
{"id": "4f8dbd9ead2f-0", "text": "2662\nSave the configuration of the test case\n5. How can saved scenario tests be accessed? Scenario testing | Pega Academy \nFrom Application: Scenario testing landing page\n6. What is the easiest test type to maintain over long run? Scenario testing | Pega Academy \nScenario Testing\nFunctional Testing\nUnit Testing\n7. How to setup a validation configuration with two different conditions?Data validation in Dev Studio | Pega Academy \nOne validate rule with two conditions\nTwo validate rules with each has one condition\nOne edit validate rule with two conditions\nTwo edit validate rules with each has one condition\n8. What can be possible reasons to configure two different mobile app channels?Mobile app channels | Pega Academy \nThe need for two different color schema\nThe need for tablet and mobile phone interfaces\nThe need for two different application icon\n9. When it is appropriate to simulate external data sources? Simulated external data sources | Pega Academy \nWhen the source system is not ready and still in development\nWhen there is an ongoing maintenance on the system\n10. Which two of the passwords below are considered sufficiently secure?(Choose two) Passwords and system access | Pega Academy \ngfhk3293^=/,-(/),jhkh\u201d\u00e9dfv,\nP3g@syst3m$\nice cream\nIamFromPizzaWithCar\n11. Match the keywords with definitions below. Keywords: CAPTCHA, Lockout, Multi-factor authentication. Security policies | Pega Acad\nemy \nFeature that sends a one-time password to users by either email or SMS text message\nChallenge-response test(typically an image) to determine whether users are human\nFeature that enforces a waiting period to slow down or prevent a brute-force attack\n12. where should you configure passed deadline \ndev studio\napp studio\n13. what tags can you add in the case (MLP)\nmobile app", "source": "VODKB-200723-160306.pdf"}
{"id": "4f8dbd9ead2f-1", "text": "app studio\n13. what tags can you add in the case (MLP)\nmobile app \nexternal source \nreject \n14. when adding a 75$ annual fee to a view how should you create the field \nconfiguring it as a calculated field \n15. a new member has joined the team of managers and administrators as an auditor and requires certain permissions from each role (all of \nthe managers and some administrators)\nchange the Administrators roles to all these actions \ncreate a new role and manage the access for the auditor \n16. if a case has an urgency of 10 then it increases by 10 the goal increases again by 10 at the deadline increeases again passed deadline \nwhat is the final urgency.", "source": "VODKB-200723-160306.pdf"}
{"id": "07acb1eadd77-0", "text": "2663\n \nSenior System Architect\nLinks\nUse the below links with caution, some questions are from other certifications and some answers are incorrect, but useful to research.\nPega Certified Senior System Architect (PCSSA) PEGAPCSSA80V1_2019 Updated Dumps Questions \nPegesystems PCSSA Certified PEGAPCSSA85V1 Real Exam Dumps (Similar questions/better formatting)\n \nQuestion Dump v8.6\nUse the below questions and answers as a reference for question style and content. All answers are speculative, please research the \ncorrect answer.\n1. What does a greyed out relevant record mean?\nThe rule is already marked as relevant record\n2. Rule types for relevant record? Relevant records | Pega Academy \nProperties\nSections\nHarnesses\nParagraphs\nCorrespondences\nService Level Agreements\nFlows\nFlow actions\n3. Three options to consider for post processing\nflow action likelihood, \nreuse \nsequence in which the system runs different actions\nDo you need to consider re-entering in flow-action for post-processing? (Don\u2019t think I had an option for reuse. Likelihood, sequence \nand one more choice)\n4. Action that declare OnChange rule can do?\nSuspend work object\n5. How to create a Mobile app that can work offline? Mobile app deployment | Pega Academy \nNative app\n6. What functions can a native app use? Mobile app deployment | Pega Academy \nOffline case processing\nPush notifications\nBarcode scanning\nBiometric identification\n7. Two things you need to build mobile app? Mobile app deployment | Pega Academy \n Certification set \nAccess to Pega Mobile Build Server\n8. What does Pega Mobile Build Server require to work? Mobile app deployment | Pega Academy \nSecure HTTPS access", "source": "VODKB-200723-160306.pdf"}
{"id": "94e7f7369c61-0", "text": "2664\nThe URL with the Pega Mobile Client License\n9. Application taking 10 seconds to finish - the tool for analyse?\nPerformance profiler/PAL\n10. Most common ways to expose app to external services? Exposing an application as a service | Pega Academy \nPega API \nSOAP Service\n11. Field value primary use? Field values | Pega Academy \nField values enable you to manage the list of allowed values separately from the property. Managing the allowed values \nseparately from the property enables you to reuse a single property, and customize the allowed values based on the context of the \nproperty.\nUse in a specific case type\n12. How to Associate Open-Review status with a case type?\nCreate Field value\nAssociate with case type\n13. Retry after an hour - something about SOAP?\n logic to error handler flow\n14. What is a Production ruleset used for? Application and production rulesets | Pega Academy \nProduction rulesets include rules that are updated in the production environment. The most common use of production rulesets is for \ndelegated rules. However, production rulesets can be used for any use case requiring rules to be updated in a production \nenvironment.\n15. What is rule delegation?\nRules are made available for users to edit in the production environment \n16. Pega, Alert and AlertSecurity drag and drop. Log files | Pega Academy \nPEGA \u2013 warnings, errors, and information messages about internal operations\nALERT \u2013 performance-related alerts or an operation exceeds the specified performance threshold\nALERTSECURITY \u2013 someone trying to tamper with the URL\n17. Static assembler: Preassembling rules in an application by using the Static Assembler utility \nThe Static Assembler utility enables the preassembly and caching of rules that belong to an application. These actions improve the", "source": "VODKB-200723-160306.pdf"}
{"id": "94e7f7369c61-1", "text": "response time for interactive users after a system startup or when new ruleset versions are imported into the system\n18. Ordering request processing: Connectors and services | Pega Academy \nConnector\nInitialise Connector\nMap outbound data\nInvoke Service\nMap inbound data\n Service \nInbound Request recieved\nMap inbound data\nRequest processing\nMap outbound data\nSystem returns a response\n19. Report definition: set up a class join Joins, associations, and subreports | Pega Academy \nCreate a class join with prefix\nDefine the type\n20. What is a class group\nRather than creating a new class, designate the parent class as a class group\nStore instances of similar or related case types together in a single DB table", "source": "VODKB-200723-160306.pdf"}
{"id": "150e32015e8f-0", "text": "2665\nA report created in the class group returns all instances in the classes that belong to the group\n21. Interactions between Mashups\nJavaScript .DoAction() \u2190 this doesn\u2019t seem to be covered in Pega Academy check: \nMashup JavaScript page actions \ndata-pega-event-onpagedata \u2190 Please see: \nData exchange through Pega Web Mashup | Pega Academy \n22. Which two statements are valid regarding Pega Web Mashups? (Choose two.)\na. A mashup display starts by calling either a flow or a harness from a Pega application. (Don\u2019t recognise this option)\nb. Pega Platform limits a mashup to working on existing cases.\nc. A mashup can allow access to Dev Studio for full system configuration.\nd. A user can view their worklist in an external portal and select items to take action on.\n23. (Similar to this Module Quiz question): Which two of the following steps are required to create a Pega Web Mashup?\nConfigure a list of approved sites for the site origin.\nGenerate the mashup code.\n24. Application Validation and Rule Validation indicated by [ ]\n25. Circumstancing and rule resolution Single-variable circumstancing | Pega Academy \na. Single variant rule where Country = x\nb. How to remove a circumstanced rule from a ruleset \nYou can select the Base check box to indicate that the rule resolution algorithm should ignore all previous occurrences of this rule \nin the same major but lower minor and patch versions at the time of rule resolution.\nWhen a circumstanced rule is withdrawn, all previous occurrences of this rule in the same major, but lower minor and patch \nversions having the same circumstance type get withdrawn. Rule resolution then selects the base rule despite meeting the \ncircumstanced condition.", "source": "VODKB-200723-160306.pdf"}
{"id": "150e32015e8f-1", "text": "circumstanced condition. \n26. Deny access control to an operator Role-based access control (RBAC) | Pega Academy \n27. Product rule and associated data instances\n28. Two operators need to get work from Units A and B Work groups | Pega Academy \nEven though operators and work queues belong to a unit, associating a work group with an operator allows the operator to share \nwork with operators in other units\n29. Why use branching? Parallel development | Pega Academy \nAllow multiple developers can implement functionality without impacting other developers\n30. Set up rule locking for a scenario involving parent and child cases. Case locking | Pega Academy \n31. Do organizations have unique encryption keys. Data encryption | Pega Academy \nEach organization uses a custom key to encrypt their data in Pega Platform. By using custom keys, different organizations can \nleverage the same cipher to generate a unique encryption result. \n32. The correct back ground processing for a company that must process orders multiple times a day\nMultiple job schedulers set to different times?\n33. The Sum of a cases' urgency based on the number of hours passed. Assignment urgency | Pega Academy \nIncluding:\nInitial urgency\nSLA delay\nGoal\nDeadline\nPassed Deadline\n34. ABC:02-02 being skimmed to new major version. Which are copied? Creating higher ruleset versions by skimming rules | Pega Acad\nemy \n01-01-01 (No)\n02-01-01 (Yes)", "source": "VODKB-200723-160306.pdf"}
{"id": "0e08f6c223b0-0", "text": "2666\n02-02-01 (Yes)\n02-01-05 (Yes)\n35. Requirement for User to not be able to open a case. (Access when or Access deny?)\n36. A patient needs to only view a case. How is this achieved?\na. Access Role to Object set to 1\nb. Access of Role to Object set to 5\nc. Something else (privilege?)\nd. Something else\n37. Doctors and nurses both need to edit patients\u2019 cases. How is this achieved?\na. Two roles for doctors and nurses with Access of Role to Object set to 5\nb. Two roles for doctors and nurses with Access of Role to Object set to 1\nc. One role for both doctors and nurses with Access of Role to Object set to 5\nd. One role for both doctors and nurses with Access of Role to Object set to 1\n38. Configure the time-out value of the child case to be less than the time-out value of the parent\n39. You want to assign the same workgroup to different units, how do you achieve this?\na. Workgroup assigned to users and a worklist assigned to the workgroup?\n40. Student application automatically approves students whose test score is above the national average. Which configuration supports this? \n(Pick Two)\na. Configuration stores national test average?\nb. Configuration calculates national test average? \nc. Check whether .NationalAverage < .StudentScore\nd. Check whether .NationalAverage > .StudentScore\n41. Which is true for guardrails? (Pick Two) Application performance issues | Pega Academy \na. When you save a rule, Pega Platform performs a guardrail examination\nb. When you checkout a rule, Pega Platform performs a guardrail examination", "source": "VODKB-200723-160306.pdf"}
{"id": "0e08f6c223b0-1", "text": "b. When you checkout a rule, Pega Platform performs a guardrail examination\nc. Something about application being ready after the guardrail compliance score is over 90 (This link only says that it\u2019s in good \nstanding after 90)Guardrails compliance score \nd. The guardrail compliance score measures the number of rules with unjustified warnings\n(Technically true?)\n42. Using Performance Analyser to measure performance (Pick Two) https://academy.pega.com/topic/performance-analyzer-\ntool/v2/in/24081/24651 \na. Run through the process once to completion first to ensure that all rules are assembled\nb. (One of the options, not sure if right): Run the process from the portal to see end user\u2019s performance\nc. \nd. \n43. Asks what is true for class mappings Data storage in Pega | Pega Academy \nPegaRULES \u2013 Maps to the database where all Pega Platform rules and system data are saved.\nPegaDATA \u2013 Maps to the database where data and work instances are saved.\n(^ One answer says only PegaRULES is for rules and PegaDATA is for work instances so I don\u2019t know if that's wrong)\n44. Call Activity returns to the originating activity, while Branch Activity skips the remainder of the originating activity.\n45. Static assembler is used for which of the following issues?\nRule cache is too big?", "source": "VODKB-200723-160306.pdf"}
{"id": "bc1d11269f81-0", "text": "2667\n46. The customer, a medium size toy maker, wants to fulfill orders received during the peak season in December and process them in \nbatches multiple times a day.\nHow do you implement this use case?\na. Create a queue processor that can process orders received by the company.\nb. Create one scheduled job and select its run schedule as multiple times a day.\nc. Create batches of orders and send each batch for processing when it gets full.\nd. Create scheduled jobs, one for each run, that can process accumulated orders.\n47. You are preparing to create a new major version of an application ruleset in which there are multiple minor and patch versions.\nHow do you create the new ruleset version?\na. Use the Ruleset Maintenance wizard to merge the existing rules in the relevant ruleset versions to the new version.\nb. Use the Ruleset Maintenance wizard to skim the relevant ruleset versions to copy the highest version of existing rules to the new \nruleset version.\nc. Create a new application ruleset using the appropriate version number, then copy the highest version of existing rules into the new \nruleset version.\nd. Use the Application Structure landing page to lock and roll the existing ruleset versions to the new version.", "source": "VODKB-200723-160306.pdf"}
{"id": "12a77246ae6a-0", "text": "2668\nApps Documentation\nDesign\nLoader Case Design\nTemp\nConfigure new spine entity to the spine loader\nLoader Process - Process Usage Charges\nEvent Loader Development\nMEF - Digital Enriched Data\nBatch NBA Case Design\nOldest one\nTreatment Buckets Design\nDataFlow Audit History\n1393706: Run AOM batch during business hours, single or multiple times\nExtractor Case Design\nExtractor Case Design _backup\nCreate RCS Channel Extract\nCreate MMS Channel Extract\nCreate RecommendationItems Extract\nBatch Controls - pause, hold, resume at treatment level\nRunning the Extractor Case\nHousekeeping Case\nHousekeeping for PurgeEOC (Purge Expired Outbound Comms)\nCommon Case Flows\nCheckpoint Check\nGenerate Extract Agent Activity Updates\nInclude recommitted in OBC purge file\nApply Volume Constraints Redesign\nScheduler Design\nThrottling Design\nHazelcast Bucket4j\nSubscription Case Design\nChannel Execution Approval & Switch Control Implementation\nProduct & Offer Catalog Design\nLoader Case Design For PC/OC\nProduct Catalogue Data Pages - OLD\nFlush Data Pages for Loader Case Sub Types\nProduct Catalogue Data Pages\nOffer Catalogue Design - Cassandra Design\nTruncate Cassandra Data Sets for Loader Case Sub Types\nModify the HBB Discount to include the VFT(Vodafone Together) discount\nVodafone reference architecture\nBDC Models\nRecommendation UniversalTariff BDC Model\nIngest Predictive IVR BDC ModelThis section will detail the AOM Design and related topics\n \nExpand all Collapse all", "source": "VODKB-200723-160306.pdf"}
{"id": "f8d448588d50-0", "text": "2669\nBDC to AOM Multipart Files Design\nDevice Recommendation BDC Model\nConvergence BDC Model\nStore All Outbound Communications Sent\nUnsubscribe Case Design\nExtract the new IH Report table to EDW\nStore IH Reporting fields in IH Reporting table\nCase Dependencies\nGetNBA Response Mapping For IVR\nApply Volume Constraints for Customers in Control Group\nExtend BundleEventAPI for Additional Parameters\nAOM RT Aggregated Event Store\nTrack Trigger Event Processes Into New Event Store Process\nTrack BundleEvent Processes into New Event Store Process\nExtend Trigger Event for Sales Order Events\nEvent Analysis Store\nExtend parallel spine loads to all spines\nRecommendations Portal\n651840 & 651806 - Enable Device & Watch Recommendations\nProvide the ability to define and manage an effective FUT Cohort within AOM for Treatments\nProvide Better Alignment of AOM Logging Processes (AOM-1797)\nSimulation Orchestration\nCase Details\nBase Line Simulation\nCustomer Simulation\nInbound Simulation\nTIL Simulation\nProcessSimulationDropOff Update\nPega 8.8 Upgrade - Simulation changes\nStop Simulation\nAOM RT Aggregated Event Store - Account Event\nData Load Threshold Assurance\nApp Changes for LIVE UAT Seed Test\nCSO Transform - Modify Order\nCSO Transform - Modify Order Transform - ADO Task/Design\nSave Offers Metadata\nOffers Case Management and Setup\nLanding Page\nLanding pages & Exception Message Handling\nPersonalized Video\nSeed Testing\nDecision Metadata for GR and GPL APIs\nSubmit Basket Request Body Additional Attributes\nTasker Case\n896436 - AggregateIH - New case subtype in Tasker case\n921213: How we identify Top selling MBB products\nHandle Business Logic Error In GetNBA API - 526157\nCalling Capture Response in Offers Setup Stage\nGet Product List V2 Enhancements\nProduct Cataogue Data Page & Catalogue Sync Changes\nStore Dataflow Response", "source": "VODKB-200723-160306.pdf"}
{"id": "f0c47ede74cc-0", "text": "2670\nAsync Capture Response\nBranching\nWorking with PRPC Branching\nHow to setup new Branch\nGuidelines for Merging Branches\nGuidelines for Testing using Branch Application\nBranching Approach\nChannel Management\nDesign Overview\nTreatment Send Config\nUser Interface\nEmail\nSMS\nApp Push\nSend SMS Message\nSimulation Portal\nCreate Simulation Screen\nBack out IH\nBack out IH Design\nBack out IH Data Model\nBack out User Interface\nBack out IH Rules & Activities\nBack out IH Case Changes\nBackout Data Design\nMaking a Delete IH request\nAssisted 2nd Line Acquisition\n933266: Refresh GetCustomer info every time VADR is launched\n991853: Recommendation Reasons\n991858: Include Digital in Commercial UI\nUpgrades - Get Customer performance improvement (1035177, 959910)\n1187062 - Newly added column mappings for device_v\nSOHO\nRedesign WBW lookup to use Data Type instead of Decision data (ADO 1163201)\n1190526 - Consume Strategic Roaming feed\nAutomated Order Submission (AOS)\nAOS - Overview\nAOS - Data Model and Config\nAOS - Portal/UI\nAOS - Activities and Rules\nConfigurations\nAOM Config\nBundleEventNTIDMap\nEventTypeConfig\nAOM Business Config\nMicrosite Configuration\nAOM Utilities\nFunctions\nTemplateConfig\nScheduler Config\nOld AOM Config\nSeed User NBA Whitelist", "source": "VODKB-200723-160306.pdf"}
{"id": "ad09a531c1f8-0", "text": "2671\nFlush Caches/Truncate Datasets\nAOM Access Groups\nClearing AOM Config Cache\nWBWDeviceMultiplierMatrix\nExternal System Integration Services\nTealium-AOM Integration\nCreate Sales Order Connector\nCheck Retention Eligibility Connector (CRE)\nGet Out of Bundle Charges Service - OOBCharges\nGet Stock Availability (GSA)\nGet Customer Party List (GCPL)\nGet Live Account Information Data Page (AOM-2734)\nCatalogue Sync\nGet Processed Service List (GPSL)\nIMI -Inbound Webhook Events\nPOC - JWT Authentication\nCheck Product Eligibility\nAOM Exposed Services\nGetRecommendedProductList (GRPL)\nGet Next Best Actions REST API\nGetNextBestActionsV2\nSet NBA Response REST API\nCustomer REST API\nCRE Call for Multiple Customers Simultaneously\n1347204 - Handling of Prepay subscriptions in GPSL within an Post pay upgrade\nGet Product List REST API\nGet Recommendations REST API\nSubmit Basket REST API\nCSO Mapping Design-- 428209\nValidate Basket REST API\nValidate Delete REST API\nGetProductList V2 REST API\nGet Customer Usage Rest API\nGet Notification Messages REST API\nRealTime Triage Tool\nWatchdog Design, Config And Reports\nAlert Management\nWatchDog to Provide better supporting Information with Alerts\nAlert Subscription Management\nWatchDog Unsubscribe\nWatchDog Case Design\nWatchDog Exception/Error Reports and Jobs Scheduled\nWatchDogConfig\nWatchDog Modifications\nReusable Report Definations\nEvent Handlers & Framework\nCustomer Permissions\nSales Order Events\nRetention Eligibility Events\nCustomer Interaction\nConnect Queue Parameters", "source": "VODKB-200723-160306.pdf"}
{"id": "66483c1d6153-0", "text": "2672\nEvent Framework - Invalid Parameter Mapping\nTrigger Event Framework\nCall Event\nSales Order\nProvisioning\nMicrosite\nDialler Outcomes\nWebhook\nDisconnections\nAppPushResponse\nLeaveRequest\nRoaming\nIMI - Outbound Events\nCall Event Handler\nSupport of Multiple Identifiers for CallEvent\nTroubleshooting The Processes\nAOM Audit Tables\nAOM Error Tables\nAuditMetadata\nAOM Error Codes\nAOM Errors & Troubleshooting\nFrequently Occurring Problems (FOP)\nEnvironment Check List\nTroubleshooting Guide\nDefect Triage for 2.09\nData Page Errors Debugging\nToolbox\nPAT Support\nVADR Versions\nTesting Functionality\nTest Action from offer flow\nSeed Test Functionality\nSMS & Email Seed Test Functionality HLD\nSeed Test Design\nGet NBA Seed Test\nAdding Seed Test to Channel Management\nAssisted Upgrades Test Harness\nEmail Seed Test POC\nAPI Simulation\nKnowledge Base\nCreating New Class Mapping for External Table\nFrequently Used / Useful Pega Functions\nHow to use Simulations in Service Connector Rules\nService REST Features PoC\nIs Case Runnable\nCommon Utilities\nDocumentation Template\nDynamic System Settings - Server Restart\nPega Unit Test Case Design & Limitations\nHow to Induct new resources into App Team\nAES 256-bit Encryption", "source": "VODKB-200723-160306.pdf"}
{"id": "ad5a5c5ce2dc-0", "text": "2673\nWorking with SSH\nMashup\nArticles\nExtend IH Table\nDatabase ER-Diagram\nTables - Description\nEntity Relationship Diagrams\nReference Material\nKT Sessions\nAOM Issue Triage Questionnaire\nPega Support Request Guide\nCoding Best Practices\nRule Types and Rulesets\nCreating Data Type\nVersioned and Un-Versioned Rules\nTriage activities\nSTF Flow\nPRPC Features\n8.5.3 - New Features\nCase Management\nLow-code Application Development\nSystem Administration\nEnhance your data sets with Apache HBase 2.1 and Hadoop 3.0 (8.5)\nAccess and curate your data by using enhanced data APIs (8.5)\nDecision Management\nCall authenticated APIs from any application (8.5)\nData Integration\nUser Guide\nHow to Run the Loader Case\nHow to run BDC loader and add new BDC model files\nOffers Landing Pages\nSimulation\nHow to Run a Loader Case - Loading files\nHow to create a Renegotiation case with mock data\nRun Simulation\nApplication Versions\nOverview\nReleases\nReleases & App Version Mapping\nR3.5\nR3.6\nR3.7\nR4.1 And R4.2\nR4.3\nR4.4\nR4.5\nR4.6\nAOMFW\nCreating a new AOMFW Application Version\nAOM\nCreate a new AOM Application Version", "source": "VODKB-200723-160306.pdf"}
{"id": "aa9ca5eec441-0", "text": "2674\nArtefacts to deploy to switch any application version to Live\n914098: Designing the process to support feature-based releases\nDeployment to make an Application Version Live\nVF Confluence Links\nR 4.04\nR4.05\nR4.06", "source": "VODKB-200723-160306.pdf"}
{"id": "d1486a251780-0", "text": "2675\nDesign\nLoader Case Design\nBatch NBA Case Design\nExtractor Case Design\nHousekeeping Case\nCommon Case Flows\nCheckpoint Check\nGenerate Extract Agent Activity Updates\nInclude recommitted in OBC purge file\nApply Volume Constraints Redesign\nScheduler Design\nThrottling Design\nSubscription Case Design\nChannel Execution Approval & Switch Control Implementation\nProduct & Offer Catalog Design\nVodafone reference architecture\nBDC Models\nStore All Outbound Communications Sent\nUnsubscribe Case Design\nExtract the new IH Report table to EDW\nStore IH Reporting fields in IH Reporting table\nCase Dependencies\nGetNBA Response Mapping For IVR\nApply Volume Constraints for Customers in Control Group\nExtend BundleEventAPI for Additional Parameters\nAOM RT Aggregated Event Store\nExtend Trigger Event for Sales Order Events\nRecommendations Portal\nProvide the ability to define and manage an effective FUT Cohort within AOM for Treatments\nProvide Better Alignment of AOM Logging Processes (AOM-1797)\nSimulation Orchestration\nAOM RT Aggregated Event Store - Account Event\nData Load Threshold Assurance\nApp Changes for LIVE UAT Seed Test\nCSO Transform - Modify Order\nSave Offers Metadata\nOffers Case Management and Setup\nDecision Metadata for GR and GPL APIs\nSubmit Basket Request Body Additional Attributes\nTasker Case\nHandle Business Logic Error In GetNBA API - 526157\nCalling Capture Response in Offers Setup Stage\nGet Product List V2 Enhancements\nProduct Cataogue Data Page & Catalogue Sync Changes\nStore Dataflow Response \nExpand all Collapse all", "source": "VODKB-200723-160306.pdf"}
{"id": "7932c5f5e3b7-0", "text": "2676\nAsync Capture Response\nBranching\nChannel Management\nSend SMS Message\nSimulation Portal\nBack out IH\nAssisted 2nd Line Acquisition\n933266: Refresh GetCustomer info every time VADR is launched\n991853: Recommendation Reasons\n991858: Include Digital in Commercial UI\nUpgrades - Get Customer performance improvement (1035177, 959910)\n1187062 - Newly added column mappings for device_v\nSOHO\nRedesign WBW lookup to use Data Type instead of Decision data (ADO 1163201)\n1190526 - Consume Strategic Roaming feed\nAutomated Order Submission (AOS)", "source": "VODKB-200723-160306.pdf"}
{"id": "850eb97c53f4-0", "text": "2677\nLoader Case Design\n \n[ Setup ]\nSetup\n \n[ Initialise Loader ] [ Inspect ] [ Ingest ] [ Prepare Usage Charges ] [ Digest ] [ Process Usage Charges ] [ Functionality ]\nInitialise Loader\nCalls Initialise flow \nChanges the stage to Elapsed if all of the check points configured are passed\nIf the check point is valid, calls InitialiseLoader activity\nSetups/Initialises below parameters\nWork Area\nIsCaseSubType's \nLoaderFileAttributes \nArchivePath\nIncomingPath\nIncomingS3Path\nManifestArchiveS3Path\nGets all values configured with LoaderFileAttributes into Primary page \nFirstly takes from LoaderFileAttributes string into CommonLoaderEntity page \nCopies CommonLoaderEntity page into Primary page\nAnd are related attributes are copied into CommonLoaderEntity page from Primary \nPopulates EntityList value-list property with LoaderEntityList AOM Config\nLoops through each EntityList (from EntityList value-list property)\nCopies CommonLoaderEntity Page into LoaderEntity Page\nGets the FileAttributes AOM Config for the Current Entity\nAdopts the Entity specific FileAttributes JSON into LoaderEntity (overwrites LoaderFileAttributes with FileAttributes) \nSets the LoaderEntityName within LoaderEntity Page\nCopies LoaderEntity Page into LoaderEntities Page Group property", "source": "VODKB-200723-160306.pdf"}
{"id": "ee1bd1e4e14f-0", "text": "2678\nIn case of any failure, calls NotifySupport flow\nInspect\n \nCall Inspect flow \nCall InspectDropZone activity\nInitialized below variables\nReady \u2192 true\nHasFiles \u2192 false\nDiagnosticData \u2192 \u201c\u201c\nManifestFilePath \u2192 \u201c\u201c\nLocal.NotInS3 \u2192 If the IncomingS3Path is null/empty set true, else false\nIf the manifest file does not exists at the loader level & NotInS3 is not true, populate Local.ManifestFilename with the latest \nmanifest file pattern from IncomingS3Path\nIf there is no manifest file found in the previous location, set Ready as false & DiagnosticData as manifest file was not found in \nIncomingS3Path and jump to Fin which exits the activity by clearing clipboardpages created as part the activity\nTransfer the ManifestFile to IncomingPath wrt the TransferMode ( copy or move )\nPopulate ManifestFilePath from the absolute path of the manifest file in IncomingPath\nCall @AOMUtilities.PopulateFileInToTextValueList to read the contents of the manifest file and populate that into TextValueList\nLoop through TextValueList which contains the list of input files to check if the input file exists\nIf file is in Incoming path call @AOMUtilities.FileExists function else call @AOMUtilities.S3FileExists function to validate if file \nexists in the location\nIf the file not found in the corresponding location, set Ready flag as false and populate DiagnosticData as the input file was \nnot found in incoming path\nLoop through the Loader Entities\nInitialize below properties\nHasFiles \u2192 false\nTextValueList \u2192 Primary.TextValueList\nManifestFilePath \u2192 Primary.ManifestFilePath\nCall InspectEntityFiles activity \nInit Ready, DiagnosticData, NotInS3", "source": "VODKB-200723-160306.pdf"}
{"id": "e3b0330393a5-0", "text": "2679\nReady \u2192 true\nDiagnosticData \u2192 \u201c\u201c\nLocal.NotInS3 \u2192 true if IncomingS3Path is null\nReset InputFIles property\nIf both of the InputFilePattern & ManifestFilePattern are empty\nSet the ErrorStackTrace and jump to Err\nElse if both of the InputFilePattern & ManifestFilePattern are populated\nCreate a Work page\nLoop through the TextValueList which contains the list of input files from the Manifest & and add it to \nWork.TextValueList if the input filename matches the InputFilePattern\nCopy the temp Work.TextValueList back to the Entity page TextValueList (to contain just the matches)\nSet the Ready flag to false if the TextValueList is empty and is Mandatory and jump to Fin else jump to LTVL (Loop \nthrough the TextValueList)\nElse if the InputFilePattern is empty and ManifestFilePattern is populated\nIf (NotInS3 != true) \n\u2192 Get the oldest Manifest File from S3 bucket\n\u2192 Set the Ready flag to false if the manifest file is not found at the S3 path & Mandatory = true and jump to Fin\n\u2192 Copy the ManifestFile into IncomingPath\n\u2192 Setup the local ManifestFilePath \nElse (NotInS3 = true)\n\u2192 Get the oldest Manifest File from Incoming Path \n\u2192 Set the Ready flag to false if the manifest file is not found at the Incoming path & Mandatory = true and jump to Fin\nRead the contents of the manifest file and populate that into TextValueList\nElse if the InputFilePattern is populated and ManifestFilePattern is empty\nGet the input files matching the InputFilePattern from the configured incoming path\nSet the Ready flag to false if there are no files found & Mandatory = true and jump to Fin\nLoop through the TextValueList which contains the list of input files\nCheck if the input file exists", "source": "VODKB-200723-160306.pdf"}
{"id": "e3b0330393a5-1", "text": "Loop through the TextValueList which contains the list of input files\nCheck if the input file exists\nSet the Ready flag to false if the file is not found and jump to Fin\nIf HasChecksum is true\n\u2192 Check if the checksum file is available\n\u2192 Set the Ready flag to false if the checksum file is not found and jump to Fin\n\u2192 Validate the Checksum of the input file\n\u2192 Handle checksum errors\nAdd the FilePath to InputFiles & set HasFiles as true\nGet the Load Type from the file name if the LoadType is of file type\nWhen LoaderEntity is Ready & has no files (!HasFiles) \nSet the LatestEntityState to Skipped\nJump to PC ( Copy the LoaderEntity into LoaderEntities and Exit iteration) \nWhen LoaderEntity is Ready \nSet the LatestEntityState to Ready if InspectEntityFiles was successful\n Jump to PC ( Copy the LoaderEntity into LoaderEntities and Exit iteration) \nWhen LoaderEntity is Not Ready \nSet the LatestEntityState, Ready flag and DiagnosticData from the previous call on failure\nCopy the LoaderEntity.ErrorStackTrace to Primary if there was an error", "source": "VODKB-200723-160306.pdf"}
{"id": "23a4af872f40-0", "text": "2680\n Jump to PC ( Copy the LoaderEntity into LoaderEntities and Exit iteration) \nIngest\nCalls Prepare flow to call Prepare activity and handle failures\nGets the GNUPGHome path, SecretsManagerRegion, SecretsManagerId, GPGPassphrase\nCreates WorkArea and Archive folders\nLoop through the LoaderEntities (to possibly Dycrypt the InputFiles, Truncate and Drop Indexes on the staging table)\nExit Iteration if LatestEntityState for this Entity is Skipped\nSet Compressed flag as true, if any CompressionType defined in the file attributes config\nLoop through the input files\nIf the input file is neither Compressed Nor Encrypted\nCall GNUcp function to copy the raw input file to the WorkAreaPath\nAdd the workarea input file to DecompressedFiles / Add the input file to TextValueList for Archival\nIf the input file is Encrypted\nPopulate decryption file path to store encrypted results (WorkAreaPath + File Name - .gpg)\nDecrypt the input file into decryption file path\nIf file is not compressed append decrypted file path into DecompressedFiles, else skip step\nIf the input file is Compressed\nPopulate decompression file path to store decompressed results\nIf the file is Encrypted, use decryption file path\nElse use current input file path\nDecompress the input file wrt compress type (zip/tgz) and populate decompressed files in given output clipboardproperty \n(DecompressedFiles)\nAdd the input file to TextValueList for Archival later\nAdd the cksum file to TextValueList for Archival later if applicable\nAdd the ManifestFilePath file to TextValueList for Archival later if available in LoaderEntity and NA in Primary page, and case sub \ntype not equals to BDC\nLoop through the LoaderEntity.TextValueList to append them to the Primary TextValueList for archival later\nClear LoaderEntity.TextValueList", "source": "VODKB-200723-160306.pdf"}
{"id": "23a4af872f40-1", "text": "Clear LoaderEntity.TextValueList\nIf Case Sub Type is not BDC/Event\nCreate a page - HTSLStatus\nSetup the staging TableName, Skip and init SchemaName\nTableName = EntityNAme + \u201c_st\u201d\nSchemaName = \u201c\u201c\nSkip = if Case Sub Type is SpineV2 and Load Type is full true, else, false\nHTSLStatus.TableName = LoaderEntiy.TableName\nDrop the indexes on the staging table (RDB-Delete, Indexes)", "source": "VODKB-200723-160306.pdf"}
{"id": "1db47c127595-0", "text": "2681\nTruncate the staging table (RDB-Delete, Truncate)\nCopy the updated LoaderEntity back into LoaderEntities\nAdd the ManifestFilePath file to TextValueList for Archival later only once when available in the Primary Page\nLoop through the TextValueList to archive the files listed\nCall the GNUmv function to move the current file to the archive folder\nIf DevMode = True, Move files back to the LoaderIncomingPath\nClear the TextValueList\n \nCalls InitialiseHTSLStatus flow to call InitialiseHTSLStatus activity and handle failures\nGet the LoaderLoopLimit and Init the LoopCounter\nLoop through the LoaderEntities\nSkip HTSL (exit iteration) if LoaderEntity.Skip is true or if LatestEntityState for this Entity is Skipped\nLoop through the LoaderEntity.DecompressedFiles\nCreate a new page - HTSLStatus\nInitialise the HTSLStatus page (CaseId, FilePath, TableName, Status, StatusTimeStamp)\nPersist the HTSLStatus page\nStatus = Init\nQueue the HTSL Job into HTSLQueueProcessor\nGet the AOM DB JNDI Name, TableName & FilePath\nUpdate the NodeId, Status to Processing and the StatusTimestamp\nPersist the HTSLStatus page\nStatus = Processing\nStart the timer\nInvoke HTSL to load the input file, using @AOMUtilities.HTSL function, which returns the Record Count within the file\nLoads the input file into staging table\nStop the timer\nUpdate the StatusTimestamp, EndTimestamp, RecordCount, MetaData and the Status to Complete\nPersist the HTSLStatus page\nStatus = Completed\n \nCalls PostProcessHTSL flow to call PostProcessHTSL activity and handle failures\nInitialise flags\nReady = false\nLoopCounter = LoopCounter + 1\nLocal.Loaded = true\nReset the HTSLStatuses & DiagnosticData\nLoop through the LoaderEntities", "source": "VODKB-200723-160306.pdf"}
{"id": "1db47c127595-1", "text": "Local.Loaded = true\nReset the HTSLStatuses & DiagnosticData\nLoop through the LoaderEntities\nSkip the loop if Latest Entity State is already Loaded or Skipped\nGet the Incomplete HTSLStatuses for the current LoaderEntity\nIf there are no Incomplete HTSLStatuses\nCall InitialiseIndexStatus Activity to kickoff the Indexing for the current loaded entity\nInitialise the IndexStatus page (CaseId, TableName, Status, StatusTimeStamp)\nPersist the IndexStatus page\nStatus = Init", "source": "VODKB-200723-160306.pdf"}
{"id": "0a5fc5d60a8d-0", "text": "2682\nQueue the HTSL Job into IndexingQueueProcessor\nUpdate the NodeId, Status to Processing and the StatusTimestamp\nPersist the IndexStatus page\nStatus = Processing\nStart the timer\nDrop the indexes on the specified table - (RDB-Delete, Indexes)\nCreate the indexes on the specified table - (RDB-Save, Indexes)\nStop the timer\nUpdate the StatusTimestamp, EndTimestamp, RecordCount, MetaData and the Status to Complete\nPersist the IndexStatus page\nStatus = Completed\nSet the LatestEntityState for the current entity to Loaded\nElse (there are Incomplete HTSLStatuses) , loop through the Incomplete HTSLStatuses\nCopy the current HTSLStatus into HTSLStatuses page group property for Diagnostics\nDerive the FileName\nHandle Errors for HTSL Status\nSet the DiagnosticData\nJump to Fin If the ErrorStackTrace was populated earlier\nLoop through the LatestEntityState to determine of all of the applicable ones are Loaded\nSet the Local.Loaded flag to false if the current entity state is not Loaded or Skipped\nIf the Local.Loaded flag is true, set the Ready flag to true and Jump to Fin\n \nCalls InspectIndexStatus flow to call InspectIndexStatus activity and handle failures\nSets Ready, LoopCounter, Local.Indexed properties AAA\nIndexStatuses and DiagnosticData properties removed to reset the status\nLoop through the LoaderEntities to inspect the Index Status for each entity\nGet LatestEntityState and if the current entity is already indexed or skipped, exit the loop iteration\nIf the Skip flag for the current entitiy is true, specify the entitiy in LatestEntityState as \u201cIndexed\u201d\nGet incomplete index statuses from and store in IndexStatuses page.\nIf there is no result returned, flag current entity in LatestEntityState as \u201cIndexed\u201d\nLoop IndexStatuses pagelist to check incomplete index statutes", "source": "VODKB-200723-160306.pdf"}
{"id": "0a5fc5d60a8d-1", "text": "Loop IndexStatuses pagelist to check incomplete index statutes\nCopy current IndexStatus for the current entitiy to Primary.IndexStatus\nIf the Status is \u201cError\u201d, populate Primary.ErrorStackTrace as the indexing is failed.\nSet Primary.DiagnosticData for the current status\nIf ErrorStackTrace was populated earlier, jump fin and clear clipboard pages created as part of activity. Else, skip the step\nLoop through Primary.LatestEntityState text value group\nIf the State is not equal to \u201cIndexed\u201d or \u201cSkipped\u201d, flag Local.Indexed as false. Else skip the step\nIf Local.Indexed is true, set Ready flag as true and jump to Fin step. Else, skip step\nIf LoaderCounter is greater than the loop limit defined in aom config, then populate ErrorStackTrace as the loop limit has been reached \nand jump to Err step to produce errors in AOMError table\nIf the step is Fin, jump to Clean step to clear all the clipboardpages created as part of InspectIndexStatus activity\nIn case of any failure, calls NotifySupport flow", "source": "VODKB-200723-160306.pdf"}
{"id": "48c9b7a2ae77-0", "text": "2683\nPrepare Usage Charges", "source": "VODKB-200723-160306.pdf"}
{"id": "33accfb93e37-0", "text": "2684\n \nThis process is only run if the IsPrepareUsageChargesRunnable WHEN rule is true - LatestEntityState = 'Indexed'\nCreates new SubscriptionInvoiceChargeHolding page\nSets CaseId, TimeToLive and PartitionKey on this page.\nCalls SQL-Rule PopulateCUH to copy records from staging table subs_invoice_charge_st into table subs_invoice_charge_holding \nwhere charge_type is ''USAGE_CHARGE\". Populates records with CaseId, TimeToLive and PartitionKey.\nIn case of any failure, calls NotifySupport flow.\nDigest\nCalls Digestor flow to digest data from staging table to alphadata or betadata schemas\nCall InitialiseDigestStatus to start writing from stagin table to alphadata or betadata wrt current live schema\nLoop through for LoaderEntities to process for each entitiy\n If the LatestEntityState for the current entity is \u201cSkipped\u201d, exit the iteration. Else, go on processing\nIf the LatestEntityState for the current entity is \u201cDigested\u201d, mark it as \u201c1stDigested\u201d as the data will be populated for alphadata and \nbetadata. Else, skip the step\nInitialize the DigestStatus and populate the Status of the digesting process in digest_status table as \u201cInit\u201d\nQueue the record in to DigestingQueueProcessor queue processor which calls VFUK-FW-AOMFW-Data-\nDigestStatus.ProcessQueueItem activity\nEach entitiy will be processed in multiple nodes to have a better performance\n Initialize below flags for the current entity is being processed\nLocal.CurrentTimeStamp \u2192 @DateTime.getCurrentTimeStamp()\nLocal.CaseId \u2192 .CaseId\n.Status \u2192 \"Processing\"\n.StatusTimestamp \u2192 Local.CurrentTimeStamp\n.StartTimestamp \u2192 Local.CurrentTimeStamp\n.NodeId \u2192 pxProcess.pxSystemNodeID\nUpdate the digest_status table with latest updates defined in previous step", "source": "VODKB-200723-160306.pdf"}
{"id": "33accfb93e37-1", "text": ".NodeId \u2192 pxProcess.pxSystemNodeID\nUpdate the digest_status table with latest updates defined in previous step\nCall the VFUK-FW-AOMFW-Data-DigestStatus.LoadData connect sql and pass EntitiyType(eg: pc_discount, oc_bundle) and \nLoadType(full or delta) which will load the data from staging table to alphadata or betadata wrt current live schema. \nIf the alphadata is the live one now, it will load into betadata and if the betadata is live now, it will load into alphadata. \nAll the insert, truncate scripts are defined in database level and orchestrated in database layer. \nOnce one of the data schema is populated it becomes live other one becomes non-live. \nIf the entitiy has a view it points to live schema\nUpdate digest_status as \u201cComplete\u201d with below flags\nLocal.CurrentTimeStamp \u2192 @DateTime.getCurrentTimeStamp()\nStatus \u2192 \"Complete\"\nStatusTimestamp \u2192 Local.CurrentTimeStamp\nEndTimestamp \u2192 Local.CurrentTimeStamp\nMetaData \u2192 Local.MetaData", "source": "VODKB-200723-160306.pdf"}
{"id": "aaf1cdc9c7c5-0", "text": "2685\n \n \nIf the CaseSubType is SpineV2 process below steps within the activity. Else, exit iteration\nPopulate EntitiyName and call VFUK-FW-AOMFW-Data-DigestStatus.GetNonLiveSchemaName connect sql which returns the \ncurrent non-live schema for the current entity\nPopulate below properties and copy into Primary.LoaderEntities page group\nUpdate Status \u201cError\u201d in digest_status table if there is an issue issue while loading data from staging table into alphadata or \nbetadata\nIn case of any failure, calls NotifySupport flow\nCalls InspectDigestStatus flow to to check if any error occured while processing data from stating table\nCalls InspectDigestStatus activity\nInitialize below flags to indicate the status of digested entities\nReady \u2192 false\nLoopCounter \u2192 LoopCounter + 1\nLocal.Digested \u2192 true\nRemove DigestStatuses & DiagnosticData properties to reset\nLoop through the LoaderEntities to check status for each one of them\nSet Local.State with LatestEntityState for the current entity\nGet the Incomplete DigestStatuses for the current LoaderEntity from digest_status table\nIf there is no record returned mark LatestEntityState for the current entity as \u201cDigested\u201d. Else skip the step\nLoop through the DigestStatus results to check incomplete digest statutes\n \nProcess Usage Charges\nThis process is only run if the IsProcessUsageChargesRunnable WHEN rule is true - LatestEntityState = 'Digested'\nCalls CaseIgnitor activity for Tasker Case. Sets Tasker.CaseSubType to \u2018CUH\u2019 and Tasker.LoaderCaseId to CaseId (.pyID).\nIn case of any failure, calls NotifySupport flow\n \n \n \nTBC\u2026\n--", "source": "VODKB-200723-160306.pdf"}
{"id": "a24127d34648-0", "text": "2686\n \n \n \n \n \nSetupInitialise Loader Checks, if the case triggered time is falling in between the current checkpoint interval, if \nso then case will continue processing & case is runnable wrt to the conditions defined in \nIs Case Runnable activity, the case processing started and case status is updated as \n\u201cRunning\u201d. Else it will snooze until the current time is falling in between the current \ncheckpoint interval. \nPopulate LoaderEntities page group for each entity available in LoaderEntityList and \nget File Attributes in both case sub type/entity level within this page (Entity level file \nattributes will overwrite the case sub type level attributes). \nInspect Incoming folder paths that are defined in the AOMConfig are checked for each entity if \nthe file exists in the corresponding location. If the files do not exist in the defined \nlocation, the case snoozes and loops for file check if the case is not elapsed.\nGets the oldest ManifestFilePath within the Incoming folder path using \nManifestFilePattern defined in Loader File Attributes, and sets Ready flag as False if the \nManifestFilePath is not found. If it is available, loops through the file list and sets Ready \nflag as False, if the file is not found in the Incoming folder path. \nLoops through the entities within the LoaderEntities page group and calls \nInspectEntityFiles activity for each entity:\nIf both ManifestFilePattern & InputFilePattern are available, get the matching input file \nnames with InputFilePattern from manifest file into the TextValueList property. If only \nManifestFilePattern available, checks if the manifest file is available. If it is available, \npopulates the content into TextValueList property, else sets Ready flag as false. If only \nInputFilePattern is available, gets the input files matching the InputFilePattern from the", "source": "VODKB-200723-160306.pdf"}
{"id": "a24127d34648-1", "text": "InputFilePattern is available, gets the input files matching the InputFilePattern from the \nconfigured incoming path. Checksum files are validated & LoadType is set if it is \nconfigured as \u2018file\u2019.\n \n \nProcessIngest WorkAreaPath, ArchivePaths directories are created, files are decrypted & \ndecompreessed for processing. Drops indexes on staging tables and truncates. \nHTSL Status table is updated for the current file as \u201cInit\u201d for each of the decompressed \nfile. Current files are moved into the archive folder location.\n(PostProcessHTSL & InspectIndexStatus can be explainedinmore details) \nPrepare Usage Charges If the CaseSubType is Spine\nIf subs_invoice_charge files have been successfully loaded for Spine, then copy \nrecords from the staging table subs_invoice_charge_st to the holding table \nsubs_invoice_charge_holding where charge_type = 'USAGE_CHARGE'.\nValidate Load Threshold In order to provide assurance of data being loaded into AOM, there is a requirement to \nbe able to pause/stop the Loader when a threshold for a particular entity has exceeded a \ngiven median/average number of records.\nDigest TBD\nClear Entity Cache If CaseSubType is one of below list Clear Entity Cache flow is running to truncate \nDataSets and Flush DataPages \nProduct Catalogue\nOffer Catalogu\nSpineCase Stage Case Step Functionality", "source": "VODKB-200723-160306.pdf"}
{"id": "a140bdeda8be-0", "text": "2687\nBDC\nThere is an activity which is called Clear Entity Cache in this flow. This activity flushes \nthe datapages, truncate the datasets.\nIf CaseSubType = ProductCatalogue\nFlush Datapages: D_CalculatedOffersForUpgrade, D_VFTQualifier\nIf CaseSubType = OfferCatalogue\nFlush Datapages: D_CalculatedOffersForUpgrade, \nD_EligibleCombiBundleQualifierReward\nIf CaseSubType =Spine\nFlush Datapages: D_VFUKFWAOMFWDataProductReference\nIf CaseSubType =BDC\nFlush Datapages: D_IVRModel\nProcess ADM Run the below Dataflows if the CaseSubType is equaled to Spine and if the status of \ndata flow fails it re-checks the status of DF after a 1 minute wait time and notifies the \nsupport team in case of failure.\nStartUniqueSubscriptionListWithSMSOutcomesT2S\nStartProcessingSMSOutcomesT2S\nPopulate Unica Campaign \nEventsCampaignCodes defined in the AOMConfig table are populated into the Unica Campaign \nEvent table if the SubCaseType is equal to SpineV2.\nProcess Call Centre \nResponsesIf the CaseSubType is equal to CCR below operations are applied sequentially. If the \nstatus of each data flow fails, it re-checks the status of DF after a 1 minute wait time and \nnotifies the support team in case of failure.\nUniquePartyListWithDiallerOutcomes decision data store is truncated and \nUniquePartyListWithDiallerOutcomes DF is run to populate the unique list of the \ncustomers for OB calls.\nProcessDiallerOutcomes DF is run.\nProcess Events If the CaseSubType is equal to Event below operations are applied", "source": "VODKB-200723-160306.pdf"}
{"id": "a140bdeda8be-1", "text": "Process Events If the CaseSubType is equal to Event below operations are applied\nWorkAreaPath, ArchivePaths directories are created, files are decrypted for \nprocessing and HTSL Status table is updated for the current file as \u201cInit\u201d. Current files \nare moved into the archive folder location.\nEvent files are processed into Event Status tables.\nIn Existing ProcessEvents activity, new activity InsertWatchDogReportData called \nwhich store the file record count data into watchdog_report_data table.\nFollowing are the new steps added to ProcessEvents activity as part of AOM-1810 :\nCalls a function GetFileLineCount which gets the line count from file path.\nIf .HasHeader is true , then reduce line count by one, otherwise continue with \nexisting line count.\nCall InsertWatchDogReportData activity with parameters required for \nwatchdog_report_data table to insert a record.\nProcess BDC Models \nProcess Catalogue Sync \nProcess Usage Charges If the CaseSubType is Spine", "source": "VODKB-200723-160306.pdf"}
{"id": "95a57004e0a3-0", "text": "2688\n Invoke Tasker Case with Tasker.CaseSubType = 'CUH'. Tasker Case will update \nUsageHistory Decision Data Set with the usage data.\n InsertWatchDogReportData Create New ReportData page which is of class VFUK-FW-AOMFW-Data-WatchDog-\nReportData.\nSet incoming parameter values to ReportData page properties.\nPass ReportData page as a step page to RDB-Save method which calls Insert \nConnect-SQL rule.\nInsert Connect-SQL rule inserts each file with record count into \nwatchdog_report_data table available for reporting purposes\nEnd Finalise Updates CaseStatus and CaseEndTime (FinaliseCase Activity)\nIf there are any errors while executing FinaliseCase Activity then NotifySupport SubFlow \nis invoked.\nIf SendCaseFinaliseEmail is set to false the only email communication will be sent out in \ncase of failure or completion. Checks if SupportEmail is set before sending the email \ncommunication out.\nCase Aborted email will be sent out from this flow.\nAbort\n(Alternative Stage)Finalise Updates CaseStatus and CaseEndTime (FinaliseCase Activity)\nIf there are any errors while executing FinaliseCase Activity then NotifySupport SubFlow \nis invoked.\nIf SendCaseFinaliseEmail is set to false the only email communication will be sent out in \ncase of failure or completion. Checks if SupportEmail is set before sending the email \ncommunication out.\nCase Aborted email will be sent out from this flow.", "source": "VODKB-200723-160306.pdf"}
{"id": "0ff30cbe4e93-0", "text": "2689\nTemp\nIngest\nCalls Prepare flow to call Prepare activity and handle failures\nGet the GNUPGHome path, SecretsManagerRegion, SecretsManagerId, GPGPassphrase\nCreate WorkArea and Archive folders\nLoop through the LoaderEntities (to possibly Dycrypt the InputFiles, Truncate and Drop Indexes on the staging table)\nExit Iteration if LatestEntityState for this Entity is Skipped\nSet Compressed flag as true, if any CompressionType defined in the file attributes config \nLoop through the input files\nIf the input file is neither Compressed Nor Encrypted\nCall GNUcp function to copy the raw input file to the WorkAreaPath \nAdd the workarea input file to DecompressedFiles / Add the input file to TextValueList for Archival\nIf the input file is Encrypted\nPopulate decryption file path to store encrypted results (WorkAreaPath + File Name - .gpg) \nDecrypt the input file into decryption file path\nIf file is not compressed append decrypted file path into DecompressedFiles, else skip step\nIf the input file is Compressed\nPopulate decompression file path to store decompressed results\nIf the file is Encrypted, use decryption file path \nElse use current input file path \nDecompress the input file wrt compress type (zip/tgz) and populate decompressed files in given output clipboardproperty \n(DecompressedFiles)\nAdd the input file to TextValueList for Archival later\nAdd the cksum file to TextValueList for Archival later if applicable\nAdd the ManifestFilePath file to TextValueList for Archival later if available in LoaderEntity and NA in Primary page, and case sub \ntype not equals to BDC\nLoop through the LoaderEntity.TextValueList to append them to the Primary TextValueList for archival later\nClear LoaderEntity.TextValueList", "source": "VODKB-200723-160306.pdf"}
{"id": "0ff30cbe4e93-1", "text": "Clear LoaderEntity.TextValueList\nIf Case Sub Type is not BDC/Event\nCreate a page - HTSLStatus\nSetup the staging TableName, Skip and init SchemaName\nTableName = EntityNAme + \u201c_st\u201d\nSchemaName = \u201c\u201c\nSkip = if Case Sub Type is SpineV2 and Load Type is full true, else, false\nHTSLStatus.TableName = LoaderEntiy.TableName", "source": "VODKB-200723-160306.pdf"}
{"id": "9600a55e693f-0", "text": "2690\nDrop the indexes on the staging table (RDB-Delete, Indexes) \nTruncate the staging table (RDB-Delete, Truncate) \nCopy the updated LoaderEntity back into LoaderEntities\nAdd the ManifestFilePath file to TextValueList for Archival later only once when available in the Primary Page\nLoop through the TextValueList to archive the files listed\nCall the GNUmv function to move the current file to the archive folder\nIf DevMode = True, Move files back to the LoaderIncomingPath\nClear the TextValueList\n \nCalls InitialiseHTSLStatus flow to call InitialiseHTSLStatus activity and handle failures \nGet the LoaderLoopLimit and Init the LoopCounter\nLoop through the LoaderEntities\nSkip HTSL (exit iteration) if LoaderEntity.Skip is true or if LatestEntityState for this Entity is Skipped\nLoop through the LoaderEntity.DecompressedFiles\nCreate a new page - HTSLStatus\nInitialise the HTSLStatus page (CaseId, FilePath, TableName, Status, StatusTimeStamp) \nPersist the HTSLStatus page \nStatus = Init\nQueue the HTSL Job into HTSLQueueProcessor\nGet the AOM DB JNDI Name, TableName & FilePath\nUpdate the NodeId, Status to Processing and the StatusTimestamp\nPersist the HTSLStatus page \nStatus = Processing \nStart the timer\nInvoke HTSL to load the input file, using @AOMUtilities.HTSL function, which returns the Record Count within the file\nLoads the input file into staging table\nStop the timer\nUpdate the StatusTimestamp, EndTimestamp, RecordCount, MetaData and the Status to Complete\nPersist the HTSLStatus page \nStatus = Completed\n \nCalls PostProcessHTSL flow to call PostProcessHTSL activity and handle failures \nInitialise flags\nReady = false\nLoopCounter = LoopCounter + 1\nLocal.Loaded = true", "source": "VODKB-200723-160306.pdf"}
{"id": "9600a55e693f-1", "text": "Initialise flags\nReady = false\nLoopCounter = LoopCounter + 1\nLocal.Loaded = true\nReset the HTSLStatuses & DiagnosticData\nLoop through the LoaderEntities\nSkip the loop if Latest Entity State is already Loaded or Skipped\nGet the Incomplete HTSLStatuses for the current LoaderEntity\nIf there are no Incomplete HTSLStatuses\nCall InitialiseIndexStatus Activity to kickoff the Indexing for the current loaded entity\nInitialise the IndexStatus page (CaseId, TableName, Status, StatusTimeStamp)\nPersist the IndexStatus page", "source": "VODKB-200723-160306.pdf"}
{"id": "2a1933d2fbd3-0", "text": "2691\nStatus = Init\nQueue the HTSL Job into IndexingQueueProcessor\nUpdate the NodeId, Status to Processing and the StatusTimestamp\nPersist the IndexStatus page \nStatus = Processing\nStart the timer\nDrop the indexes on the specified table - (RDB-Delete, Indexes) \nCreate the indexes on the specified table - (RDB-Save, Indexes) \nStop the timer\nUpdate the StatusTimestamp, EndTimestamp, RecordCount, MetaData and the Status to Complete\nPersist the IndexStatus page \nStatus = Completed\nSet the LatestEntityState for the current entity to Loaded\nElse (there are Incomplete HTSLStatuses) , loop through the Incomplete HTSLStatuses\nCopy the current HTSLStatus into HTSLStatuses page group property for Diagnostics\nDerive the FileName \nHandle Errors for HTSL Status \nSet the DiagnosticData\nJump to Fin If the ErrorStackTrace was populated earlier\nLoop through the LatestEntityState to determine of all of the applicable ones are Loaded\nSet the Local.Loaded flag to false if the current entity state is not Loaded or Skipped\nIf the Local.Loaded flag is true, set the Ready flag to true and Jump to Fin\n \nCalls Digestor flow \nCall InitialiseDigestStatus activity and handle failures \nLoop through the LoaderEntities\nExit Iteration if LatestEntityState for the current Entity is Skipped\nUpdate the Latest Entity State as 1stDigested if it was already Digested as part of the 1st Sequence\nCreate a new page - DigestStatus\nInitialise the DigestStatus page for below parameters\nCaseId\nEntityName\nLoadType\nStatus = Init\nStatusTimestamp\nPersist the DigestStatus page\nQueue the Digesting Job into DigestingQueueProcessor\nUpdate the NodeId, Status to Processing and the StatusTimestamp\nPersist the page \nStatus = Processing \nStart the timer", "source": "VODKB-200723-160306.pdf"}
{"id": "2a1933d2fbd3-1", "text": "Persist the page \nStatus = Processing \nStart the timer\nExecute load_data function (RDB-Save, LoadData) \nTakes EntityName & LoadType as inputs\nGets DDLs from admin_ingest_ddl_metadata table for both full/delta types", "source": "VODKB-200723-160306.pdf"}
{"id": "d28a4d9a9c4b-0", "text": "2692\nUses full_ddl_statement/delta_ddl_statement regarding to the load type\n\u2192 full ddl example: select load_table_replace('oc_bundle_st', 'nonlive.oc_bundle');\n\u2192 full ddl example: select truncate_insert('product_holding_st', 'nonlive.product_holding', true, 'full');\n\u2192 delta ddl example: select load_table_merge_using_changeid('oc_bundle_st', 'nonlive.oc_bundle', \nget_primary_key('oc_bundle_st'));\n\u2192 delta ddl example: analyze product_holding_st(asset_integ_id, subscription_id); select \ndelete_insert_merge('product_holding_st', 'nonlive.product_holding', get_primary_key('product_holding_st'), true, \n'delta');\nGets loader_type, live_schema_name, nonlive_schema_name from admin_loader_config_v \nReplaces \u2018nonlive\u2019 and \u2018live' strings with real schema names within l_ddl_statement\nExecutes the ddl : l_ddl_statement\nStop the timer\nUpdate the StatusTimestamp, EndTimestamp, MetaData and the Status to Complete\nPersist the page \nStatus = Complete\nIf CaseSubType = SpineV2\nCreate a new page - DigestStatus2\nSet the EntityName\nExecute the GetNonLiveSchemaName function (RDB-Open, GetNonLiveSchemaName) \nGets the nonlive schema name & returns it under Metadata parameter\nSetup below parameters within LoaderEntity\nTableName \u2192 EntiyName\nSchemaName \u2192 DigestStatus2.MetaData + \".\" (nonlive schema name + \u201c.\u201d)\nSkip \u2192 false\nCopy the updated LoaderEntity back into Loader Entities", "source": "VODKB-200723-160306.pdf"}
{"id": "d83d10854cd1-0", "text": "2693\nConfigure new spine entity to the spine loader\nOverview\nNew Spine entity will be added to loader case - LMS spine\nImplementation\nAOM Config Changes\nNew Entity will add in Spine\nDataSet\nDatasetName: Loans\nPrimaryKey: SubscriptionId, LoanId\nClass\nClass rule will create by the DatabaseMappings Landing Page for performing SQL operations on an external database table\nClassName: VFUK-FW-AOMFW-Data-Loans\nParentClass: VFUK-FW-AOMFW-Data\nTableName: loans_v \nPrimaryKeys: SubscriptionId, LoanId\nRuleset: AOMFW - Database\n--schema will be empty --\n \nExternal MappingLoaderEntityList Spine subscription,account,contact,product_holding,pro\nduct_reference,subs_flex_attribute,subs_invoice\n_charge,address,tps,device,benefits, loans loans added in R2.11\nFileAttributes loans {\"ManifestFilePattern\": \"loans_.*_.*.readme\", \n\"PositiveVariationPercentage\":10 , \n\"NegativeVariationPercentage\":10}New oneConfigType ConfigName ConfigValue Notes\nSubscription Id SubscriptionId\nLoan_ID LoanId\nPrimary_Loan_status PrimaryLoanStatusColumn Name Pega Property Name", "source": "VODKB-200723-160306.pdf"}
{"id": "f461559f543c-0", "text": "2694\n Secondary_loan_status SecondaryLoanStatus\nTertiary_loan_status TertiaryLoanStatus\nLoan_start_dt LoanStartDate\nLoan_end_dt LoanEndDate\nLoan_tenure LoanTenure\nLoan_amount LoanAmount\nMonthly_Recurring_Cost MonthlyRecurringCost\nLoan_Arrears_Amount LoanArrearsAmount\nLoan_Outstanding_Balance LoanOutstandingBalance\nRemaining_months RemainingMonths\nDevice_type DeviceType\nDevice_description DeviceDescription\nLoan_upfront_payment LoanUpfrontPayment\nRecord_Dt RecordDate\nDeleted_flg DeletedFlag", "source": "VODKB-200723-160306.pdf"}
{"id": "b9857bbb8fe2-0", "text": "2695\nLoader Process - Process Usage Charges\nUpdates to Loader Case to get all usage charge data from subs_invoice_charge. Loader case loads files for subs_invoice_charge.\nAfter the Ingest process of the Loader Case, Connect SQL rule is called to load data from s u b s _ i n v o i c e _ c h a r g e _ s t table into \nholding table s u b s _ i n v o i c e _ c h a r g e _ h o l d i n g for records where charge_type = \u2018USAGE_CHARGE\u2019\n Rule to load subs_invoice_charge information into a separate holding table - s u b s _ i n v o i c e _ c h a r g e _ h o l d i n g - that is keyed by \ncase_id \nSelect only records where charge_type = \u2018USAGE_CHARGE\u2019\nselect subscription_id, invoice_dt, \ncharge_type,usage_category_id,usage_subcategory_id,usage_cnt,used_amt,outside_bundle_used_amt from \nsubs_invoice_charge_st where charge_type = 'USAGE_CHARGE';\nThis part is synchronous \nOnly to be done if there is a file for subs_invoice_charge \nAt End stage of Loader Case, start New Tasker Case asynchronously\nPass parameter LoaderCaseId with CaseId (.pyID)\nClass Name: VFUK-FW-AOMFW-Data-SubscriptionInvoiceChargeHolding\nTable Name: subs_invoice_charge_holding\n Table Structure\ncase_id CaseId String Case Id\nsubscription_id SubscriptionId String Subscription Id\ninvoice_dt InvoiceDate DateTime Invoice Date\ncharge_type USAGE_CHARGE ChargeType String Charge Type\nusage_category_id UsageCategoryId Decimal Usage Category Id\nusage_subcategory_id UsageSubCategoryId Decimal Usage Subcategory Id\nusage_cnt UsageCount Decimal Usage Count\nused_amt UsedAmount Decimal Used Amount\noutside_bundle_used_a", "source": "VODKB-200723-160306.pdf"}
{"id": "b9857bbb8fe2-1", "text": "usage_cnt UsageCount Decimal Usage Count\nused_amt UsedAmount Decimal Used Amount\noutside_bundle_used_a\nmt OutsideBundleUsedAmou\nntDecimal Outside Bundle Used \nAmount Column Name Constraints Pega Property Pega Type Notes \nCopies records from subs_invoice_charge_st staging table to subs_invoice_charge_holding table for charge_type = \n'USAGE_CHARGE'. Sets CaseId, TimeToLive and PartitionKey to pass to SQL-Rule.\nApplies To VFUK-FW-AOMFW-Work-Loader\nRuleset AOMFW\nInput Parameter NA PrepareUsageCharges Activity", "source": "VODKB-200723-160306.pdf"}
{"id": "e2aab36f6054-0", "text": "2696\nOutput Parameter NA\nError Handling Primary Catch-all Error Handler\nLogs to Error Log\n Loads subs_invoice_charge information from s u b s _ i n v o i c e _ c h a r g e _ s t into a holding table - s u b s _ i n v o i c e _ c h a r g e _ h o l d i n g- that is \nkeyed by case_id . Select only records where charge_type = \u2018USAGE_CHARGE\u2019.\nApplies To VFUK-FW-AOMFW-Data-SubscriptionInvoiceChargeHolding\nRuleset AOMFW\nSQL {SQLPage:SQLDiagnostics}\ninsert\n into\n subs_invoice_charge_holding(subscription_id, invoice_dt, charge_type, usage_category_id, \nusage_subcategory_id, usage_cnt, used_amt, outside_bundle_used_amt, case_id, time_to_live)\nselect\n subscription_id,\n invoice_dt,\n charge_type,\n usage_category_id,\n usage_subcategory_id,\n usage_cnt,\n used_amt, \n outside_bundle_used_amt,\n '{ASIS:.CaseId}' ,\n case\n when (extract(epoch\n from\n (invoice_dt::timestamp - CURRENT_DATE::timestamp)) + '{ASIS:.TimeToLive}')<=0 then 1\n else (extract(epoch\n from\n (invoice_dt::timestamp - CURRENT_DATE::timestamp)) + '{ASIS:.TimeToLive}')\n end as time_to_live\nfrom\n subs_invoice_charge_st\nwhere\n charge_type = 'USAGE_CHARGE';PopulateCUH Connect SQL\nRuns the Tasker Case to process usage charges. This will be called when subs_invoice_charge_holding table has been successfully", "source": "VODKB-200723-160306.pdf"}
{"id": "e2aab36f6054-1", "text": "updated in the Loader case. Sets Tasker CaseSubType to \u2018CUH\u2019 and sets Tasker LoaderCaseId to CaseId (.pyID)\nApplies To VFUK-FW-AOMFW-Work-Loader\nRuleset AOMFW\nInput Parameter NA\nOutput Parameter NA ProcessUsageCharges Activity", "source": "VODKB-200723-160306.pdf"}
{"id": "343bfa5b4ac0-0", "text": "2697\n Error Handling Primary Catch-all Error Handler\nLogs to Error Log", "source": "VODKB-200723-160306.pdf"}
{"id": "1cc78c6cbcd5-0", "text": "2698\nEvent Loader Development\n610866 - Processing the RCS and MMS Files\n610866 - Processing the RCS and MMS Files\nOverview\nNew Configs\nEvent Type Config\nAOM Config\nWatchDog Config\nSchedulerConfig Config\nIMIResponseHandler Activity\nString ProcessIMIResponseFile(String filePath, String delimiter , boolean hasHeader) Function\nValidateIMIResponse Data Transform\nIMIResponsePreProcessor Activity\nIMIResponsePayloadHandler Activity\nIMIResponseInvalidParameterRecords Job Scheduler\nCapture Response Context Attributes\nTest Cases\nOverview\nRCS and MMS Responses are now handled using Event Queue Processor and as part of Event Loader case to capture the responses from \nincoming response files and create entries in IH in a standardized way.\nNew Configs\nEvent Type Config\nAOM ConfigIMIResponse SUBMITTED true 0 false false true false\nIMIResponse CLICKED true 0 false false true false\nIMIResponse RESPONSE true 0 false false true false\nIMIResponse CLOSED true 0 false false true falseEventType SubEventType\n ProcessFla\ng RampUpValue CIS ProcessEvent\n CaptureResponse StoreRawEvent \nLoaderEntityList Event < E X I S T I N G _ C O N F I G>,IMIResponse\nFileAttributes IMIResponse \"\n{\"CompressionType\":\"zip\",\"Encrypted\":true,\"InputFilePatter\nn\":\"AOM_IMI_.*.zip.gpg\",\"Mandatory\":false,\"HasChecksum\n\":false,\"HasHeader\":true,\"Delimiter\":\"|\",\"LargeFile\":true}\"ConfigType ConfigName ConfigValue", "source": "VODKB-200723-160306.pdf"}
{"id": "afd05e4e8715-0", "text": "2699\nWatchDog Config\nSchedulerConfig ConfigCaseId IMIResponseInvalidParameterRe\ncordsWatchDog \nCaseStatus IMIResponseInvalidParameterRe\ncordsWatchDog \nSkipCaseFinaliseEmail IMIResponseInvalidParameterRe\ncordsWatchDogTRUE\nIMIResponseI\nnvalidParamet\nerRecordsVFUK-FW-\nAOMFW-\nData-\nAOMError IdentifyInva\nlidParamet\nerRecordsError Identify list of Error \nRecords when a \nparticular event in the \nEvent Framework fails \ndue to invalid \nparameter mapping \nevery hour\"\n{\"\"IntervalPeriod\"\":\"\"\n1\"\",\"\"IntervalType\"\":\n\"\"hours\"\",\"\"ErrorCod\nes\"\":\"\"\"\"1252\"\",\"\"12\n54\"\",\"\"1255\"\",\"\"1256\n\"\",\"\"1257\"\"\"\"}\"true CSV Name ClassNam\neS\nQ\nL\nR\nul\neReportDefi\nnitionSever\nityDescription DynamicParamete\nrsInclu\ndeA\nsAtt\nach\nmen\ntAttac\nhme\nntTy\npeBi\nte\nAc\ntiv\nityBi\nte\nCl\nas\nsBit\neP\nar\nam\nete\nrs\n CaseIgni\ntor{\"CaseSubType\":\"IMIResp\nonseInvalidParameterRec\nords\"}VFUK-FW-AOMFW-Work-\nWatchDog0 0 0/1 ? * * *false WatchDogpyGUID Activity\nNameActivityParameters ClassName CronExpress\nionEnabled Type\nProcesses the RCS & MMS Response records in the task_status table. It validates if the file hasn\u2019t been previously loaded.\nApplies To VFUK-FW-AOMFW-Data-TaskStatus\nRuleset AOMFW\nInput Parameter N/A", "source": "VODKB-200723-160306.pdf"}
{"id": "afd05e4e8715-1", "text": "Ruleset AOMFW\nInput Parameter N/A\nOutput Parameter N/A\nError Handling Primary Catch-all Error Handler\nLog to Error Log\nConnect Point IMIResponseHandler activity will be added into existing ProcessQueueItem activity in VFUK-FW-AOMFW-\nData-TaskStatus classIMIResponseHandler Activity", "source": "VODKB-200723-160306.pdf"}
{"id": "7c11eab4f9ee-0", "text": "2700\nValidation: \nEnsure mandatory parameters are met based on Outcome and Table below. \nEnsure Outcome Date is <= Current Time \nEnsure Relative LOVs are Validated apart from outcomes this will be managed by EventTypeConfig\nRelative Validation Errors should not be passed to EventQueueProcessor and a relative Watchdog should highlight these events\nFormatting: Processes the response files for RCS & MMS Response event by reading file in filePath and it will ignore 1st record based on hasHeader. \nFor each record it will call IMIResponsePreProcessor for creating a record in Event_Status table.\nParamete\nrsfilePath The full path of the Event file\n delimiter Delimiter used in the Event file\n hasHeader Does the Event file have a header?\nReturns Duration of the process as String\nThrows RuntimeException - Error in ProcessRCSResponseFile while reading the file\nConnect \nPointProcessIMIResponseFile function will be called from IMIResponseHandler activity aboveString ProcessIMIResponseFile(String filePath, String delimiter, boolean hasHeader) \nFunction\nChecks mandatory fields in the RCS & MMS Response file\nApplies To VFUK-FW-AOMFW-Work\nRuleset AOMFW\nInput Parameter N/A\nOutput Parameter N/A\nMandatory Fields INTERACTIONID\nSUBSCRIPTIONID\nTREATMENTNAME\nCHANNEL\nOUTCOMEDATE\nOUTCOME\nMESSAGEID\nIf OUTCOME = CLICKED, then check\nPOSTBACKDATA\nPOSTBACKTYPE\nACTIONTYPE\nIf OUTCOME = RESPONSE, then check\nPOSTBACKDATA\nPOSTBACKTYPE\nConnect Point ValidateIMIResponse data transform will be invoked from IMIResponsePreProcessor activity belowValidateIMIResponse Data Transform", "source": "VODKB-200723-160306.pdf"}
{"id": "c7caff6adbde-0", "text": "2701\nFormat File into Relative JSON payload required for processing into Event Queue Processor\nINTERACTIONID String AOM Interaction \nReference for the \nInitial Outgoing \nMessage Sent - \nthis is to be \ntreated as the \nConversation \nIdentifier within \nAOM \n \nTo be taken from \nIncoming \nCampaign File \nfrom AOM \nSUBSCRIPTIONID String AOM Customer \nReference Id to \nidentify the \ncustomer in \nrelation to the \nInteraction \n \nTo be taken from \nIncoming \nCampaign File \nfrom AOM \nTREATMENTNAME String AOM Proposition \nName \n \nTo be taken from \nIncoming \nCampaign File \nfrom AOM \nCHANNEL String Channel Message \nwas Sent Via \nOUTCOMEDATE DateTime (IS\nO format)Date Time in \nwhich the \nOutcome was \ndone 2021-03-\n29T00:46:04.117Z\nOUTCOME String \nMESSAGEID String Message \nReference to allow \nus to understand Split String based on ~ to create \nSequence Number using second \nstring as Sequence Number ~\n FieldName Type Description Formatting Requirements Example", "source": "VODKB-200723-160306.pdf"}
{"id": "22d1f5aefed5-0", "text": "2702\nEvents should be passed with\nPrimary Context - IMIResponse\nSecondary Context - \nIdentifier: SubscriptionId the message is \nsent If the Sequence Number is NULL \ndefault it to 1 and will act as initial \nmeeting \nPOSTBACKDATA String Action or \nSuggestion \nPostback Data or \nFree Text Data \nResponse If POSTBACKTYPE is \"Action\"\nSplit String based on ~ to create \nPostback Id using second string as \nPostback Id\nIf the Postback Id is NULL then Error \nRecord Saying Invalid Parameter if \n3rd String Present Pass as \nActionDetail \nIf you get more than 3 Strings throw \nerror Saying Invalid Parameter \nNULLIFY POSTBACKDATA\n \nIf POSTBACKTYPE is \"FreeText\" \n Leave As is.~\n~\n \nPOSTBACKTYPE String Type of Postback \nLOV: \nAction\nFreeText \nACTIONTYPE String If POSTBACK Type is Action then \nWhat type of Action Taken: \nOpenURL \nDiallerAction \nProcesses the payload and set the Work.TextValueGroup data for Capture Response Event handling, please Refer Context Mapping . Will \nprocess the inputs and do below validations before creating a Event_Status record with metadata = { \"Delimiter\":\"json\"}\nIdentify Where EventTimestamp is <= Current Time\nSub Event Type Not Matched\nFormatting Requirements\nApplies To VFUK-FW-AOMFW-Data-TaskStatus\nRuleset AOMFW\nInput Parameter\n Payload\nDelimiter\nOutput Parameter N/AIMIResponsePreProcessor Activity", "source": "VODKB-200723-160306.pdf"}
{"id": "6b9df788f0be-0", "text": "2703\n Job scheduler is removed because this is driven by SchedulerConfig data type and added a config to SchedulerConfig above.\nCapture Response Context AttributesError Handling Primary Catch-all Error Handler\nLog to Error Log\nConnect Point IMIResponsePreProcessor activity will be invoked from ProcessIMIResponseFile function above\nSets SourceIdType, SkipLogic and EventTimestamp\nApplies To VFUK-FW-AOMFW-Data-EventStatus\nRuleset AOMFW\nInput Parameter N/A\nOutput Parameter N/A\nError Handling N/A\nConnect Point IMIResponsePayloadHandler activity will be called from existing PayloadHandlerRouter activity in VFUK-FW-\nAOMFW-Data-EventStatus classIMIResponsePayloadHandler Activity\nRuns a Watchdog case with subtype IMIResponseInvalidParameterRecords every 1 hour\nRuleset AOMFW\nAssociated with node \ntypesBackgroundProcessing\nSchedule Multiple times a day\nFrequency Every 1 hour\nClass VFUK-FW-AOMFW-Work-WatchDog\nActivity CaseIgnitorIMIResponseInvalidParameterRecords Job Scheduler\nInteractionId INTERACTION_ID \nPropositionName TREATMENT_NAME \nChannel CHANNEL \nEventTimestamp Mapped from OUTCOMEDATE \nSubEventType Mapped from OUTCOME \nMessageSequenceNumber Mapped from SEQUENCE_NO\nPostbackId Mapped from POSTBACKDATA - PostbackId Calculated Above Subscription.Context Mapping", "source": "VODKB-200723-160306.pdf"}
{"id": "a62490726a5b-0", "text": "2704\nTest Cases\nhttps://docs.google.com/spreadsheets/d/17ic-E167YipyDtGTPPd_mgzEAakLC3FZmTBQ2WioAlQ/edit#gid=1740030592 - \n MessageText Mapped from POSTBACKDATA \nPostbackType Mapped from POSTBACKTYPE \nActionType Mapped from ACTIONTYPE \nActionDetail Mapped from POSTBACKDATA - ActionDetail Calculated Above \nEventType \u201cIMIResponse\u201d\nConnect your\nGoogle account", "source": "VODKB-200723-160306.pdf"}
{"id": "a863b9a2e1e9-0", "text": "2705\nMEF - Digital Enriched Data\nLoader Case Changes\nAOM Config\nAdoptXMLFile Function\nProcessMEF Flow\nProcessMEF Activity\nUpdate InitialiseLoader Activity\nUpdate InspectDropZone Activity\nSequences\nConnect SQL\nPurge Config \nIntegration Class Structure\nVFUK-FW -AOMFW -Int-MEF-Root\nVFUK-FW -AOMFW -Int-MEF-List\nVFUK-FW -AOMFW -Int-MEF-Row\nVFUK-FW -AOMFW -Int-MEF-Element\nData Class Structure for data to store into Datasets\nList of Cassandra Datasets and their keys\nVFUK-FW -AOMFW -Data-BundleContent\nVFUK-FW -AOMFW -Data-ProductContent\nVFUK-FW -AOMFW -Data-BundleMerchandising\nVFUK-FW -AOMFW -Data-ProductMerchandising\nVFUK-FW -AOMFW -Data-ProductGroupDetails\nVFUK-FW -AOMFW -Data-ProductGroupMemberDetails\nLoader Case Changes\nAOM Config\nCaseId MEFLoader \nCaseStatus MEFLoader Completed\nLoaderEntityList MEF MEFContent, MEFMerchandising\nLoaderFileAttributes MEF { \"LoadType\": \"full\",\"InputFilePattern\":\"*.*.zip\", \n\"CompressionType\":\"zip\", \"Encrypted\": false, \"Mandatory\": \nfalse, \"HasChecksum\": false, \"HasHeader\": false, \n\"S3TransferMode\": \"move\" } \nFileAttributes MEFContent {\"InputFilePattern\":\"MEF_CONTENT_Prod.*.xml\"} \nFileAttributes MEFMerchandising {\"InputFilePattern\":\"MEF_MERCHANDISING_PROD_ME\nF.*.xml\"}", "source": "VODKB-200723-160306.pdf"}
{"id": "a863b9a2e1e9-1", "text": "F.*.xml\"}\nLoaderCheckPoints MEF \nLoaderIncomingPath MEF ConfigType ConfigName ConfigValue", "source": "VODKB-200723-160306.pdf"}
{"id": "9c327d796d5d-0", "text": "2706\n \nProperty\nCreate IsCaseSubTypeMEF - Boolean property\nHolds the information about whether the case sub type is MEF or not\nWhen\nCreate IsProcessMEFRunnable when rule\nReturns true if Loader case sub type is equal to \u201cMEF\u201dLoaderIncomingS3Path MEF \nLoaderLoopLimit MEF \nPauseCase MEFLoader false\nSkipCaseFinaliseEmail MEFLoader true\nAdopts XML file data into a Clipboard Property\nLibrary AOMUtilities\nRuleset AOMFW\nInput Parameters XMLFilePath - String\nproperty - The ClipboardProperty in which the XML will be adoptedAdoptXMLFile Function\nRuns if IsProcessMEFRunnable when rule returns true.\nCalls PrepareMEF activity to parse the data and load into Cassandra datasets.\nClass VFUK-FW-AOMFW-Work-Loader\nRuleset AOMFWProcessMEF Flow\nThis activity iterates through the MEF entities, do parse XML and write data into appropriate datasets\nClass VFUK-FW-AOMFW-Work-Loader\nRuleset AOMFW\nLogic For each Loader Entity Type (in this case, MEFContent and MEFMerchandising),\nMEFContent Iteration:\nCalls AdoptXMLFile function to adopt XML file into a XML property\nDo Parse XML to create a MEFContent ClipboardPage from XML property populated by the function\nGet next value for MEFContent sequence and assign it to VersionId\nBy using MEFContent page data and VersionId write the data into following datasets\nBundleContent\nProductContentProcessMEF Activity", "source": "VODKB-200723-160306.pdf"}
{"id": "f48ab38dd1ac-0", "text": "2707\nUpdate InitialiseLoader Activity\nAdd .IsCaseSubTypeMEF property to set it in Property-Set step\nUpdate InspectDropZone Activity\nCheck InputFilePattern is empty or not in Loader file attribute level.\nGet zip file by matching the InputFilePattern in S3 folder.\nMove zip file from S3 to Incoming Path.\nDecompress the zip file.\nCall InspectEntityFiles activity and prepare InputFiles with matching pattern.\nAppend InputFiles to LoaderEntities.\nAfter processing move all extracted files to archival path.\nGo to ProcessMEF Flow and run ProcessMEF activity.\nSequences\nCreate below sequences in database\nConnect SQL\nCreate a Connect SQL rule to get next sequence value from above sequences and store the values in VersionId property.MEFMerchandising Iteration:\nCalls AdoptXMLFile function to adopt XML file into a XML property\nDo Parse XML to create a MEFMerchandising ClipboardPage from XML property populated by the \nfunction\nGet next value for MEFMerchandising sequence and assign it to VersionId\nBy using MEFMerchandising page data and VersionId write the data into following datasets\nBundleMerchandising\nProductMerchandising\nProductGroupDetails\nProductGroupMemberDetails\nMEFContent Name - MEFContent\nMinValue - 1\nMaxValue - 9223372036854775807\nIncrement - 1\nCycle - false\nMEFMerchandising Name - MEFMerchandising\nMinValue - 1\nMaxValue - 9223372036854775807\nIncrement - 1\nCycle - falseSequence Name Details", "source": "VODKB-200723-160306.pdf"}
{"id": "6787e37bb54b-0", "text": "2708\nPurge Config \nAdd records to AOMConfig for MEFContent and MEFMerchandising and provide a value for deleting the records by using VersionId key.\n<>\nIntegration Class Structure\nFrom below wizard, create class structure for the given XSD.\nConfigure > Integration > Connectors > Connectors and Metadata Wizard\nCheck the names of Parse XML, XML Stream etc rules created and rename with appropriate names.\nCreate VFUK-FW-AOMFW-Int-MEF class\nVFUK-FW-AOMFW-Int-MEF-Root\nXML Stream and Parse XML rules should be created under this class\nVFUK-FW-AOMFW-Int-MEF-List\nVFUK-FW-AOMFW-Int-MEF-Row\nversion Text\nlist Page List (VFUK-FW-AOMFW-Int-MEF-List)PropertyName Type\nname Text\nrow Page List (VFUK-FW-AOMFW-Int-MEF-Row)PropertyName Type\nelement Page List (VFUK-FW-AOMFW-Int-MEF-Element)PropertyName Type", "source": "VODKB-200723-160306.pdf"}
{"id": "a800dbd68d9e-0", "text": "2709\nVFUK-FW-AOMFW-Int-MEF-Element\nData Class Structure for data to store into Datasets\nList of Cassandra Datasets and their keys\nVFUK-FW-AOMFW-Data-BundleContent\nCreate VFUK-FW-AOMFW-Data-BundleContent class\nCreate Dataset - BundleContent\nKeys -VersionId, ProductId\nCreate below properties in this classname Text\nValue TextPropertyName Type\nBundleContent VersionId\nProductId\nProductContent VersionId\nProductId\nBundleMerchandising VersionId\nProductId\nProductMerchandising VersionId\nProductId\nProductGroupDetails VersionId\nGroupName\nProductGroupMemberDetails VersionId\nProductIdDataset Name Keys\nVersionId Integer NA\nProductId Text wcm:element name=\"bundleId\" \nDisplayName Text wcm:element name=\"displayName\" \nDescription Text wcm:element name=\"desc\" \nFullDescription Text wcm:element name=\"fullDetails\" \nMobileDescription Text wcm:element name=\"descMobile\" \nFullMobileDescription Text wcm:element name=\"fullDetailsMobile\" PropertyName Type Mapped From", "source": "VODKB-200723-160306.pdf"}
{"id": "0ebd82f9287f-0", "text": "2710\nXML Structure for BundleContent\n\n113571 \nUnlimited with Entertainment \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n ImageURLThumbnailFront Text wcm:element \nname=\"imageURLs.thumbs.front \nImageURLThumbnailLeft Text wcm:element \nname=\"imageURLs.thumbs.left \nImageURLThumbnailRight Text wcm:element \nname=\"imageURLs.thumbs.right \nImageURLThumbnailSide Text wcm:element", "source": "VODKB-200723-160306.pdf"}
{"id": "0ebd82f9287f-1", "text": "name=\"imageURLs.thumbs.right \nImageURLThumbnailSide Text wcm:element \nname=\"imageURLs.thumbs.side \nImageURLThumbnailBack Text wcm:element \nname=\"imageURLs.thumbs.back \nImageURLFullFront (Not in XML) Text imageURLs.full.front \nImageURLFullLeft Text imageURLs.full.left \nImageURLFullRight Text imageURLs.full.right \nImageURLFullSide Text imageURLs.full.side \nImageURLFullBack Text imageURLs.full.back \nImageURLFullHero (Not in XML) Text imageURLs.full.hero", "source": "VODKB-200723-160306.pdf"}
{"id": "265acafe43f9-0", "text": "2711\nVFUK-FW-AOMFW-Data-ProductContent\nCreate VFUK-FW-AOMFW-Data-ProductContent class\nCreate Dataset - ProductContent\nKeys -VersionId, ProductId\nCreate below properties in this class\nVersionId Integer NA\nProductId Text wcm:element name=\"productId\"\nDisplayName Text wcm:element name=\"displayName\" \nDescription Text wcm:element name=\"preDesc\" \nFullDescription Text wcm:element name=\"postDesc\" \nMobileDescription Text wcm:element name=\"preDescMobile\" \nFullMobileDescrip\ntion Text wcm:element name=\"postDescMobile\" \nImageURLGroup PageGroup (VFUK-FW-AOMFW-\nData-MEF-ImageURL)wcm:element name=\"imageURLs.thumbs\" and or \nwcm:element name=\"imageURLs.full\" \n Front Text wcm:element name=\"imageURLs.thumbs.front || \nimageURLs.full.front\" \n Left Text wcm:element name=\"imageURLs.thumbs.left || \nimageURLs.full.left\" \n Right Text wcm:element name=\"imageURLs.thumbs.right || \nimageURLs.full.right\" \n Side Text wcm:element name=\"imageURLs.thumbs.side || \nimageURLs.full.side\" \n Back Text wcm:element name=\"imageURLS.thumbs.back || \nimageURLs.full.back\" \n Hero Text wcm:element name=\"imageURLS.full.hero\" \nGridImageURL Text wcm:element name=\"imageURLS.grid\" \nSpecificationList PageList (VFUK-FW-AOMFW-\nData-MEF-SpecificationList)For each: \nwcm:element name=\"specificationGroups.group.", "source": "VODKB-200723-160306.pdf"}
{"id": "265acafe43f9-1", "text": "wcm:element name=\"specificationGroups.group.\n.groupName\" \nRemove Spaces from Name \n GroupName Text wcm:element name=\"specificationGroups.group.\n.groupName \nKeep Spaces in Name \n Specifications ValueList For each: \nwcm:element PropertyName PropertyName (Child \nlevel)Type Mapped From/Description", "source": "VODKB-200723-160306.pdf"}
{"id": "f44f4426352a-0", "text": "2712\nname=\"specificationGroups.group.X.specifications.valu\ne.X\" + \" \" + \nwcm:element \nname=\"specificationGroups.group.X.specifications.valu\neUOM.X\" \nWhere: wcm:element \nname=\"specificationGroups.group.X.specifications.hide\nInList.X is true - do not add specification to value list \n \nExample: specification value Body is not added to \nthe value list \nitem \nBody \n1 \nno \nno \nText \n \n \n \ntrue ", "source": "VODKB-200723-160306.pdf"}
{"id": "f44f4426352a-1", "text": "InList.1\">true \n Example: 5000 mAh output \n5000 ", "source": "VODKB-200723-160306.pdf"}
{"id": "81fd69375a0e-0", "text": "2713\nXML Structure for ProductContent\n\n210722 \nApple iPhone 12 Pro 128GB (Like New) Graphite \niPhone 12 Pro is a beautiful leap forward with superfast 5G, A14 Bionic chip and a pro camera system for \nnext-level low-light photography. \n\n\n\n\n\n/images/desktop/Apple_iPhone_12_Pro_graphite-thumbs-front.png \n\n\n\n\n\n\n\n\n\n/images/desktop/Voxi_Apple_iPhone_12_Pro_graphite-full-product-front-\n600.png ", "source": "VODKB-200723-160306.pdf"}
{"id": "81fd69375a0e-1", "text": "600.png \n/images/desktop/Voxi_Apple_iPhone_12_Pro_graphite-full-product-front-\n600.png \n\n\n\n\n\n\n\n\n\n/images/desktop/Voxi_Apple_iPhone_12_Pro_graphite-grid-product-front.png \n\n\n\n\n\n\n\n\nBattery mAh \n Only add Space if valueUOM has value.", "source": "VODKB-200723-160306.pdf"}
{"id": "38c21447f65e-0", "text": "2714\n1 \nno \nBattery \nNon-removable \n1 \nno \nNo \nText \n\n\n\n\nBattery \nFast battery charging \n2 ", "source": "VODKB-200723-160306.pdf"}
{"id": "38c21447f65e-1", "text": "no \nNo \nText \n\n\n\n\nBattery \nQi wireless charging \n3 \nno \nNo \nText \n\n\n", "source": "VODKB-200723-160306.pdf"}
{"id": "38c21447f65e-2", "text": "\n\nBattery Life \n2 \nno \nBody \n3 \nno \nitem \nBody \n1 \nno \nno \nText \n\n", "source": "VODKB-200723-160306.pdf"}
{"id": "2de838bcfd16-0", "text": "\n\n\ntrue \nBody \nCeramic Shield front, Textured matt glass back and stainless \nsteel design ", "source": "VODKB-200723-160306.pdf"}
{"id": "f4a32df9eeea-0", "text": "2715\n2 \nno \nNo \nText \n\n\n