id
stringlengths 14
14
| text
stringlengths 2
2.42k
| source
stringclasses 1
value |
|---|---|---|
4178e65c09e3-0 | 4034
Post Processing (TBD)
TBD
RunSimulation activity calls the pxSimulationLoadProgress activity which loads simulation progress in the Data-Decision-SimulationProgress
page.
Applies To VFUK-FW-AOMFW-Work
Ruleset TBD
Input
Parameter
sSimulaitonID
Output
Parameter
sN/A
Error
HandlingPrimary Catch-all Error Handler: Catches all the unhandled Exceptions or Errors in the activity | VODKB-200723-160306.pdf |
cb1d742b448a-0 | 4035
Application Versions
Overview
Releases
AOMFW
AOM
Artefacts to deploy to switch any application version to Live
914098: Designing the process to support feature-based releases
Deployment to make an Application Version Live
VF Confluence LinksExpand all Collapse all | VODKB-200723-160306.pdf |
ad44ec376359-0 | 4036
Overview
Application V ersioning
System Architecture
Example Flow
VADR.Administrators ( Trunk Application V ersion/ Live Application V ersion)
VADR.Administrators.Charlie ( PostMVP+ Apple Lovers Application V ersion )
PM Tool
Application Versioning
Application versioning is a way to differentiate current and past application configurations. Rule resolution can look through all the minor and patch versions for the current major ruleset.
Application components include the application ruleset stack — which contains the rules and data types used by the application. To version an application, you must version the application's rulesets.
The below diagram explains the low-level flow of how the application version works with all the rules involved in AOM context
An Operator accessing the pega application in any form like Mashup/API/Dev Studio etc would be mapped to an Access Group which authorizes access to the right rules to get the expected
result/response.
An Access group would be mapped to a specific Application rule version which authorizes a version of the code base to be executed for all the operators mapped to this Access Group
Authentication Profile is used by the Connector rules in Pega to invoke an External API, this rule encapsulates the user credentials for the source system to authenticate the user and respond
System Architecture
The below diagram talks about how the different systems using AOM communicate with the application versioning in the context.
VADR Application can integrate with multiple application versions in parallel from AOM at any given point in time ( but vice-versa is not true) using multiple operators and access-group discussed in
the above section
TIL/Tealium/Microsite can integrate with only one application version from the multiple versions available in AOM at any given point in time, due to technical limitations in the source systems | VODKB-200723-160306.pdf |
56453fd8f2a0-0 | 4037
Example Flow
Below is the example flow of user/operator using different application versions and how the UI changes can be displayed accordingly to the access group
dilek.basaran2 is the operator used in the below example
dilek.basaran mapped to VADR.Administrators which is trunk code base R3.05 application version
dilek.basaran2 mapped to VADR.Administrators.Charline which is R3.05 + PostMVP+ Apple Lovers application version
VADR.Administrators ( Trunk Application Version/ Live Application Version)
1. Below is the screenshot of the dilek.basaran Operator mapped to VADR.Administrators which in turn is mapped to the VADR:01.01.01 application version
2. The same use is logging Upgrade Journey from VADR using Mashup and pega prompts for credentials
Note: This is not applicable for Call Centre agents as SSO is in place in the PROD environment hence the user will not be prompted for credentials again as they are logged into
Halo( Siebel) already. | VODKB-200723-160306.pdf |
b82f70545871-0 | 4038
3. As displayed below, we can see the Upgrade Case launched and recommendations are displayed.
VFT together icon highlighted in the screenshot below is displayed, which is applicable to the VADR:01.01.01 application version
VADR.Administrators.Charlie ( PostMVP+ Apple Lovers Application Version )
1. Below is the screenshot of the dilek.basaran2 Operator mapped to VADR.Administrators.Charlie which in turn is mapped to the VADR:01.04.01 application version ( PostMVP+ Apple Lovers
Application Version ) | VODKB-200723-160306.pdf |
5f569400c35f-0 | 4039
2. The same use is logging Upgrade Journey from VADR using Mashup and pega prompts for credentials
Note: This is not applicable for Call Centre agents as SSO is in place in the PROD environment hence the user will not be prompted for credentials again as they are logged into
Halo( Siebel) already.
3. As displayed below, we can see the Upgrade Case launched and recommendations are displayed.
The new VFT together icon highlighted in the screenshot below is displayed, which is applicable to the VADR:01.04.01 application version | VODKB-200723-160306.pdf |
0140d158e86f-0 | 4040
PM Tool
Business users log in to their respective application versions to create/update the catalogue version.
PMTool also supports pushing the version into the respective catalogue version into the AOM application version.
The below diagram explains one-to-one mapping between the catalogue version and the AOM application version. | VODKB-200723-160306.pdf |
fd1415ba072b-0 | 4041 | VODKB-200723-160306.pdf |
6ba766baffbd-0 | 4042
Releases
Releases & App Version Mapping
R3.5
R3.6
R3.7
R4.1 And R4.2
R4.3
R4.4
R4.5
R4.6
Build Package Propagation
The application version build is the same regular build process where the required rules will be packaged and deployed into the target
environment.
Access to the rules on the target is controlled by the access group specific to the application version and is available to a specific user only
In, PROD a feature which is part of the application version is available to the super agent user only.
Once, the business users are happy with the feature then, a new build package needs to be cut from Dev which includes access group
changes, API Operators etc to point to the relevant application version so that all the agents are not moved to this application version in
context | VODKB-200723-160306.pdf |
60036c3e6d4a-0 | 4043
Releases & App Version Mapping
R3.5 R3.5 Core
ReleaseVADR:
01:01:01AOM:
01:03:01
AOMFW:
01:03:01NA(Live
)Once this application version code is deployed, it will be available to all users
which means application code will be Live by default
Apple
Lovers
Renegotiatio
n
Commission
ing VADR:
01:04:01AOM:
01:04:01
AOMFW:
01:04:01Charlie Deployed as Feature release. Needs further deployment once business clears
FUT testing cycle on PROD to make it Live ( available to all users)
R3.6 R3.6 Core
ReleaseVADR:
01:05:01AOM:
01:05:01
AOMFW:
01:05:01NA(Live
)Once this application version code is deployed, it will be available to all users
which means application code will be Live by default
Mobile
Broadband VADR:
01:06:01AOM:
01:06:01
AOMFW:
01:06:01Alpha Deployed as Feature release. Needs further deployment once business clears
FUT testing cycle on PROD to make it Live ( available to all users)
R3.7 R3.7 Core
ReleaseNone AOM:
01:07:01
AOMFW:
01:07:01NA(Live
)Once this application version code is deployed, it will be available to all users
which means application code will be Live by default
No Features based application version requested by Business | VODKB-200723-160306.pdf |
60036c3e6d4a-1 | which means application code will be Live by default
No Features based application version requested by Business
R4.1 R4.1 Core
ReleaseVADR:
01:08:01AOM:
01:08:01
AOMFW:
01:08:01NA(Live
)Once this application version code is deployed, it will be available to all users
which means application code will be Live by default
5G Ultra VADR:
01:010:0
1None Beta Deployed as Feature release. Needs further deployment once business clears
FUT testing cycle on PROD to make it Live ( available to all users)
R4.2 R4.2 Core
ReleaseVADR:
01:08:01AOM:
01:08:01
AOMFW:
01:08:01NA(Live
)There is no new application for R4.2 and developed in existing version 01:08:01Relea
seFunctionali
tiesVADR
App
VersionAOM App
VersionAccess
GroupComments | VODKB-200723-160306.pdf |
2bdddb87d812-0 | 4044
No Features based application version requested by Business
SOHOSOHO VADR:
01:08:01AOM:
01:08:01
AOMFW:
01:08:01NA(Live
)There is no new application for SOHO and developed in existing version
01:08:01
No Features based application version requested by Business
R4.3 R4.3 Core
ReleaseVADR:
01:09:01AOM:
01:09:01
AOMFW:
01:09:01NA(Live
)Once this application version code is deployed, it will be available to all users
which means application code will be Live by default
No Features based application version requested by Business
R4.4 R4.4 Core
ReleaseVADR:
01:11:01AOM:
01:11:01
AOMFW:
01:11:01NA(Live
)Once this application version code is deployed, it will be available to all users
which means application code will be Live by default
FUT
ChangesVADR:
01:012:0
1AOM:
01:12:01
AOMFW:
01:12:01Alpha Deployed as Feature release for Alpha users. Needs further deployment once
business clears FUT testing cycle on PROD to make it Live ( available to all
users)
Retail VADR:
01:015:0
1AOM:
01:15:01
AOMFW:
01:15:01Charlie Deployed as Feature release for Charlie users. Needs further deployment once
business clears FUT testing cycle on PROD to make it Live ( available to all
users) | VODKB-200723-160306.pdf |
2bdddb87d812-1 | business clears FUT testing cycle on PROD to make it Live ( available to all
users)
R4.5 R4.5 Core
ReleaseVADR:
01:13:01AOM:
01:13:01
AOMFW:
01:13:01NA(Live
)Once this application version code is deployed, it will be available to all users
which means application code will be Live by default
Retail VADR:
01:015:0
1AOM:
01:15:01
AOMFW:
01:15:01Charlie Deployed as Feature release for Charlie users. Needs further deployment once
business clears FUT testing cycle on PROD to make it Live ( available to all
users)
R4.6 R4.6 Core
ReleaseVADR:
01:16:01AOM:
01:16:01
AOMFW:
01:16:01NA(Live
)Once this application version code is deployed, it will be available to all users
which means application code will be Live by default
No Features based application version requested by Business
Core/Default Release Application VersionLegends | VODKB-200723-160306.pdf |
6f1541112e6a-0 | 4045
Feature based application Version | VODKB-200723-160306.pdf |
6d72d9d83557-0 | 4046
R3.5
List of Application versions as part of R3.5 release
For more details on below access groups, refer to Access Groups page.
01.03.01
01.04.0101.03.01 R3.05
01.04.01 PostMVP, Apple LoversApplication Versions Features/Releases
VADR 01.03.01VADR:AssistedAgents NA Access Group for Call Centre
agents
VADR:Administrators NA Access Group for Application
developers
AOM 01.03.01AOM:API VFUK.VADR
AOM:API VFUK.TIL
AOM:Mailjet [email protected]
AOM:RulesAdmins NA Access Group for Application
developers
AOMFW 01.03.01AOMFW:Tealium VFUK.Tealium
AOMFW:MSUnauthenticated Microsite
AOMFW:AssistedAgents VFUK.Assisted.Agent
AOMFW:Administrators NA Access Group for Application
developers
AOMFW:MarketManager NA Access Group for Logic
developers
AOMFW:PegaMarketManager NA Access Group for Logic
developersApplication Version Access Group Operator Notes
VADR 01.04.01VADR:AssistedAgents.Charlie NA Access Group for Call Centre
agentsApplication Version Access Group Operator Comments | VODKB-200723-160306.pdf |
e8f1f22ed428-0 | 4047
VADR:Administrators.Charlie NA Access Group for Application
developers
AOM 01.04.01AOM:API.Charlie VFUK.VADR.Charlie
AOM:API.Charlie VFUK.TIL.Charlie
AOM:Mailjet.Charlie [email protected]
AOM:RulesAdmins.Charlie NA Access Group for Application
developers
AOMFW 01.04.01AOMFW:Tealium.Charlie VFUK.Tealium.Charlie
AOMFW:MSUnauthenticated.Ch
arlieMicrosite
AOMFW:AssistedAgents.CharlieVFUK.Assisted.Agent.Charlie
AOMFW:Administrators.Charlie NA Access Group for Application
developers
AOMFW:MarketManager.CharlieNA Access Group for Logic
developers
AOMFW:PegaMarketManager.C
harlieNA Access Group for Logic
developers | VODKB-200723-160306.pdf |
af7aec1b8ead-0 | 4048
R3.6
List of Application versions as part of R3.6 release
For more details on below access groups, refer to Access Groups page.
01.05.01
01.06.0101.05.01 R3.06
01.06.01 MBBApplication Versions Features/Releases
VADR 01.05.01VADR:AssistedAgents NA Access Group for Call Centre
agents
VADR:Administrators NA Access Group for Application
developers
AOM 01.05.01AOM:API VFUK.VADR
AOM:API VFUK.TIL
AOM:Mailjet [email protected]
AOM:RulesAdmins NA Access Group for Application
developers
AOMFW 01.05.01AOMFW:Tealium VFUK.Tealium
AOMFW:AssistedAgents VFUK.Assisted.Agent
AOMFW:Administrators NA Access Group for Application
developers
AOMFW:MarketManager NA Access Group for Logic
developers
AOMFW:PegaMarketManager NA Access Group for Logic
developersApplication Version Access Group Operator Notes
VADR 01.06.01VADR:AssistedAgents.Alpha NA Access Group for Call Centre
agentsApplication Version Access Group Operator Comments | VODKB-200723-160306.pdf |
48ec86e895b2-0 | 4049
VADR:Administrators.Alpha NA Access Group for Application
developers
AOM 01.06.01AOM:API.Alpha VFUK.VADR.Alpha
AOM:API.Alpha VFUK.TIL.Alpha
AOM:Mailjet.Alpha [email protected]
AOM:RulesAdmins.Alpha NA Access Group for Application
developers
AOMFW 01.06.01AOMFW:Tealium.Alpha VFUK.Tealium.Alpha
AOMFW:AssistedAgents.Alpha VFUK.Assisted.Agent.Alpha
AOMFW:Administrators.Alpha NA Access Group for Application
developers
AOMFW:MarketManager.Alpha NA Access Group for Logic
developers
AOMFW:PegaMarketManager.Al
phaNA Access Group for Logic
developers | VODKB-200723-160306.pdf |
7c7f8c46dd4b-0 | 4050
R3.7
List of Application versions as part of R3.7 release.
01.07.01
There are no changes in the VADR application so no new application version was created.01.07.01 R3.07Application Versions Features/Releases
AOM 01.07.01AOM:API VFUK.VADR
AOM:API VFUK.TIL
AOM:Mailjet [email protected]
AOM:RulesAdmins NA Access Group for Application
developers
AOMFW 01.07.01AOMFW:Tealium VFUK.Tealium
AOMFW:AssistedAgents VFUK.Assisted.Agent
AOMFW:Administrators NA Access Group for Application
developers
AOMFW:MarketManager NA Access Group for Logic
developers
AOMFW:PegaMarketManager NA Access Group for Logic
developers
AOMFW:MSUnauthenticated NA Access Group for microsite user
PegaNBAM:Agents NA Access Group for OOTB agentsApplication Version Access Group Operator Notes | VODKB-200723-160306.pdf |
03e6b9e8720d-0 | 4051
R4.1 And R4.2
List of Application versions as part of R4.1 and R4.2 release
01.08.01
01.08.01 R4.01 and R4.02
01.10.01 5G Ultra - Only for VADRApplication Versions Features/Releases
VADR 01.08.01VADR:AssistedAgents NA Access Group for Call Centre
agents
VADR:Administrators NA Access Group for Application
developers
AOM 01.08.01AOM:API VFUK.VADR
AOM:API VFUK.TIL
AOM:Mailjet [email protected]
AOM:RulesAdmins NA Access Group for Application
developers
AOMFW 01.08.01AOMFW:Tealium VFUK.Tealium
AOMFW:AssistedAgents VFUK.Assisted.Agent
AOMFW:Administrators NA Access Group for Application
developers
AOMFW:MarketManager NA Access Group for Logic
developers
AOMFW:PegaMarketManager NA Access Group for Logic
developers
AOMFW:MSUnauthenticated NA Access Group for microsite user
AOMFW:Simulation NA This is for simualtion users to run
simulation on previous code base
PegaNBAM:Agents NA Access Group for OOTB agentsApplication Version Access Group Operator Notes | VODKB-200723-160306.pdf |
d937aef752ae-0 | 4052
01.10.01
VADR 01.10.01VADR:AssistedAgents.Beta NA Access Group for Call Centre
agents
VADR:Administrators.Beta NA Access Group for Application
developersApplication Version Access Group Operator Notes | VODKB-200723-160306.pdf |
1a9a0f6350b3-0 | 4053
R4.3
List of Application versions as part of the R4.03 release
01.09.01
01.09.01 R4.03Application Versions Features/Releases
VADR 01.09.01VADR:AssistedAgents NA Access Group for Call Centre
agents
VADR:Administrators NA Access Group for Application
developers
AOM 01.09.01AOM:API VFUK.VADR
AOM:API VFUK.TIL
AOM:Mailjet [email protected]
AOM:RulesAdmins NA Access Group for Application
developers
AOMFW 01.09.01AOMFW:Tealium VFUK.Tealium
AOMFW:AssistedAgents VFUK.Assisted.Agent
AOMFW:Administrators NA Access Group for Application
developers
AOMFW:MarketManager NA Access Group for Logic
developers
AOMFW:PegaMarketManager NA Access Group for Logic
developers
AOMFW:MSUnauthenticated NA Access Group for microsite user
AOMFW:Simulation NA This is for simulation users to run
simulation on previous code base
PegaNBAM:Agents NA Access Group for OOTB agentsApplication Version Access Group Operator Notes | VODKB-200723-160306.pdf |
238c3a329966-0 | 4054
R4.4
List of Application versions as part of R4.4 release
01.11.0101.11.01 (v11) R4.04 Core
01.12.01 (v12) Feature - Upgrades backlog (FUT)
01.15.01 (v15) RetailApplication Versions Features/Releases
VADR 01.11.01VADR:AssistedAgents NA Access Group for Call Centre
agents
VADR:Administrators NA Access Group for Application
developers
VADR:API VADR.PMT Access Group for Pmtool API user
AOM 01.11.01AOM:API VFUK.VADR
AOM:API VFUK.TIL
AOM:Mailjet [email protected]
AOM:RulesAdmins NA Access Group for Application
developers
AOMFW 01.11.01AOMFW:Tealium VFUK.Tealium
AOMFW:AssistedAgents VFUK.Assisted.Agent
AOMFW:Administrators NA Access Group for Application
developers
AOMFW:MarketManager NA Access Group for Logic
developers
AOMFW:PegaMarketManager NA Access Group for Logic
developers
AOMFW:MSUnauthenticated NA Access Group for microsite user
AOMFW:Simulation NA This is for simulation users to run
simulation on previous code
base(V9)
PegaNBAM:Agents NA Access Group for OOTB agentsApplication Version Access Group Operator Notes | VODKB-200723-160306.pdf |
0b8c8356ae3f-0 | 4055
01.12.01
01.15.01
VADR 01.12.01VADR:AssistedAgents.Alpha NA Alpha Access Group for Call
Centre agents
VADR:Administrators.Alpha NA Alpha Access Group for
Application developers
VADR:API.Alpha VADR.PMT.Alpha Alpha Access Group for Pmtool
API user
AOM 01.12.01AOM:API.Alpha VFUK.VADR.Alpha
AOM:API.Alpha VFUK.TIL.Alpha
AOM:Mailjet.Alpha [email protected]
AOM:RulesAdmins.Alpha NA Alpha Access Group for
Application developers
AOMFW 01.12.01AOMFW:Tealium.Alpha VFUK.Tealium.Alpha
AOMFW:AssistedAgents.Alpha VFUK.Assisted.Agent.Alpha
AOMFW:Administrators.Alpha NA Alpha Access Group for
Application developers
AOMFW:MarketManager.Alpha NA Alpha Access Group for Logic
developers
AOMFW:PegaMarketManager.Al
phaNA Alpha Access Group for Logic
developersApplication Version Access Group Operator Notes
VADR 01.15.01VADR:AssistedAgents.Charle NA Charle Access Group for Call
Centre agents
VADR:Administrators.Charle NA Charle Access Group for
Application developers
VADR:API.Charlie VADR.PMT.Charlie Charlie Access Group for Pmtool
API user
AOM 01.15.01AOM:API.Charle VFUK.VADR.Charle
AOM:API.Charle VFUK.TIL.Charle
AOM:Mailjet.Charle [email protected] Application Version Access Group Operator Notes | VODKB-200723-160306.pdf |
954373ba1191-0 | 4056
AOM:RulesAdmins.Charle NA Charle Access Group for
Application developers
AOMFW 01.15.01AOMFW:Tealium.Charle VFUK.Tealium.Charle
AOMFW:AssistedAgents.Charle VFUK.Assisted.Agent.Charle
AOMFW:Administrators.Charle NA Charle Access Group for
Application developers
AOMFW:MarketManager.CharleNA Charle Access Group for Logic
developers
AOMFW:PegaMarketManager.C
harleNA Charle Access Group for Logic
developers | VODKB-200723-160306.pdf |
1403e4b7f58b-0 | 4057
R4.5
List of Application versions as part of R4.5 release
01.13.01
01.13.01 (v13) R4.05 Core
01.15.01 (v15) RetailApplication Versions Features/Releases
VADR 01.13.01VADR:AssistedAgents NA Access Group for Call Centre
agents
VADR:Administrators NA Access Group for Application
developers
VADR:API VADR.PMT Access Group for Pmtool API user
AOM 01.13.01AOM:API VFUK.VADR
AOM:API VFUK.TIL
AOM:Mailjet [email protected]
AOM:RulesAdmins NA Access Group for Application
developers
AOMFW 01.13.01AOMFW:Tealium VFUK.Tealium
AOMFW:AssistedAgents VFUK.Assisted.Agent
AOMFW:Administrators NA Access Group for Application
developers
AOMFW:MarketManager NA Access Group for Logic
developers
AOMFW:PegaMarketManager NA Access Group for Logic
developers
AOMFW:MSUnauthenticated NA Access Group for microsite user
AOMFW:Simulation NA This is for simulation users to run
simulation on previous code
base(V11)
PegaNBAM:Agents NA Access Group for OOTB agentsApplication Version Access Group Operator Notes | VODKB-200723-160306.pdf |
45ec17635ee6-0 | 4058
01.15.01
VADR 01.15.01VADR:AssistedAgents.Charle NA Charle Access Group for Call
Centre agents
VADR:Administrators.Charle NA Charle Access Group for
Application developers
VADR:API.Charlie VADR.PMT.Charlie Charlie Access Group for Pmtool
API user
AOM 01.15.01AOM:API.Charle VFUK.VADR.Charle
AOM:API.Charle VFUK.TIL.Charle
AOM:Mailjet.Charle [email protected]
AOM:RulesAdmins.Charle NA Charle Access Group for
Application developers
AOMFW 01.15.01AOMFW:Tealium.Charle VFUK.Tealium.Charle
AOMFW:AssistedAgents.Charle VFUK.Assisted.Agent.Charle
AOMFW:Administrators.Charle NA Charle Access Group for
Application developers
AOMFW:MarketManager.CharleNA Charle Access Group for Logic
developers
AOMFW:PegaMarketManager.C
harleNA Charle Access Group for Logic
developersApplication Version Access Group Operator Notes | VODKB-200723-160306.pdf |
6cc2bc6c8d3c-0 | 4059
R4.6
List of Application versions as part of R4.6 release
01.16.01
01.16.01 (v16) R4.06 CoreApplication Versions Features/Releases
VADR 01.16.01VADR:AssistedAgents NA Access Group for Call Centre
agents
VADR:Administrators NA Access Group for Application
developers
VADR:API VADR.PMT Access Group for Pmtool API user
AOM 01.16.01AOM:API VFUK.VADR
AOM:API VFUK.TIL
AOM:Mailjet [email protected]
AOM:RulesAdmins NA Access Group for Application
developers
AOMFW 01.16.01AOMFW:Tealium VFUK.Tealium
AOMFW:AssistedAgents VFUK.Assisted.Agent
AOMFW:Administrators NA Access Group for Application
developers
AOMFW:MarketManager NA Access Group for Logic
developers
AOMFW:PegaMarketManager NA Access Group for Logic
developers
AOMFW:MSUnauthenticated NA Access Group for microsite user
AOMFW:Simulation NA This is for simulation users to run
simulation on previous code
base(V13)
PegaNBAM:Agents NA Access Group for OOTB agentsApplication Version Access Group Operator Notes | VODKB-200723-160306.pdf |
59b08ae49aac-0 | 4060
AOMFW
[ AOMFW : 01-01-01 ] [ AOMFW : 01-02-01 ] [ AOMFW : 01-03-01 ]
Ruleset Name Ruleset Version
AOMFW-Local 01-01-01
AOMFW-Artifacts 01-01-24
AOMFW 01-01-16
AOMFW-Int 01-01-01
AOMFW-Testing 01-01-01
AOMFW-PM-Artifacts 01-01-01
AOMFW-PM-Campaigns 01-01-02
AOMFW-PM-Catalogue 01-01-01
AOMFW-BuildArtifacts 01-01-01
AOMFW-UI 01-01-06
VFUK 01-01-01
VFUKInt 01-01-01
AOMFW-Database 01-01-01AOMFW : 01-01-01
Ruleset Name Ruleset Version
AOMFW-Local 01-02-01
AOMFW-Artifacts 01-02-56
AOMFW-Database 01-02-09
AOMFW 01-02-19
AOMFW-Int 01-02-10
AOMFW-Analysis 01-02-02
AOMFW-Testing 01-02-01
AOMFW-Test-Cases 01-02-07
AOMFW-PM-Artifacts 01-02-03
AOMFW-PM-Campaigns 01-01-02AOMFW : 01-02-01 | VODKB-200723-160306.pdf |
7f9bd36435fe-0 | 4061
AOMFW-PM-Catalogue 01-01-01
AOMFW-BuildArtifacts 01-01-01
AOMFW-UI 01-02-04
VFUK 01-01-01
VFUKInt 01-01-01
Ruleset Name Ruleset Version
AOMFW-Local 01-03-01
AOMFW-Business-Artifacts 01-03-90
AOMFW-Artifacts 01-03-24
AOMFW-Database 01-03-23
AOMFW 01-03-26
AOMFW-Int 01-03-20
AOMFW-Analysis 01-03-01
AOMFW-Testing 01-03-02
AOMFW-Test-Cases 01-03-13
AOMFW-PM-Artifacts 01-03-01
AOMFW-PM-Campaigns 01-01-02
AOMFW-PM-Catalogue 01-01-01
AOMFW-BuildArtifacts 01-01-01
AOMFW-UI 01-03-09
AOMFW-Simulation 01-01-01
VFUK 01-01-01
VFUKInt 01-01-01AOMFW : 01-03-01 | VODKB-200723-160306.pdf |
ef3c22d320c7-0 | 4062
Creating a new AOMFW Application Version
[ Rulesets ] [ Application ] [ Custom Access Groups ] [ OOTB Access Groups ] [ Unauthenticated access group ] [ Operators ] [ Agents ] [
Job Schedulers ] [ System Runtime Context ] [ Requestors ]
Below are the changes required to be performed when a new application version is created.
Rulesets
Create new ruleset versions for all the applicable rulesets
Application
Update the AOMFW application rule by incrementing the Minor Version as in the screenshot below and save into the applicable ruleset.Ruleset Name Existing Ruleset Version New Ruleset Version
AOMFW-Local 01-03-01 01-04-01
AOMFW-Business-Artifacts 01-03-90 01-04-01
AOMFW-Artifacts 01-03-24 01-04-01
AOMFW-Database 01-03-23 01-04-01
AOMFW 01-03-26 01-04-01
AOMFW-Int 01-03-20 01-04-01
AOMFW-Analysis 01-03-01 01-04-01
AOMFW-Testing 01-03-02 01-04-01
AOMFW-Test-Cases 01-03-13 01-04-01
AOMFW-PM-Artifacts 01-03-01 01-04-01
AOMFW-UI 01-03-09 01-04-01
AOMFW-Simulation 01-01-01
VFUK 01-01-01
VFUKInt 01-01-01 | VODKB-200723-160306.pdf |
ef3c22d320c7-1 | VFUK 01-01-01
VFUKInt 01-01-01
AOMFW-PM-Campaigns 01-01-02
AOMFW-PM-Catalogue 01-01-01
AOMFW-BuildArtifacts 01-01-01 AOMFW : 01-03-01 | VODKB-200723-160306.pdf |
f99c894976f0-0 | 4063
Custom Access Groups
From the records explorer, Click on the Access Group Under Security ( Security → Access Group)
On the Access Group Rule, update the application version as shown below and save the application rule | VODKB-200723-160306.pdf |
9725c948b779-0 | 4064
Update all the below access groups to point to the new application version ( AOMFW: 01-04-01)
OOTB Access Groups
Unauthenticated access group
Operators
AOMFW:Administrators AOMFW:MarketAdmins AOMFW:Managers
AOMFW:AssistedAgents AOMFW:MarketAnalysts AOMFW:PegaMarketAdmins
AOMFW:Authors AOMFW:MarketingArchitects AOMFW:PegaMarketManager
AOMFW:CVMManager AOMFW:MarketingDeveloper AOMFW:Simulation
AOMFW:CVMOperations AOMFW:MarketingOperations AOMFW:Tealium
AOMFW:HealthCheck AOMFW:MarketInstall AOMFW:Upgrade
AOMFW:Users AOMFW:MarketManager
AOMFW:MSUnauthenticated AOMFW:Microsites Access Group Name
PegaNBAM:Agents PegaMKT:Unauthenticated Access Group Name
AOMFW:MSUnauthenticated Miscrosite is driven by Microsite operator which is now pointing to
this access group and we cannot have multiple operators for each
application version. We need to update the application version to test
the appropriate application.Access Group Name
VFUK.VADR This is for VADR application to invoke AOM API’s
VFUK.TIL This is for TIL system to invoke AOM API’s
VFUK.Tealium This is for Tealium eventsOperators | VODKB-200723-160306.pdf |
ce96ab3ca972-0 | 4065
Agents
Please verify, if the Agents created on the below ruleset are mapped to updated access groups. Please check on the security tab of the
Agent and Agent Schedule rule
Job Schedulers
Please verify, if all the job schedulers under AOMFW and AOMFW-Local rulesets are pointing to updated access groups pointing to the
latest application rule
System Runtime Context
Please verify, if the system runtime is pointing to the latest application rule.
Below is the navigation screenshot to System Runtime Context from the Pega Designer Studio (Configure → System → General →
System Runtime Context)
The application version should be AOMFW:01-04-01 as highlighted below in the System Runtime Context tabPegaMKT-Engine Pega Marketing OOTB Agents
AOMFW-Artifacts ProcessBatchJob OOTB Agent
AOMFW ResumeCaseFlow and GenerateExtract Custom AgentsRuleset Name Description | VODKB-200723-160306.pdf |
71fa552b787b-0 | 4066
Requestors
Below navigation to the System Name from the Pega Designer Studio ((Configure → System → Settings → System Name) | VODKB-200723-160306.pdf |
20c5967d1e98-0 | 4067
Pickup the Current Name from the screenshot below.
Below is the Navigation to the Requestors Types and their access groups ( (Configure → System → General → Requestors)
Please verify, if the below requestors matching the System Name picked-un in the previous step ( AOM-Dev1) below are mapped to the
updated AOMFW access groups which are mapped to the latest application version rule | VODKB-200723-160306.pdf |
902dbdacaf74-0 | 4068 | VODKB-200723-160306.pdf |
96eca430d890-0 | 4069
AOM
[ AOM : 01-01-01 ] [ AOM : 01-02-01 ] [ AOM : 01-03-01 ]
Ruleset Name Ruleset Version
AOM-Artifacts 01-01-01
AOM-Rules 01-01-01
AOM-Int 01-01-06
AOM 01-01-01
AOM-Testing 01-01-01AOM : 01-01-01
Ruleset Name Ruleset Version
AOM-Local 01-02-01
AOM 01-02-01
AOM-Int 01-02-06
AOM-Rules 01-02-01
AOM-Artifacts 01-01-01
AOM-Testing 01-02-01
AOM-Test-Cases 01-02-02AOM : 01-02-01
Ruleset Name Ruleset Version
AOM-Local 01-03-01
AOM 01-03-01
AOM-Int 01-03-17
AOM-Rules 01-03-01
AOM-Artifacts 01-01-01
AOM-Testing 01-03-01
AOM-Test-Cases 01-03-06 AOM : 01-03-01 | VODKB-200723-160306.pdf |
152004bd5ed5-0 | 4070 | VODKB-200723-160306.pdf |
bfa39e3915fc-0 | 4071
Create a new AOM Application Version
[ Rulesets ] [ Application ] [ Custom Access Groups ] [ Operators ] [ Agents ] [ Job Schedulers ] [ System Runtime Context ] [ Requestors ]
Below are the changes required to be performed when a new application version is created.
Rulesets
Create new ruleset versions for all the applicable rulesets
Application
Update the AOM application rule by incrementing the Minor Version as in the screenshot below and save it into the applicable ruleset( AOM
in this case)
Ruleset Name Existing Ruleset Version New Ruleset Version
AOM-Local 01-03-01 01-04-01
AOM 01-03-01 01-04-01
AOM-Int 01-03-17 01-04-01
AOM-Rules 01-03-01 01-04-01
AOM-Artifacts 01-01-01 01-04-01
AOM-Testing 01-03-01 01-04-01
AOM-Test-Cases 01-03-06 01-04-01AOMFW : 01-03-01 | VODKB-200723-160306.pdf |
2cc1404af4ed-0 | 4072
Custom Access Groups
From the records explorer, Click on the Access Group Under Security ( Security → Access Group)
On the Access Group Rule, update the application version as shown below and save the application rule
Update all the below access groups to point to the new application version ( AOMFW: 01-04-01)
AOM:Unauthenticated AOM:MarketInstall
AOM:RulesAdminsV2 AOM:MarketAnalystsAccess Group Name | VODKB-200723-160306.pdf |
785a9b0b72b6-0 | 4073
Operators
Please verify, if the below API operators are mapped to updated access groups
Agents
Please verify, if the Agents created on the below ruleset are mapped to updated access groups. Please check on the security tab of the
Agent and Agent Schedule rule.
Job Schedulers
Not Applicable
System Runtime Context
Not Applicable
Requestors
Not Applicable
AOM:RulesAdmins AOM:MarketAdmins
AOM:MarketManagers AOM:Mailjet
AOM:MarketManager AOM:APIv2
AOM:API
VFUK.VADR VFUK Layer API User
VFUK.TIL VFUK Tibco Integration Layer API User
VFUK.TIL.v2 VFUK Tibco Integration Layer API User ( ***Can be Deleted)
[email protected] Mailjet API UserOperataror Name Description
AOM-Artifacts ProcessBatchJob OOTB AgentRuleset Name Description | VODKB-200723-160306.pdf |
8f7a9d12e748-0 | 4074
Artefacts to deploy to switch any application version to Live
All the below Access Groups points to latest application version. (Need discussion on the following access groups to finalise)
AOMFW Access Groups
AOM Access groups
VADR Access Groups
Access Groups included in the Live Package
Below is the list of Access groups which are included in the package to make a specific version LIVEAOMFW:AssistedAgents AOMFW:MarketAnalysts AOMFW:PegaMarketAdmins
AOMFW:Authors AOMFW:MarketingArchitects AOMFW:PegaMarketManager
AOMFW:CVMManager AOMFW:MarketingDeveloper AOMFW:SimAdmin
AOMFW:CVMOperations AOMFW:MarketingOperations AOMFW:Simulation
AOMFW:HealthCheck AOMFW:MarketInstall AOMFW:Tealium
AOMFW:Users AOMFW:MarketManager AOMFW:Upgrade
AOMFW:Unauthenticated AOMFW:MarketManagers AOMFW:Managers
PegaNBAM:Agents AOMFW:Administrators AOMFW:MarketAdmins AOMFW:Microsites
AOM:RulesAdmins AOM:MarketAnalysts AOM:MarketManagers
AOM:MarketManager AOM:MarketAdmins AOM:Mailjet
AOM:APIv2 AOM:API AOM:Unauthenticated AOM:MarketInstall AOM:RulesAdminsV2
VADR:AssistedAgents VADR:Administrators VADR:Operations
AOM:RulesAdmins AOM
AOM:API AOM
AOMFW:Administrators AOMFW
AOMFW:MarketAdmins AOMFW
AOMFW:PegaMarketManager AOMFW
AOMFW:Unauthenticated AOMFW | VODKB-200723-160306.pdf |
8f7a9d12e748-1 | AOMFW:PegaMarketManager AOMFW
AOMFW:Unauthenticated AOMFW
AOMFW:Tealium AOMFWAccess Group Application | VODKB-200723-160306.pdf |
32eaab3820f0-0 | 4075
Update Connect-REST rules changed as part of specific application version with live authentication profile.
Datapages changed as part of specific application version need to change with live access groups.
Job schedulers changed as part of specific application version need to change with live access groups.
Note: Revert set of operators who tested specific application to live access group to test Live application.AOM:Mailjet AOMFW
AOMFW:Simulation AOMFW
AOMFW:AssistedAgents AOMFW
PegaNBAM:Agents AOMFW | VODKB-200723-160306.pdf |
b2079467c304-0 | 4076
914098: Designing the process to support feature-based releases
Steps to create a new application version for Charlie
Rules Created for Charlie application version
Charlie(MBB) application
Charlie(MBB) application Test Result
Live application
Live application Test Result
Make Charlie as Live application
Make Charlie as Live application Test Result
Outcome
Limitations
Manual tasks
For Charlie application
For making Charlie as Live application
VADR Journey for Charlie application
VADR Journey after making Charlie as Live application
Steps to create a new application version for Charlie
Create new Application version for AOMFW, AOM and VADR applications. (In this POC, the new application version is for Charlie
release with MBB features)
Create Access Groups for new application versions as shown below
Add new access groups to some of the rules like Job Scheduler, Data page which we change in new release.
Create new minor ruleset versions in all new application versions.
Merge new feature(MBB) branch into new minor ruleset version created as part of new application versions.01.03.01 01.03.01 01.01.01 Live For App:
AOMFW:Adminis
trators
For Logic:
AOMFW:Market
Manager
AOMFW:PegaMa
rketManagerAOM:RulesAdmi
nsVADR:AssistedA
gents
01.04.01 01.04.01 01.04.01 Charlie For App:
AOMFW:Adminis
trators.Charlie
For Logic:
AOMFW:Market
Manager.Charlie
AOMFW:PegaMa
rketManager.Cha
rlieAOM:RulesAdmi
ns.CharlieVADR:AssistedA
gents.CharlieAOMFW
Application
versionAOM
Application
versionVADR
Application | VODKB-200723-160306.pdf |
b2079467c304-1 | Application
versionAOM
Application
versionVADR
Application
versionRelease AOMFW Access
GroupsAOM Access
GroupsVADR Access
Groups | VODKB-200723-160306.pdf |
d112d43124d7-0 | 4077
Create an access group AOM:API.Charlie in AOM for API and point the new AOM version application.
Create a new operator Charlie.VFUK.VADR in AOM application and add above access group.
Create an Authentication Profile CharlieAuthentication in VADR application and add above operator into it.
Add this Authentication Profile in a Connect-REST rule, if there is any change in any API in Charlie release.
Rules Created for Charlie application version
Access Groups, Operator and Authentication Profile rules created as part of Charlie application can be re-used for another feature in next
application version after making Charlie as Live application.
Charlie(MBB) application
Change required set of operators with VADR:AssistedAgents.Charlie access group with VADR 01.04.01 application by using activity
ReplaceOperatorAccessGroup.
Test MBB API features from VADR and able to see Live features also.
Charlie(MBB) application Test Result
The "DealProductType" and "DeviceType" properties appear on the Clipboard Page.
Purple Background appears on the Recommendation page (There is no text because there is no Device selected).
On the Edit page, Purple Background appears in the Selected basket section, and Upfront Cost column is located in the Device Tab.Application AOMFW:01.04.01 AOMFW
Application AOM:01.04.01 AOM
Application VADR:01.04.01 VADR-Rules
Access Group AOMFW:Administrators.Charlie AOMFW
Access Group AOMFW:MarketManager.Charlie AOMFW
Access Group AOMFW:PegaMarketManager.Charlie AOMFW
Access Group AOM:RulesAdmins.Charlie AOM
Access Group VADR:Administrators.Charlie VADR-Rules
Access Group VADR:AssistedAgents.Charlie VADR-Rules | VODKB-200723-160306.pdf |
d112d43124d7-1 | Access Group VADR:AssistedAgents.Charlie VADR-Rules
Access Group AOM:API.Charlie AOM-Int
Operator Charlie.VFUK.VADR AOM
Authentication Profile CharlieAuthentication VADR-IntRuleType RuleName Ruleset | VODKB-200723-160306.pdf |
68de1a210a97-0 | 4078
Live application
Use existing operators who has VADR:AssistedAgents access group with VADR 01.01.01 application.
Test to check if existing Live changes working correctly and not Charlie changes.
Live application Test Result
The "DealProductType" and "DeviceType" properties do not appear on the Clipboard Page.
Purple Background do not appear on the Recommendation page.
On the Edit page, Purple Background do not appear in the Selected basket section, and Upfront Cost column is not located in the
Device Tab.
Clipboard Page
Recommendations
Edit Section
Clipboard Page | VODKB-200723-160306.pdf |
7a916e27c8a3-0 | 4079
Make Charlie as Live application
Point VADR:AssistedAgents access group to VADR 01.04.01(Charlie) version.
Remove any Connect-REST rules created with CharlieAuthentication as part of Charlie changes.
Point AOM:API access group to AOM 01.04.01(Charlie) version.
Use the ReplaceOperatorAccessGroup activity to change all Charlie operators to VADR:AssistedAgents access group.
Once we make Charlie Live then we need to change the below access groups with new application version.
AOMFW:Administrators
AOMFW:MarketManager
AOMFW:PegaMarketManager
AOM:RulesAdmins
VADR:Administrators
Make Charlie as Live application Test Result
The "DealProductType" and "DeviceType" properties appear on the Clipboard Page.
Purple Background appears on the Recommendation page (There is no text because there is no Device selected).
On the Edit page, Purple Background appears in the Selected basket section, and Upfront Cost column is located in the Device Tab.
Recommendations
Edit Section | VODKB-200723-160306.pdf |
0fc1f8a4bf7f-0 | 4080
Outcome
A feature can include changes in AOM and/or VADR including API based integration - Tested using GetRecommendations API changes
as part of MBB
Ability to enable a feature for a specific access group (Alpha/Beta) - Tested MBB features by using Charlie access group
Ability to check if those specific access groups (Alpha/Beta) can also access all the live features - Tested MBB features along with Live
features using Charlie access group
Ability to check, if the live user group can access only the live features and not the ones which are not available to them (i.e.: Alpha/Beta
access group features) - Tested Live access group cannot access MBB features
Ability to promote a feature(s) from one access group (Alpha/Beta) to another access group (Beta/Live). For example, from Alpha to
Beta or Beta to Live - Tested Charlie to Live and access MBB features from Live access group
Ability to discard a feature(s) from an access group (Alpha/Beta) - Not Tested as we have only MBB branch currently, required multiple
branches/features to test this
Limitations
As application versions are incremental, the feature in highest version can see the low level version features.
Clipboard Page
Recommendations
Edit Section
01.03.01 01.03.01 01.01.01 Live
01.04.01 01.04.01 01.04.01 CharlieAOMFW Application version AOM Application version VADR Application version Release | VODKB-200723-160306.pdf |
a4878b4de8f9-0 | 4081
If we want to make Alpha(01.06.01) Live, then along with Alpha changes we can also see Beta(01.05.01) and Charlie(01.04.01) changes
from Live.
Manual tasks
For Charlie application
Import a CSV file with Operator Ids and VADR:AssistedAgents.Charlie access group into OperatorAccessGroup datatype.
Run the ReplaceOperatorAccessGroup activity to change operator access group as mentioned above.
For making Charlie as Live application
Point VADR:AssistedAgents access group to VADR 01.04.01(Charlie) version.
Remove/Not available any Connect-REST rules created with Charlie authentication profile as part of Charlie changes.
Point AOM:API access group to AOM 01.04.01(Charlie) version.
Use the ReplaceOperatorAccessGroup activity to change all Charlie operators to VADR:AssistedAgents access group to access Charlie
changes from Live.
Need to change the below access groups with new application version.
AOMFW:Administrators
AOMFW:MarketManager
AOMFW:PegaMarketManager
AOM:RulesAdmins
VADR:Administrators
VADR Journey for Charlie application
Launch Mashup for Upgrade which internally uses VADR:AssistedAgents.Charlie access group to create the Upgrade Case.
VADR:AssistedAgents.Charlie access group points to VADR 01.04.01(Charlie) application version.
VADR 01.04.01 application contains 01-04-01 rulesets which invokes GetCustomer/GetProductList/GetRecommendations API.
GetCustomer/GetProductList/GetRecommendations API contains CharlieAuthentication Authentication Profile.
CharlieAuthentication uses Charlie.VFUK.VADR operator to access APIs in AOM application. | VODKB-200723-160306.pdf |
a4878b4de8f9-1 | CharlieAuthentication uses Charlie.VFUK.VADR operator to access APIs in AOM application.
Charlie.VFUK.VADR operator has AOM:API.Charlie access group which points to AOM 01.04.01 application version.
AOM 01.04.01 application version contains 01-04-01 ruleset versions and also AOMFW 01.04.01 application rulesets which contains
MBB code changes.
VADR Journey after making Charlie as Live application
Launch Mashup for Upgrade which internally uses VADR:AssistedAgents access group to create the Upgrade Case.
VADR:AssistedAgents access group points to VADR 01.04.01 application version.
As we removed the Connect REST rules created as part of 01-04-01 rulesets, application will invoke
GetCustomer/GetProductList/GetRecommendations API from base rulesets.
GetCustomer/GetProductList/GetRecommendations API contains VADRAuthentication Authentication Profile.
VADRAuthentication uses VFUK.VADR operator to access APIs in AOM application.
VFUK.VADR operator has AOM:API access group which points to AOM 01.04.01 application version.
AOM 01.04.01 application version contains 01-04-01 ruleset versions and also AOMFW 01.04.01 application rulesets which contains
MBB code changes.01.05.01 01.05.01 01.05.01 Beta
01.06.01 01.06.01 01.06.01 Alpha | VODKB-200723-160306.pdf |
1f9199c1eed0-0 | 4082 | VODKB-200723-160306.pdf |
8c88f26b6934-0 | 4083
Deployment to make an Application Version Live
Overview
Once all the super testing is completed and the business is happy to promote the application version to all the agents.
A new release package needs to be extracted from both AOM and VADR and then deployed into the target environment like ST/PAT/Pre-
PROD/PROD
Below is the set of rules which needs to be included in the release package
Release Package
AOM/AOMFW
Application rule –Include the application version rules which is being promoted
Access Groups – Verify/Update the application version that is being promoted ( Access groups listed below)
Job Scheduler rules – Verify/Update the access group to the relevant which is pointing to the application version being promoted
Datapages - Verify/Update the access group to the relevant which is pointing to the application version being promoted
Agents- Verify/Update the access group to the relevant which is pointing to the application version being promoted
VADR
Application rule –Include the application version rules which is being promoted
Access Groups – Verify/Update the application version that is being promoted ( Access groups listed below)
Connect-Rest Rules– Verify/Update the access group to the relevant which is pointing to the application version being promoted
AuthenticationProfile -
Datapages - Verify/Update the access group to the relevant which is pointing to the application version being promoted
Agents- Verify/Update the access group to the relevant which is pointing to the application version being promoted | VODKB-200723-160306.pdf |
d6764b1c668c-0 | 4084
VF Confluence Links | VODKB-200723-160306.pdf |
9a4b62c8db47-0 | 4085
R 4.04
App Versions https://ukit-confluence.vodafone.co.uk/display/AOM/R4.4
1238633,1238687, 1238692, 1238683 https://ukit-
confluence.vodafone.co.uk/display/AOM/Recommendations+Portal
1082203,1079515,938334 https://ukit-confluence.vodafone.co.uk/display/AOM/Retail+Stories
957454, 962007 https://ukit-
confluence.vodafone.co.uk/display/AOM/Product+Metadata+REST+
API
545047,658943
https://ukit-
confluence.vodafone.co.uk/display/AOM/Get+Document+List
1082376, 1083201, 1083193
https://ukit-confluence.vodafone.co.uk/display/AOM/4.04+-
+FUT+tickets
ADO VF Confluence Link | VODKB-200723-160306.pdf |
ac819244fe94-0 | 4086
R4.05
1242780, 1206211,
1216428, 1263821,
556365, 868359https://ukit-confluence.vodafone.co.uk/display/AOM/R4.05+Task
1082218, 938125,
1082301, 1082338,
1082343https://ukit-confluence.vodafone.co.uk/display/AOM/R4.05+Retail
1323217, 1323312,
1323389https://ukit-confluence.vodafone.co.uk/display/AOM/Assisted+2nd+Line+Acquisition
https://ukit-confluence.vodafone.co.uk/display/AOM/Product+Catalogue+Data+Pages
AOS : 1305774,
1221923, 1237242,
1305774, 1236218,
1236208, 1236271,
1275682, 1236975,
1236952, 1236768,
1234884, 1234910https://ukit-confluence.vodafone.co.uk/display/AOM/Check+Product+Eligibility
https://ukit-confluence.vodafone.co.uk/pages/viewpage.action?pageId=127170400
1277610 http://ukit-confluence.vodafone.co.uk/display/AOM/Create+Simulation+Screen
1347204 https://ukit-confluence.vodafone.co.uk/display/AOM/1347204+-
+Handling+of+Prepay+subscriptions+in+GPSL+within+an+Post+pay+upgrade
https://ukit-confluence.vodafone.co.uk/display/AOM/AOM+Business+Config
https://ukit-confluence.vodafone.co.uk/pages/viewpage.action? | VODKB-200723-160306.pdf |
ac819244fe94-1 | https://ukit-confluence.vodafone.co.uk/pages/viewpage.action?
pageId=69698308#GetProcessedServiceListConnector(GPSL)-GetProcessedServiceListActivity
https://ukit-confluence.vodafone.co.uk/display/AOM/Customer+REST+API
1277666 https://ukit-confluence.vodafone.co.uk/display/AOM/AOM+Access+Groups
App Versions http://ukit-confluence.vodafone.co.uk/display/AOM/R4.5ADO VF Confluence Link | VODKB-200723-160306.pdf |
b4bda8e0198d-0 | 4087
R4.06
App Versions https://ukit-confluence.vodafone.co.uk/display/AOM/R4.6
AOS : 952690, 1223632,
1235895, 1237009, 1237045,
1237064, 1237080, 1338951,
1237196, 1338915, 1338982,
1237100, 1257124, 1234869,
1234890https://ukit-confluence.vodafone.co.uk/display/AOM/AOS+-+Event+Loader+Changes
https://ukit-confluence.vodafone.co.uk/display/AOM/AOS+-+AOS+Management
https://ukit-confluence.vodafone.co.uk/pages/viewpage.action?pageId=127170400
904758, 1329871, 734010,
1329867https://ukit-confluence.vodafone.co.uk/display/AOM/4.06+TaskADO VF Confluence Link | VODKB-200723-160306.pdf |
a5ee9241fe20-0 | 4088
ST Team - Home Page
ST Team Enhancements
Welcome to ST Team Home Page
ST Enhanceme …
08 Mar 2022, 10:08 AMan.pptx | VODKB-200723-160306.pdf |
6abcbdec9b26-0 | 4089
Defect Management & Triage | VODKB-200723-160306.pdf |
98318a462b2c-0 | 4090
Triage Guidance
The following are minimal triage guidance to be followed for AOM ST Release testing
Loader Case
1. Can you please check, if the Operator who triggered the Case is pointing to the right access-group?
2. Can you please check the error message in the Pega logs?
3. Can you please check the aom_error and aom_audit tables for this issue?
4. Can you please check the admin_spine_load_status table?
a. If a record exists in this table with the same file name loader will skip the file and no data will be loaded
5. Can you please check, if the applicable ResumeCaseFlow Agent is running?
BatchNBA Case
1. Can you please check, if the Operator who triggered the Case is pointing to the right access-group?
2. Can you please check, if the SMS and Email campaigns are scheduled and the last run is successful before triggering the batch NBA
case?
a. In the case of channel management there is no campaigns involved.
3. Can you please check if the respective dataflow work item id is available in AOMConfig and the dataflow landing page, both need to
complement each other for each dataflow which needs running from the case
4. Can you please check the error message in the Pega logs?
5. Can you please check the aom_error and aom_audit tables for this issue?
6. Can you please check, if the applicable ResumeCaseFlow Agent is running?
Extractor Case
1. Can you please check, Is the Operator who triggered the Case is pointing to the right access-group?
2. Can you please check the error message in the Pega logs?
3. Can you please check the aom_error and aom_audit tables for this issue? | VODKB-200723-160306.pdf |
98318a462b2c-1 | 3. Can you please check the aom_error and aom_audit tables for this issue?
4. Can you please check the extractor_status table and check if the status is completed for the respective CaseId?
5. Can you please check, if the applicable GenerateExtract Agent is running?
6. Once extractor is completed the respective files should be generated in the mount point location for Sub channels resq and Concentrix.
7. In the case MVP OBCC generating file functionality has been taken out with 4.1 release. File will only geenrate for Batch OBCC.
AOM API
1. Please validate the request JSON using online tools or Notepad++ Plugins, ( 500 error is possible outcome for an invalid input JSON as
well)
2. Can you please check, if the API Operator who triggered the API is pointing to the right access-group?
3. Can you please check the error message in the Pega logs?
4. Can you please check the aom_error and aom_audit tables for this issue?
TIL API
1. Can you please check, if the API Operator who triggered the API is pointing to the right access-group?
2. Can you please check the error message in the Pega logs?
3. Can you please check the aom_error and aom_audit tables for this issue?
4. Can you please check, if the Simulation Data Transform or Dataset (STF Data) are right for the scenario being tested?
Minimum details on ADO
1. Exact Error Message from the log file | VODKB-200723-160306.pdf |
a1c7b691abc4-0 | 4091
2. aom_arror and aom_audit records for the test which would help us understand the request and response in the case of API and where it
went wrong in other cases like case failures etc
3. Details of scenario with expected result and current result.
4. The request or file used. (AOM API Specs Vodafone UK - AOM API Interfaces - All Documents (sharepoint.com)
5. AOM External Spec (Vodafone UK - AOM External API Interfaces - All Documents (sharepoint.com)) | VODKB-200723-160306.pdf |
c01b2640c03d-0 | 4092
Defect Management Guidelines for Azure DevOps (Vodafone)
Triage:
@Satya Tata @Serkan Baltacı @Dilek Başaran @Shabna Bandre @Thimmasani Gangi Reddy @Birjesh Sharma @Ramya
@amaralingeswar.sunkoji @Akash Ghosh @Sunilkumar Regulagadda @Karthikgoud Ampally @Asha Verma @Chaitanya
Chebrolu @Sruti Purushottamahanti @Birjesh Sharma @Anteshwar Tondare @Sureckaa @Connor McCarthy
Leads:
@Kausik Pal @Suraj Amin @Rajukumar Badkal @SaiSuman Rekala @Praveen Karki
Please follow the following guidelines for raise defects or managing defects in Azure DevOps for the Vodafone project
Creating a NEW defect ticket
Defect Triage Discussion
Defect Fix / Triage Investigations Response (App / Logic Dev Teams)
Defect Retest Actions (QA Team)
Action Step Required Inputs | VODKB-200723-160306.pdf |
aa165ecabc43-0 | 4093
Creating a NEW defect ticket Ensure the following field details are correctly populated:
State: Mandatory
When raising a new defect has to be “New”
Title: Mandatory
Title must be preceded by the functionality short name for which the defect is raised e.g. AU,
MBB, HBB, Simulation ….
The title must look to summarise what the issue is for triage and other testers to have a quick
grasp of the issue e.g. “MBB: EVO tariff not displayed for the recommendation screen and Tariff
tab”
Do not have generic title descriptions e.g. “Simulation: Failed to run simulation”
Area: Mandatory
Select the appropriate Area from the drop list
Assigned To: Mandatory
If the defect is related to logic issues then assign to the logic triage SPOC
If the defect is related to app or UI issues then assign it to the app triage SPOC
If unsure then assign it to Test Manager to be picked up in triage
Iteration: Mandatory
Ensure the correct iteration path shows the correct release or package being tested e.g.
“AOM\Programme\R4.02”
Do not leave it as “AOM\Programme” as that will not be picked up during triage or ay reporting
Parent: Mandatory
Ensure that the parent user story is linked to this defect
Any dependent / related defects than these should also be linked here
Repro Steps: Mandatory
Mention the detailed description of the issue faced
Include all relevant reference documents used / reference for the test
Prerequisites: Mention the test prerequisites
…
Steps to Reproduce:
Mention all the steps taken to get to the defect
…….
Expected Result
As shown in test case / scenario
Include any relevant screen shots
Actual Result:
Mention the actual result in enough details to explain the exact outcome and what the | VODKB-200723-160306.pdf |
aa165ecabc43-1 | Actual Result:
Mention the actual result in enough details to explain the exact outcome and what the
defect is
Include all relevant screenshots
Mashup link
Provide the full mashup link here
Technical details:
Environment:
Browser / OS / Version: | VODKB-200723-160306.pdf |
19064917ddd3-0 | 4094
Graph Id: <<STF Graph name>>
Date / Time of test:
Subscriber Id / MISDN:
Defect Priority: Degree of impact a defect has on the test scenario / case. Tester defaults to 2
but this can will be changed and addressed during triage. If its a priority i.e. all testing is
coming to a grinding stop then set it to 1 and communicate the defect id to Test Lead /
Manager to immediate attention. During triage Priority will be set as follows:
1 = Needs a fix immediately (Blocking complete execution).
2 = Medium priority. Fix needed as soon as possible (Blocking scenarios but execution can be
carried out)
3 = Low priority. Fix can be agreed on a later date or in a later release (e.g. UI defects)
4 = Can essentially be taken to the defect backlog for future remediation.
Defect Severity: (Set by tester)
1 = This is a blocking issue and no testing can progress across the entire fictionality / epic or
group of user stories
2 = This is a bug and is stopping the progress of s specific test case / scenario. Testing can
proceed. Test evidence cannot be collected
3 = This is a bug but does not stop testing from progressing forward. Test evidence related to the
defect cannot be taken but the following scenarios are ok. e.e (UI Defects)
4 = Very low impact. Workarounds available.
Bug Reason: Mandatory
Select the option “Defects” from the drop list
AoM Dev App Version: Mandatory
Select the appropriate app version from the drop list
Raised By (if different from Created By): Optional
If you are using some one else’s Azure DevOps profile then enter your name in the text box | VODKB-200723-160306.pdf |
6120594bab53-0 | 4095
Defect Triage Discussion During defect triage the defect quality is assessed, defect is discussed with with SPOCs and ST
representatives and updates are made as shown below
BUG RCA: Mandatory (Test Manager / Defect Manager)
Choose “Under Investigation” from the drop list
Triage Actions:
1. Defect sent back to tester / author:
a. Change the assigned to owner as appropriate
b. Enter the relevant comments in the “Discussion” box and tag the relevant person
2. Defect accepted in triage and sent to Dev SPOC for next steps
a. Confirm the right SOPC owner is selected in the “Assigned To” area
b. Enter the relevant comments in the “Discussion” box and tag the relevant person
c. Choose the option “Under Investigation” from the BUG RCA Drop list
3. Fix identified on defect (Dev Team / Triage Team)
a. Change the state of the defect to “Fix identified”
b. Add relevant comments in “Discussion” section about what the fix and when it will be
delivered
4. Defect agreed to Close
a. Add relevant comments in “Discussion” section
b. Choose the relevant Resolved Reason option from drop list
i. “Fixed and verified” : If retested successfully
ii. “As designed” : If comments from triage gives us that information
iii. “Duplicate” : If there is a similar defect. Mention the original defect link in the discussion
comments
iv. “Obsolete” : If the feedback received states defect is no longer valid due to passage of time
or other fixes overriding this defect
c. Change the state of the defect to “Closed”
Defect Fix / Triage
Investigations Response (App
/ Logic Dev Teams)Ensure all relevant notes, attachments are updated in the Discussion section | VODKB-200723-160306.pdf |
6120594bab53-1 | / Logic Dev Teams)Ensure all relevant notes, attachments are updated in the Discussion section
If defect is a Code Fixed
Confirm that the BUG RCA shows option “Coding Error”, “Code version error” or “Design
Error” which ever is relevant. if not mark it appropriately
Coding Error: This is a standard code fix delivered
Code version error: This an update code version delivered to fix issue. Not a fix but dev
sent the correct package
Design Error: This is related to a design clarification that led to dev making code changes.
IMPORTANT: This is not to be chosen for design change as that will be treated
differently
Change Resolved Reason to “Fixed”
Change State to “Fix Identified”
Add relevant tag to defect i.e. “AOM_APP”, “AoM_VADR_App” or “AOM_Logic”. This
is important for defect tracking and retrospective
Assign (Return) the defect to the concerned QA owner
If defect is is not a fix but to correct QA collateral
Confirm that the BUG RCA is one of the following:
Test Data Issue: For QA team to correct test data
Test Script Error: For QA team to correct script
Resolved Reason: Is set to “Will not fix” | VODKB-200723-160306.pdf |
054712e4b2cc-0 | 4096
Assign (Return) the defect to the concerned QA owner
If the defect cannot be reproduced during investigations
Resolved Reason: Is set to “Cannot reproduce”
Assign (Return) the defect to the concerned QA owner
If the defect is a duplicate to a existing defect
In the discussion section mention the link to original defect
Resolved Reason: Is set to “Duplicate”
Assign (Return) the defect to the concerned QA owner
If the defect is deferred for a later release
In the discussion section provide the appropriate comments and guidance
Resolved Reason: Is set to “Deferred”
Assign (Return) the defect to the concerned QA owner
If Dev decide not to fix the defect
In the discussion section provide the explanation as to why it will not be fixed
Resolved Reason: Is set to “Will not fix”
Assign (Return) the defect to the concerned QA owner
Defect Retest Actions (QA
Team)Review the recent “Discussion” comments to confirm there is a note for the fix being delivered
Retest and attach the required evidences of the retest outcomes and also add relevant notes in
the “Discussion” section
If Retest is “Pass”
In Resolved Reason select “Fixed and verified” from drop list
Confirm that the BUG RCA shows option “Coding Error”, “Code version error” or “Design
Error” which ever is relevant. if not mark it appropriately
Coding Error: This is a standard code fix delivered
Code version error: This an update code version delivered to fix issue. Not a fix but dev
sent the correct package
Design Error: This is related to a design clarification that led to dev making code changes.
Test Data Issue: IF
IMPORTANT: This is not to be chosen for design change as that will be treated
differently
Change State to “Closed”
If Retest is “Fail” | VODKB-200723-160306.pdf |
054712e4b2cc-1 | differently
Change State to “Closed”
If Retest is “Fail”
Ensure relevant outcomes notes and screenshots are attached
Change state of defect to “Active”
Assign (Return) the defect to the concerned App or Logic team triage owner
Most importantly all discussions should be recorded in ADO not one to one conversations or
anywhere, if there any email conversations please see that they are attached to email
Finally, before closing the defect please attach the working snapshot and a comment. | VODKB-200723-160306.pdf |
9bd5f444734f-0 | 4097
STF
This page holder and its sub pages will be used to hold any KT sessions, Process guidelines and other related documents in relation to
Adqura STF | VODKB-200723-160306.pdf |
c7e5dab53d63-0 | 4098
STF - Introduction
The STF Test Framework is used to generate huge volumes of data without going to the production or source system.
STF Test Framework mainly contains eight modules
1. Data Designer
2. Data Generator
3. Test Designer
4. Mock Designer
5. Toolbox
6. Tag Management
7. Bucket Management
8. Field Config
9. Search
STF divided into multiple components
Data Designer
Graph List:
Add New Graph
A Graph is a combination of Entities and Decision Data Stores, which we are configured based on our business requirements.
Import graph from a file
When a graph is required in other environments then we can export it from one environment to another environment.
Entity list
List of Entities and Decision Data Stores
Delete selected graphs
The user wants to delete a selected graph then selected the required graph or multiple graphs and click on the Delete selected
graphs link
Open a graph
The user wants to open a graph to add/modify/delete the entity
Preview a graph
Clone a graph
The user wants to Clone functionality for example we will take the existing graph and add/update/delete some entities in that
graph and use it for another purpose
Export a graph
Same graphs we want to use in another environment then use the export functionality
Delete a graph
If we don’t want a particular graph in the feature then we will delete that graph
Entity List
Add New Entity
Import Entity From File
Add Selected Entities from Graph
Delete Selected Entities
Open an Entity | VODKB-200723-160306.pdf |
3233108b4368-0 | 4099
Preview an Entity
Clone an Entity
Export an Entity
Data Generator:
It is used to generate a given number of records, and generators are used to generate various types of data, such as SQL attributes,
SQL lists, clipboard references, constants, dates, GUIDs, Joda, and so on. Random Date From Range, Random Decimal From Range,
Random Integer From Range, Random Number From Range, Random Selection From String Array, Random Timestamp From Range,
Random String, Serial, Timestamp, JSON Of Page, and Pega Expressions: these generators are associated with attributes in the
spines based on the data type of the attribute.
Test Designer
Test Plan List
Add New Test Plan
Import Test Plan from File
Test Suite List
Test Case List
Delete Selected Test Plan
Open a Test Plan
Clone a Test Plan
Export a Test Plan
Delete a Test Plan
Test Suite List
Add New Test Suite
Import Test Suite from File
Add Selected Test Suite to Test Plan
Delete Selected Test Suite
Open a Test Suite
Clone a Test Suite
Export a Test Suite
Test Case List
Add New Case
Import Test Case from File
Add Selected Test Case to Test Suite
Delete Selected Test Case
Open a Test Case
Clone a Test Case
Export a Test Case
Mock Designer
Config
Service
Toolbox
Reports
Tag Management | VODKB-200723-160306.pdf |
1862c134d9d6-0 | 4100
Bucket Management
Field Config
Search
Create Graph: Entity Graph is a toolbox that manages the meta-data and their operations, like the user, ability to create, edit, delete, and
clone graphs.
Entity Config: Entity Config is used to define spine/table configurations, like the name of the spine and whether the user wants to generate
data into the database tables or in the datasets using existing class name details. Users can create, edit, delete, and clone an entity.
Attribute Config: Attribute Config is used to define attribute/column configuration, like the name of the column, user wants to generate
different kinds of data using generators. Users can create, edit, and delete an attribute.
Generators: Generators are used to generate various types of data, such as SQL attributes, SQL lists, clipboard references, Constant,
Date, GUID, Joda, and so on. Random Date From Range, Random Decimal From Range, Random Integer From Range, Random Number
From Range, Random Selection From String Array, Random Timestamp From Range, Random String, Serial, Timestamp, JSON Of Page,
and Pega Expression these generators are associated with attributes in the spines based on the data type of the attribute.
Dataset Generator: The user can define the number of records and click generate button, Many records are generated in the dataset. | VODKB-200723-160306.pdf |
8fb00d1a56bb-0 | 4101
STF Demo Link
Click here to see a demo for STF v0.9
Other recordings click here
For STF V0.9 tutorials click here | VODKB-200723-160306.pdf |
088cda1d7d23-0 | 4102
STF Graph Generation Process & Usage Guidelines
@Venkata Ravi Kiran Chitturi @Satya Tata | VODKB-200723-160306.pdf |
995bef7e784e-0 | 4103
STF - API testing guidelines | VODKB-200723-160306.pdf |
04dd866c763e-0 | 4104
STF - Truncate Data Sets & Flush Data Pages
A test case is available for truncating all data sets and flushing data pages at a time. It is available in the CAPST2 environment.
Click on the run button, Truncate Data Sets and Flush Data Pages at once
List of Data Sets and Data Pages | VODKB-200723-160306.pdf |
486da39c8b9f-0 | 4105
R2.13
This page holds relevant ST testing information related to R2.13
Design Gaps Identified
PC SIT Environment Downtime Log
Defect Id Description Owner
23 Feb 2022 05:00 pm IST 09:30 pm IST Assisted Upgrades, ELP UK
Mobile numbers user story
Date Time From Time To Impact and description | VODKB-200723-160306.pdf |
e229152a1c71-0 | 4106
R3.1
This page holds all ST details related to VF 3.1 Release | VODKB-200723-160306.pdf |
74e08af34db0-0 | 4107
R3.1 ST Epics Walkthrough Status
@Satya Tata @Shabna Bandre @Asha Verma @Serkan Baltacı @Venkata Ravi Kiran Chitturi @Çağlar @Dilek Başaran
@Karthikgoud Ampally @Sunilkumar Regulagadda @Birjesh Sharma @Sruti Purushottamahanti @Chaitanya Chebrolu @Rajani
Gullapalli @Ramya @Kavitha Ramasamy (Unlicensed)
In the column “Session Comments” please record the following: Date on sessions (DD /MMM /YY), user stories covered, and copy paste
the link to the session recordings
Opti GetWell PM Tool: PM Tool
changes - Usability (620740,
620747, 620749, 620752,
620753, 620763, 620776,
642456)Divya / Mounika Sruti ADOs covered in session:
620747,620740,620749,
653275
Session by Divya on 24th Feb
Link to recording:
https://adqura-
my.sharepoint.com/:v:/p/chaita
nya_chebrolu/EVVT9NPJgx5B
qdNJi_72wWQBsyqyIBvMudZv
qF_gaqrp0A
Extras Landing Pages-PM Tool
changes (653275,676843) Sruti 653275 - Tested as a prod fix in
R3.1
676843 - Tested in R2.13
Opti GetWell Framework - Intent
Redesign (651288) - XLSachit Speak with Matt to identify which 25 | VODKB-200723-160306.pdf |
74e08af34db0-1 | Redesign (651288) - XLSachit Speak with Matt to identify which 25
scenarios are to be tested by STShabna
Opti GetWell Framework
Simplification (604833, 651289,
604938, 614224 [HW])Sachit 1. Could we please have a E2E story
group walkthrough
2. Simplification could lead to
additional regression. Can
regression points please be
identified as part of walkthroughShabna 1. 604833 : Session by Sachith
on 03/07/2022
Link to Recording:
https://adqura-
my.sharepoint.com/:v:/p/serkan
_baltaci/ETIEmWCoPudKvBSK
oLpT7oAB7AA3HjzO7kUQSyC
In0MZTw
2. 651289: Session by Sachith
on 03/11/2022
Link to Recording:
https://adqura-
my.sharepoint.com/:v:/p/ramya
_vishwanadula/EXT2FBvULsZ
JkXt_XDVXg2MBayklh9kvPKw
dp3sHyyomAwEpic Level Walk throughs with
Designers / Developers
(Min 1.5 hrs per session)Walkthrough
Delivery
OwnerGuidance & Comments for
Walkthrough Sessions OwnersST Stub
Team
Session Comments | VODKB-200723-160306.pdf |
e66b40b0153b-0 | 4108
3. 614224 : Session by Sachith
on 10-03-2022 ==>
https://adqura-
my.sharepoint.com/:v:/p/ramya
_vishwanadula/EXT2FBvULsZ
JkXt_XDVXg2MBayklh9kvPKw
dp3sHyyomAw
Opti GetWell - Real Time Triage
Tool (619575)Sachit 1. Could we please have a E2E story
group walkthrough
2. 4 APIs in scope. Turning on triage
mode starts writing to a dataset
3. APIs impacted - GetNBA ,
GTBUNDLEEVENT,
GETPRODUCTLIST,
GETRECOMMENDATION (VADR)Shabna Session by Sachith on
03/07/2022
Link to Recording:
https://adqura-
my.sharepoint.com/:v:/p/serkan
_baltaci/ETIEmWCoPudKvBSK
oLpT7oAB7AA3HjzO7kUQSyC
In0MZTw
Opti GetWell - Simulation User
Story (595836) - XLSachit 1. Could we please have a E2E story
group walkthrough
2. ST needs to be aware which
funnels are involved with GETNBA
3. All 20 need to be tested
4. Process of testing same as batch
5. Read this confluence page:
https://adqura.atlassian.net/wiki/spa
ces/VODKB/pages/3283615745/Si
mulation+Funnels+GetNBAAsha
Opti GetWell - Volume | VODKB-200723-160306.pdf |
e66b40b0153b-1 | mulation+Funnels+GetNBAAsha
Opti GetWell - Volume
Constraint (651290,614228) - LSachit 1. Could we please have a E2E story
group walkthrough
2. Test scenarios have been attached
for referenceShabna 614228:Session by Sachith on
03/11/2022
Link to Recording:
https://adqura-
my.sharepoint.com/:v:/p/ramya
_vishwanadula/EXT2FBvULsZ
JkXt_XDVXg2MBayklh9kvPKw
dp3sHyyomAw
eCare-Digital NBA (570075,
570078, 570080,570081 [HW]) Ravi Given KT by Sachith on 03/08
and covered User
Stories 570075, 570081 (click
here to watch the Recorded KT
session).
Given KT session by Kausik
Pal on 03/10, User Story
570078 (click here to watch the
Recorded KT session).
Given KT session by Rajkumar
B on 03/14, User Story 570080
(click here to watch the
Recorded KT session). | VODKB-200723-160306.pdf |
a816ec9e9ce3-0 | 4109
Opti GetWell - BDC pipeline -
New BDC Pipeline - dual
running (613758)Sachit 1. Could we please have a E2E story
group walkthrough
2. Push old pipeline and new pipeline
and verify outcomes for same
customer
3. Logic should use new pipeline
where old and new are both
available for a customer for the
same modelRavi KT Session given by Sachith
on 03/09 (click here to watch
the Recorded KT session).
Extras Landing Pages-App
Dynamics (653328) Shabna
Extras Landing Page -
Strategy Framework
Changes(473873) Shabna
NBA FW-Strategy
Framework(469699)Sachit Shabna Session by Sachith on
03/07/2022
Link to Recording:
https://adqura-
my.sharepoint.com/:v:/p/serkan
_baltaci/ETIEmWCoPudKvBSK
oLpT7oAB7AA3HjzO7kUQSyC
In0MZTw
Private Pricing 2nd Line
(484338, 569060,
570156,573199) XLSachit 1. Could we please have a E2E story
group walkthrough
2. A MIRO board can be shared to
understand the journeyAsha
Private Pricing 2nd Line R2.13
backlog(484153, 484238,
484240,484334,484342,484345,
502913
523263,523329,524880,534887,
535549,535600,536461,569164, | VODKB-200723-160306.pdf |
a816ec9e9ce3-1 | 535549,535600,536461,569164,
570103)Sachit Asha
Data - Siebel Orders:
Identification of Loan Device
(608761)Sunand Serkan Session by Sai and Rajendar
on 03/09
Link to Recording:
https://adqura-
my.sharepoint.com/:v:/p/satya_
tata/EbRLKPq44AlNl1wxvJB7
m3ABRgQYbUK2-
Cf5VAzRCXFW8w
General - Ops: DataFlow Audit
History(649596)Shrin Satya
Data (590003) Satya
Roaming (654059) Satya | VODKB-200723-160306.pdf |
76b726f344c3-0 | 4110
Data-BDC pipeline (670853) This is a technical change.
Existing functionality should work
as it is.
Feasibility to avoid data page to
optimization teamRavi KT Session given by Raju on
03/11 (click here to watch the
Recorded KT session)
Upgrades - Usage
Tab:Entertainment Flag(523918)Sunand Serkan Not needed. Scenarios
designed and review done,
execution complete
Upgrades - Lionheart: Lionheart
Reward Identification (650405)Sunand Serkan Session by Sai and Rajendar
on 03/09
Link to Recording:
https://adqura-
my.sharepoint.com/:v:/p/satya_
tata/EbRLKPq44AlNl1wxvJB7
m3ABRgQYbUK2-
Cf5VAzRCXFW8w
Upgrades - Customer API:GCPL
- Change Structure of Response
to Page not Page List(650411)Sunand Serkan Session by Sai and Rajendar
on 03/09
Link to Recording:
https://adqura-
my.sharepoint.com/:v:/p/satya_
tata/EbRLKPq44AlNl1wxvJB7
m3ABRgQYbUK2-
Cf5VAzRCXFW8w
Upgrades - Customer API:GCPL
- Get Customer - Lionheart
Processing of Only Active Status
Offers(650417)Sunand Serkan Session by Sai and Rajendar
on 03/09
Link to Recording:
https://adqura-
my.sharepoint.com/:v:/p/satya_ | VODKB-200723-160306.pdf |
76b726f344c3-1 | ERROR: type should be string, got "https://adqura-\nmy.sharepoint.com/:v:/p/satya_\ntata/EbRLKPq44AlNl1wxvJB7\nm3ABRgQYbUK2-\nCf5VAzRCXFW8w\nUpgrades - Pilot 1 UI: Keeping \nthe Pilot UI up to date for \nongoing Commercial UAT \n(594082) - LSunand Serkan Session by Raju on 03/14\nLink to Recording:\nhttps://adqura-\nmy.sharepoint.com/:v:/p/serkan\n_baltaci/ERjJnC411DxFjMcz8\nWqebXcB1gA7C3iFJJccgEjqs4\nvg-w\nUpgrades - Displaying the \nDevice in the Pilot 1 front end \n(623187) - LSunand Serkan Session by Raju on 03/14\nLink to Recording:\nhttps://adqura-\nmy.sharepoint.com/:v:/p/serkan\n_baltaci/ERjJnC411DxFjMcz8" | VODKB-200723-160306.pdf |
a074819d72ae-0 | 4111
WqebXcB1gA7C3iFJJccgEjqs4
vg-w
Upgrades - Displaying the
Device in the Pilot 1 front end
(623190) - LSunand Serkan Not in scope
Assisted Upgrades-Bingo to
Bingo (560920,590670) Serkan Not needed. Scenarios
designed and review done
Assisted Upgrades-Customer
Billing (523919,544928) Serkan They will be in 3.2
Assisted Upgrades-Customer
profile (527479) Serkan Not needed. Scenarios
designed and review done | VODKB-200723-160306.pdf |
c9afcf73525b-0 | 4112
R3.1 - PC SIT Environment Downtime Log
@Satya Tata @Shabna Bandre @Asha Verma @Serkan Baltacı @Venkata Ravi Kiran Chitturi @Çağlar @Dilek Başaran
@Karthikgoud Ampally @Sunilkumar Regulagadda @Birjesh Sharma @Sruti Purushottamahanti @Chaitanya Chebrolu @Rajani
Gullapalli @Ramya @Kavitha Ramasamy (Unlicensed)
15 Mar 2022 11:15 IST PC SIT Env down due to some AWS issue. At the time of this entry the environment
is still down and ST team overall has lost over 5 hours.
22 Mar 2022 12:00 IST PC-SIT is down for multiple times for about 3 hours due to L4 testing activities and
heap dump created.
30 Mar 2022 3:30 IST PC-SIT is down due to heap dump issueDate
From Time To Time Reason / Comments | VODKB-200723-160306.pdf |
eb01563c5fdb-0 | 4113
R3.1 Data Configuration Concerns
@Satya Tata @Shabna Bandre @Asha Verma @Serkan Baltacı @Venkata Ravi Kiran Chitturi @Çağlar @Dilek Başaran
@Karthikgoud Ampally @Sunilkumar Regulagadda @Birjesh Sharma @Sruti Purushottamahanti @Chaitanya Chebrolu @Rajani
Gullapalli @Ramya @Kavitha Ramasamy (Unlicensed)
1 Mail sent to Anteshwar/Sachith for Private Pricing
DecisionData’s (All Decision Data’s are not
Properly configured/Pushed)Sunil/Kart
hikAnteshwar Anteshwar/Sunil/Karthik updated All Private Pricing
DD’s manuvally.
2 Bug 749494: Private Pricing: All Offers Dropping
at IdentifyBestTreatmentForGetNBA StrategySunil Anteshwar Some condition is missing in
IdentifyBestTreatmentForGetNBA strategy, New
changes are applied.
3 Bug 750805: Private Pricing: Duplicate offers in IH
Table.karthik
4 Test Groups should have the option of setting
eligibility/entry criteria (e.g. prop filter)
TestGroupEligibility Proposition filter - There
is no rule defined in PC-SIT?Asha Sachith There is no actual catalogue provided by business
so there are no rules built. By default, its set to
true. Optimization team will build rules according to
the requirement in future.
5 Users should be able to set start and end dates
for Test Groups, and enable/disable as required
Which DD and column holds the start and end | VODKB-200723-160306.pdf |
eb01563c5fdb-1 | for Test Groups, and enable/disable as required
Which DD and column holds the start and end
dates of test group and how to enable and
disable it?Asha Sachith Test Groups can be enabled or disabled using
Enabled column in the Test Groups decision data .
Note: Start date and end dates are not available.
Intentionally we haven't built this one.
6 Users should be able to set a duration for each
test group, which reflects the amount of time a
customer will spend in a test group. This should
be a configuration item (e.g. 30 days). We will
need an exit date to calculated based on the
duration value (i.e. selection date + duration)
Where can we have this value configured?Asha Sachith It can be configured in the TestGroupExpiry column
in the Test Groups Decision Data.
749494 - Private Pricing: All Offers Dropping at
IdentifyBestTreatmentForGetNBA StrategySunil Anteshwar
750805 - Private Pricing: Duplicate offers in IH
Table.Karthik Anteshwar
754775 - Private Pricing: Duplicate offers inserted
into IH Table for AddMobileWithHandset and
AddSIMOSunil Anteshwar No. Questions / Concern Raised
ByMitigation
OwnerResolution / Comments | VODKB-200723-160306.pdf |
7ad372a9e02d-0 | 4114
754741 - Issue with 12/24 duration in
IdentifyMaxDiscountForTariffType StrategySunil Anteshwar
755274 - Private Pricing: IH Reporting table not
getting child offers and max discount.Karthik Anteshwar
758301 - Private Pricing: Not getting Child offer
for MIFI OfferSunil Anteshwar
758302 - Private Pricing: Child offers dropping
when LegalRequirement value is greater than 0Sunil Anteshwar
758459 - Private Pricing: GPL API getting
Business Logic error.Karthik Anteshwar
761081 - Private Pricing: GPL Payload response
is not matching with the Product IH Reporting
Table.Karthik Anteshwar
764033 - Private Pricing: Getting Business logic
error, when we hit GetNBA with No Of Actions 0Sunil Anteshwar
766973 - Private Pricing: Internal Server Error Sunil Anteshwar
766976 - Private Pricing: Not getting Child offers
for all Parent OffersSunil Anteshwar
769658 - Private Pricing : GPL two tariffs we are
getting in payload but in IH parent - child is
missing.Karthik Anteshwar
769991 - Private Pricing: Issue with Tariff tier
ComparisonSunil Anteshwar
770621 - Private pricing : Test Group column is
empty for child offers in IH.Karthik Anteshwar
772402 - AddMifi offer is not displaying in IH even
we getting Dongle TariffKarthik Anteshwar
772426 - Private Pricing: Detail section missing
for all offersSunil Anteshwar
774022 - Private Pricing: Issue with Tariff tier | VODKB-200723-160306.pdf |
7ad372a9e02d-1 | for all offersSunil Anteshwar
774022 - Private Pricing: Issue with Tariff tier
Comparison for AddDataSIMOSunil Anteshwar
774199 - Private Pricing: Issue with Tariff tier
Comparison for AddSIMOSunil Anteshwar
774486 - Private Pricing: Issue with Tariff tier
Comparison for AddMIFISunil Anteshwar
776915 - Private Pricing: 'No Offer' response is
not returned in the GetNBA API and IH.Karthik Anteshwar
777927 - Private Pricing: Issue with Prioritize for
Unlimited PlanSunil Anteshwar | VODKB-200723-160306.pdf |
ab887f91bb3c-0 | 4115
778255 - Private Pricing: Issue with Prioritize for
EVO PlanSunil Anteshwar
778393 - Private Pricing: Issue with Discount
Codes for Data Allowance PlanSunil Anteshwar
779262 - Private Pricing: Prioritization not working
for Unlimited and EVO planSunil Anteshwar
779880 - Private Pricing>>SetNBA>>After
triggering the SetNBA request, the Test Group
column value displayed as NULL in IH for both
SubChannels(Purchase/UpgradesAndOffers Anteshwar
779970 - Private pricing : Intent, ExecutionMode,
TargetSubchannel and TestGroup Expiry column
inserted not properly in IH.Karthik Anteshwar
781034 - Private Pricing: GPL payload response
and IH, childs not getting eligible for Tablet and
Mifi parent offers.Karthik Anteshwar
781687 - Private Pricing: Issue With Hero Plan Sunil Anteshwar
782222 - Previous test cell is not allocated if
already there is IH entry for account having same
offer Anteshwar
785860 - Private Pricing : Subscription Type is
Mobile Service For GetHandsetTariffsForSKU, But
in GPL Payload response getting Dongle related
Tariffs.Karthik Anteshwar
786515 - Private Pricing: Prioritization issue for
Hero PlanSunil Anteshwar
783061 - Cell code is allocated and test group is
default and test group expiry is current time stamp
when test group is not configured for offerAsha Anteshwar
783749 - Testgroupexpiry date time stamp is
changing for AddTable on second hit of GPL when | VODKB-200723-160306.pdf |