id
stringlengths 14
14
| text
stringlengths 2
2.42k
| source
stringclasses 1
value |
|---|---|---|
f130613862c2-0 | 155
Step1 : To select a treatment which has to be added to bundle as child instead of searching in the populated list.
Step2 : To enable/disable a treatment which will be added to the list in Summary and Landing page.
Step3 : Click on plus(+) to add treatment as child to the bundle and navigates back to bundle page. | VODKB-200723-160306.pdf |
599820ce54ca-0 | 156
Enable/Disable Treatment to Treatment Variation
Treatment to treatment variations for a treatment will be displayed in treatment review page at which an option is available to enable/disable
without editing as shown below. | VODKB-200723-160306.pdf |
0f01e6d96027-0 | 157
Add/Edit Treatment Variation
For new treatment, "Add Default variant" button is available in the treatment page after record is saved to create "TreatmentVariantDefault"
variation to a treatment as shown below.
For Existing treatment, treatment variation and treatment to treatment variation can be created by clicking on "Add Variant" button and can
edit/delete existing variation from the review page.
This opens treatment variation page where it allows to create a new treatment variation and treatment to treatment variation or modify the
existing one. | VODKB-200723-160306.pdf |
22778b5991de-0 | 158
Step1 : When existing variation is selected from the list, all the details will get populated.
Step2 : Existing treatment to treatment variation for a treatment will be displayed as shown.
If the selected SubChannel for treatment has ApplyTemplates false, edit page will be shown as below.
If the selected SubChannel for treatment has ApplyTemplates true, In Channel ApplyActions to true and ApplyScenarioTemplating to
false, edit page will be shown as below. Templates and Outcomes will be under each subchannel.
If the selected SubChannel for treatment has ApplyTemplates true, In Channel ApplyActions to true and ApplyScenarioTemplating to
true, edit page will be shown as below. Default scenario will be displayed by default when scenarios are defined. | VODKB-200723-160306.pdf |
e2c97b8d0f57-0 | 159
Templates and Outcomes will be under each subchannel & scenario combination.
Click on ‘Update’ button at template or action selection to update the values.
All the outcomes which are defined for a channel will be displayed under Outcomes as below. | VODKB-200723-160306.pdf |
b27a8eac188a-0 | 160
When ‘Create Customer Interaction’ is selected, a section will be displayed to update interaction details.
Below Action Type section will be displayed only when ‘Allow HandoverActions’ is set to true in channel screen. Unique list of action
types from handover actions screen will be displayed as tabs and selection of action id displays its respective action attributes and
template attributes.
Click on ‘Update’ button at action attributes and template attributes to update the values. | VODKB-200723-160306.pdf |
24da30ea7ae2-0 | 161
Once treatment to treatment variation is created, it will be added to the list in the review page. | VODKB-200723-160306.pdf |
2e046c0ba554-0 | 162
Volume Constraints
Constraints can be created/modified in treatment page.
For all treatments, constraints will be at channel level as above except for OutboundCC treatments.
For OutboundCC treatment, constraints will be at subchannel level as below.
Volume Limit is disabled for other channels which as the ability to select multiple subchannels.
Volume Limit will be greyed out and set to -1 when Unlimited Volume is checked.
Volume constraints will be created for the edited treatment only when a value is given to volume limit. If the value is made empty after
create for any channel or when subchannel is unselected for OutboundCC treatments, then volume constraints will be deleted. | VODKB-200723-160306.pdf |
42374951ae30-0 | 163
Clone Treatment
A treatment can be cloned from below three screens. Clone option will be available for locked/unlocked treatment.
Clicking on clone icon/button allows to clone a particular treatment which navigates to edit screen in order to create a new treatment by
changing it’s unique fields. | VODKB-200723-160306.pdf |
7e97629e9891-0 | 164
Clone Treatment Variation & Treatment To Variation
A treatment variation and treatment to variation can be cloned from below screen. Clone button will be disabled for locked treatment.
Step1 : ‘Clone Treatment Variation’ button allows to clone treatment variation and treatment to variation with new treatment variation.
Step2 : ‘Clone Treatment To Treatment Variations’ button allows to clone only treatment to variation with existing treatment variation. | VODKB-200723-160306.pdf |
a93783588b71-0 | 165
Clone Treatment To Variation
Treatment to variation is merged into treatment variation page. Please refer to Clone Treatment Variation & Treatment To Variation -
Vodafone - Confluence (atlassian.net) | VODKB-200723-160306.pdf |
f31d3d4e4d27-0 | 166
Upload/Download Treatment
Upload and download option for treatment is available in manage treatments screen as below.
Dropdown has two options:
Treatment : Select Treatment to download and upload treatments.
TreatmentToSubChannel : Select TreatmentToSubChannel to map subchannels to existing treatment.
Download : It downloads all unlocked treatments along with the treatments in edit within the work item. User can download the treatments
based on search provided.
Upload : It allows to upload the treatments data in bulk. The modified treatments will be added to in edit list and locked with the work item. | VODKB-200723-160306.pdf |
75557c4fd8c3-0 | 167
Upload/Download Treatment To Variation
Upload and download option for treatment to variation is available in treatment review screen as below.
Upload button will be disabled for the locked treatment.
Download : It downloads treatment to variation data of respective treatment.
Upload : It allows to upload the treatment to variation data in bulk. The respective treatment will be added to in edit list and locked with the
work item when treatment to variation is uploaded with the modified data. | VODKB-200723-160306.pdf |
e6437ab2926a-0 | 168
Manage Releases
In new ways of working, several work items can be clubbed into a release. Users with Manager access will be able to create a package and
include work items as needed. Packaging performs merge of multiple work items and creates a new baseline. This new baseline can be
scheduled for push as part of package work flow. New baseline is also available in the Push screen. | VODKB-200723-160306.pdf |
eeab7bc61b6d-0 | 169
Create Release
Packages are shown in “Package Release” menu item under Home menu which is visible only for Manager and Release Manager. This
shows the list of packages that are created. Click on "Create Package" button to create a new package.
This opens below page where releases which are in progress will be shown under 'Release Version' selection. Based on the selection of
release, the assigned work items for that release and Ready for Release status work items will be displayed. Change history review is
possible by clicking on respective work item from the list.
Work items can be added/removed for package creation until the merge is completed.
Click on Next to review the changes from multiple work items which creates a branch with release version.
Below is the Merge view and discard option is not given to discard the changes in merge. | VODKB-200723-160306.pdf |
9f26eb385fe7-0 | 170
If there are any catalogue validation errors in merge, it is possible to go back to work items selection page and add/remove a work item for
package.
If there are no errors, merge completion message will be displayed as below.
The status for selected Assigned to Release/Ready for Release work items are updated with ‘Committed to Release’ and Assigned to
Release work items which are not selected are updated with ‘Ready for Release’
Click on Next which navigates to Package Completion page to schedule. | VODKB-200723-160306.pdf |
c0aca4d896ef-0 | 171
Discard Release
If the package is not required, it can be discarded by using Delete icon in packages list. Delete icon is enabled when package is in 'In
Progress' status and before merge is completed.
A confirmation dialog will be shown to user as shown below.
Clicking on Yes button removes the package from the list. | VODKB-200723-160306.pdf |
3bb4acae4ce0-0 | 172
Schedule Push
Schedule push is possible once merge is completed. The list of work items that are selected for package creation will be displayed
whenever package is opened after merge as below.
On submitting the page, it navigates to Package completion to schedule the push where the users which have 'Release Manager' access
will be displayed in Operator. All are mandatory for Immediate and Schedule push.
Deploy has three options :
Immediate : To push the package as soon as the release manager approves it.
Schedule : On selection of Schedule, Scheduled Time is displayed as shown below which is mandatory and wont accepts the past date
time. The package get pushed at the time of schedule after the approval of release manager.
Don’t Schedule : This will not schedule the push which updates the status to ‘Resolved-Completed’ and can schedule later. The other fields
are not mandatory.
The status will be ‘Pending-Approval’ in case of Immediate/Schedule and all other fields are mandatory and the package will get pushed to
PROD environment after approval.
An email notifications will be sent to the release manager and user who has assigned the package. | VODKB-200723-160306.pdf |
bfdcc35a60fc-0 | 173
Approve Push
The list of work items selected are displayed when Release Manager opens a package which is in ‘Pending-Approval’ status.
Only Release Manager can navigate to the Release Approval page where the details will be displayed above to approve/reject.
Reason for Rejection is mandatory when release manager rejects the release which is shown as soon as Manager opens the package as
below.
Below message is displayed when the release is approved and by submitting the page.
The package will get pushed to PROD environment after approval.
An email notifications will be sent to Release Manager and Manager who has assigned the package when approved/rejected. | VODKB-200723-160306.pdf |
9e654402a3d4-0 | 174
Assisted Upgrade Wizard
Catalogue consists of many artifacts within PM Tool. The branch way of working has few limitations.
A subset of artifacts are changed in most of the releases but every branch is presented with all the artifacts in the PM Tool Portal under
Artifacts menu.
Whenever a Push is done, all the artifacts will be deployed to target environment.
In new way of working, AU versions will help overcome these limitations. A version can consist of only Assisted artifacts data.
Push can be done immediately into production or scheduled for a later date and time. Only artifacts which undergone the changes in the
version will only be refreshed in the target environment upon push. | VODKB-200723-160306.pdf |
de8af9337950-0 | 175
Create Version
AU versions which are in ‘In Progress’ will be shown in Assisted Upgrade Patch menu item under PM Tool Flows Menu. This menu item
shows the list of versions created so far and is order by Update On column in descending order. At the bottom of the list “Create Patch”
button allows to launch the wizard.
Click on Create Patch which displays below screenshot that allows user to give the catalogue version to work on.
Give the version and click on Next button which creates a new version and navigates to Summary page which will be empty as it is a new
version. | VODKB-200723-160306.pdf |
e956b577b665-0 | 176
Version and Artifacts are displayed towards the left side of the page. Below are displayed towards right side of the page.
Close Flow : allows the user to close the flow.
Merge and Review : allows to merge the changes to a trunk.
Change History : displays the history of this version. | VODKB-200723-160306.pdf |
29cbff79098d-0 | 177
Manage Artifacts
Select any artifact from the left side of the page and artifact names are displayed under each management menu like in PM Tool Portal.
Artifact view will be same like in portal.
Select any record from the grid which populates the values at the bottom section as below.
Save : allows to save the changes of selected record.
Clear : allows to clear the selected record. | VODKB-200723-160306.pdf |
ab4179fe8249-0 | 178
Clone : allows to clone the selected record to create a new record.
Download : allows to download all the records of an artifact in a single csv file.
Upload : allows to upload the changes made in the downloaded file.
Click on Next to navigate to the Summary page. | VODKB-200723-160306.pdf |
2365313b2ae3-0 | 179
Summary
Allows to view the changed records with it’s unique names of each artifact in an individual tabular form as below.
Click on Next to navigate to the Merge view. | VODKB-200723-160306.pdf |
8ecdead3d7a7-0 | 180
Change History
Click on Change History button to view the history of this version.
Click on Next which navigates back to the previous screen from where Change History was selected. | VODKB-200723-160306.pdf |
9786c4e36e28-0 | 181
Merge To Trunk
Click on Merge and Review button to review the changes which are compared with the latest baseline version.
Each artifact related changes are displayed for each record in a tabular form.
Click on Next to navigate to Patch Completion to assign the version to a Release Manager for release approval.
Done with all changes : allows to merge the changes in version to a new baseline version and makes all other fields as mandatoy.
Back to Summary : allows to navigate to Summary page to continue with the changes.
Operator : shows all the users who has Release Manager access and mandatory when Done with all changes is selected. | VODKB-200723-160306.pdf |
08c306c06db2-0 | 182
Deploy : displays Immediate and Schedule options and mandatory when Done with all changes is selected.
Immediate : To push the baseline version as soon as the release manager approves it.
Schedule : On selection of Schedule, Scheduled Time is displayed as shown below which is mandatory and won't accepts the past date
time. The baseline version get pushed at the time of schedule after the approval of release manager.
Click on Next which creates a temp version to validate all the artifacts and then displays the below page.
Provide the version ID into which the changes should get merged and then click on Next to complete the merge process.
The version created to make the changes and the baseline version will be approved before reaching to this point.
Click on Finish that assigns the version to release manager. The status will be ‘Pending-Approval’ in case of Immediate/Schedule and the
baseline version will get pushed to PROD environment after approval.
An email notifications will be sent to the release manager and user who has assigned the version. | VODKB-200723-160306.pdf |
cf434981141e-0 | 183 | VODKB-200723-160306.pdf |
612165cbfa69-0 | 184
Approve AU Push
The list of versions which are assigned to a release manager will be displayed in the Home Menu under Work Items.
When a version is selected, below page is displayed with the details of version, notes and deploy.
Reason for Rejection is mandatory when release manager rejects the release which assigns back to user and will be in ‘In Progress’.
When user opens the rejected version in Assisted Upgrade Patch menu, displays the below summary page where merge and artifacts are
not displayed and Reason for Rejection is displayed above the artifacts. | VODKB-200723-160306.pdf |
ebf678ce250e-0 | 185
Next button navigates to Patch Completion page where any of the fields can be modified and assign to release manager.
Below message is displayed when the release is approved and by submitting the page. | VODKB-200723-160306.pdf |
dd9ab8f81bac-0 | 186
The baseline version will get pushed to PROD environment after approval.
An email notifications will be sent to Release Manager and user who has assigned the package when approved/rejected. | VODKB-200723-160306.pdf |
b5294802032e-0 | 187
Config Flow
Catalogue consists of many artifacts within PM Tool. Typically a branch is created and developers work on branch version of the catalogue
until the manager merges the branch to create a new baseline version of the catalogue. The branch way of working has few limitations.
Only one person can work on a branch at a time and has to be assigned to different users to complete a new baseline.
A subset of artifacts are changed in most of the releases but every branch is presented with all the artifacts in the PM Tool Portal under
Artifacts menu.
Whenever a Push is done, all the artifacts will be deployed to target environment.
In new way of working, work items will help overcome these limitations. Multiple work items can be created at any point of time allowing
parallel development towards a new baseline release. Business Config/Bundle Event NTID Map/Events managed within a work item are
locked into it and other work items cannot edit those Business Config/Bundle Event NTID Map/Events until the lock is released by including
the work item in a release. Only Business Config and their related artifacts are managed within a work item so a limited set of artifacts to
deal with instead of all artifacts available in a catalogue.
Push can be done immediately into production or scheduled for a later date and time. Only Business Config/Bundle Event NTID
Map/Events artifacts related targets will be refreshed in the target environment upon push. | VODKB-200723-160306.pdf |
b7168559b4de-0 | 188
create a config flow work item
Work items are shown in config Flow menu item under PM Tool Flows Menu. This menu item shows the list of work items created so far and
is order by Update On column in descending order. At the bottom of the list “Create Work item” button allows creating a new work item. | VODKB-200723-160306.pdf |
a2766fe12a3e-0 | 189
Assign config flow work item to a different user
From work items list, click on the Assigned To user of the work item to be reassigned to a different user.
This opens a popup window and allows selection of users who can be assigned a work item. Users with Manager and User privileges are
shown the list of users under “Assign to” drop down. Optionally, you can provide notes which will be visible to the user once the work item is
opened.
Only work items with “In Progress” status can be assigned. | VODKB-200723-160306.pdf |
a29df3c103af-0 | 190
Discard config flow work item changes
If the changes in the work item are no longer required, all those changes can be discarded by using Delete icon in work items list. Delete
icon is disabled once the work item status is changed to ‘Committed to Release’.
A confirmation dialog will be shown to user as shown below.
Clicking on Yes button removes all changes done in the work item and work item will be removed from the list.
This feature removes the work item and all its changes. Please do not use this option if only a particular Business Config/Bundle Event
NTID Map/Events changes have to be reverted out of many items In Edit list. For this requirement, consider usingRollback Changes | VODKB-200723-160306.pdf |
4a3491bddff4-0 | 191
See Artifacts in edit
When the work item is opened, the landing page shows the Business Config/Bundle Event NTID Map/Events in Edit. All items changed in
this work item will be added to In Edit list. This list is available in landing page.
Below is the list of Business Config in landing page.
Below is the list of Bundle Event NTID Map in landing page.
Below is the list of Events in landing page. | VODKB-200723-160306.pdf |
915bd42c6c26-0 | 192 | VODKB-200723-160306.pdf |
a70a61ed4a8b-0 | 193
Manage Config Flow Artifacts
Business Config :
Click on ‘Manage Business Config’ button to navigate to the business config screen.
Bundle Event NTID Map :
Click on ‘Manage Bundle Event NTID Map’ button to navigate to the bundle event NTID map screen.
Events :
Click on ‘Manage Events’ button to navigate to the events screen.
Upload and download will be based on the selection from the dropdown below the upload button. | VODKB-200723-160306.pdf |
3dc8a896f6e9-0 | 194
Select any record from the table to view the details.
Save : It allows to save the changes of selected record.
Clear : It allows to clear the selected record.
Clone : It allows to clone the selected record to create a new record.
Download : It downloads the unlocked records along with the items in edit of an artifact.
Upload : It allows to upload the data in bulk. The modified data will be added to in edit list and locked with the work item.
Locked Message : When the selected record is locked within the other work item, message will be displayed and save button will be
disabled.
Click on ‘Back to Landing page’ to navigate to the landing page. | VODKB-200723-160306.pdf |
58a3408edffd-0 | 195
Rollback Changes
If all changes in work item are not required, one could Discard config flow work item changes . Sometimes it may be necessary to
remove one of the Business Config/Bundle Event NTID Map/Events from the work item as the changes are no longer required for a given
Business Config/Bundle Event NTID Map/Events. Restore feature allows rolling back changes done for a given Business Config/Bundle
Event NTID Map/Events. The Restore Icon in Landing Page performs Rollback.
When Restore is invoked for an Business Config, changes done to the particular entity will be rolled back to their original values present at
the time of creating the work item. Similar icon is available for Bundle Event NTID Map/Events also.
Below is for Events Screen
Restore action cannot be undone. All changes done for the Business Config/Bundle Event NTID Map/Events will be removed from work
item. | VODKB-200723-160306.pdf |
23eb3e945c2c-0 | 196 | VODKB-200723-160306.pdf |
08d6093d9928-0 | 197
Push Artifact changes to Dev2
Landing Page of the work item has a button to Push changes to Dev2 environment.
Push from within work item ensures that only Business Config/Bundle Event NTID Map/Events modified within the work item are updated in
Dev2 (Delta Push). | VODKB-200723-160306.pdf |
7744122246fb-0 | 198
Assign work item to Manager
Clicking ‘Show Merge View’ button performs comparison and navigates to the screen shown below.
This page gives an option to choose Manager from list of available users with Manager access in PM Tool portal. Choose manage from
dropdown and Submit using the ‘Ready for Release’ button at the bottom of the screen. The work item status changes to ‘Ready For
Release’ and will be routed to the Manager. | VODKB-200723-160306.pdf |
b34071afac78-0 | 199
Approve config flow work item
When work item changes are complete, they are assigned to Manager. The status of the work item will be set as “Ready for Release”.
These items are available for Manager to review and approve changes.
Below screen appears when a ‘Ready for Release’ work item is opened from work items list.
Click on Show Merge View button to view the changes made in the work item.
Click on Review button which navigates to the below screen. | VODKB-200723-160306.pdf |
3468bd6125e4-0 | 200
Changes can be approved by selecting ‘Give Release Version’ and by providing a Release Version. Optionally Review Comments can be
provided as notes for self. Clicking on Submit button at the bottom of the screen changes the status of the work item to ‘Assigned to
Release’.
If any further changes are needed to be complete before approval, work item can be returned back to developer by selecting ‘Return to
Developer’ and providing Review Comments. In this case, Review Comments are mandatory. | VODKB-200723-160306.pdf |
40cc3fc2938b-0 | 201
Once submitted by clicking the Submit button at the bottom of the screen, work item is returned to the developer with ‘In Progress’ status.
Review Comments provided by the Manager will be visible in the Landing Page as shown above | VODKB-200723-160306.pdf |
ae60f4d8a1d5-0 | 202
Change 'Assigned to Release' config flow work item
Work items in ‘Assigned to Release’ cannot be edited by users. Work item should be returned to user by Manager. This changes the status
to ‘In Progress’ and now user can edit the work item like any other in progress work item. | VODKB-200723-160306.pdf |
4b7dc2080557-0 | 203
Pull in Config Flow
Pull Baseline changes is available in the landing page.
Click on the button which basically pulls all the changes from the latest baseline version to the work item except the changes related to in
edit list items. Pull completed message will be displayed below the button once the pull is successful.
Pull icon will be displayed as below only after pull baseline changes was done. Icon will be visible if there are any changes to in edit list
entities when compared to pull baseline changes action.
Click on pull icon to view the changes from the latest baseline version. | VODKB-200723-160306.pdf |
e4325731def3-0 | 204
Discard and Prefer Branch option will be available in order to keep the work item changes as is without pulling from the baseline version.
Pull icon will be available until all the changes related to that entity are propagated to the work item. | VODKB-200723-160306.pdf |
c2fb7510bec9-0 | 205
PMT - Test Cell Management
Navigate to Artifacts menu and select Test Cell Management which displays below screen.
Once Test Group value is entered, two default test cells are populated as below and test cells range should be from 1-100.
Cell Code is generated in sequential order with test group name. Initial value of a test cell should be equal to Final value of previous test
cell plus(+) one.
Initial value for the first test cell and Final value for the last test cell are disabled.
Delete option is not available for first test cell and Add/Delete options are not available for last test cell as above.
Add and Delete options are available for the other test cells as below.
In download, each test cell for a test group will be shown as individual row as below. | VODKB-200723-160306.pdf |
2cf14013ed70-0 | 206
In upload, user can create/update/delete a test cell for a test group.
To add a test cell for a test group, ID should be empty and have to provide test group to which test cell have to be mapped.
To delete a test cell for a test group, have to remove the row from the file. | VODKB-200723-160306.pdf |
9157811ef807-0 | 207
PMT - Channel Management
Channel management changes are made in Channel and Treatment To Variation screens. | VODKB-200723-160306.pdf |
596a9526e10c-0 | 208
Channel Screen
Select the branch from “Manage Version” screen and then select “Artifacts” from Home dropdown to navigate to Channel screen.
Select Channel from Artifacts menu which opens channel screen as shown below.
Select an existing channel from grid or create a new one and update Social Hour Start and Social Hour End fields. | VODKB-200723-160306.pdf |
9fca846d0147-0 | 209
The format for Social Hour Start and Social Hour End should be HH:MM. | VODKB-200723-160306.pdf |
8984081ec7e1-0 | 210
Treatment To Treatment Variations Screen
Select Treatment To Treatment Variations from Artifacts menu which opens Treatment To Treatment Variations screen as shown below.
When Social Hour Start and Social Hour End fields are configured in Channel screen, Channel Management section will be available as
below.
Social Hour Start and Social Hour End values from Channel screen will be displayed and can be overridden at treatment to treatment
variations level.
‘Vodafone’ is default value for Sender Alias.
'Medium - 5' is default value for Priority.
Throttle Limit will be set to -1 when Unlimited Throttle is set to true. | VODKB-200723-160306.pdf |
bb9aa56aa5e2-0 | 211
PMT - TradeIn
TradeIn menu will be accessible only to the users who has VFUKCatalogue:TradeInUser or VFUKCata:TradeInUser access group.
For creation of TradeIn version, please refer Manage Versions - Vodafone - Confluence (atlassian.net)
When a version created with TradeIn release is pushed, only WBWDeviceMultiplierMatrix datatype will be updated.
When a full catalogue version is pushed, WBWDeviceMultiplierMatrix will be pushed along with other decision datas and datatypes. | VODKB-200723-160306.pdf |
824fac957817-0 | 212
WBW Device Multiplier Matrix
Select TradeIn menu and WBW Device Multiplier Matrix artifact which displays below.
Unique Validation : FromDevice, ToDevice, MultiplierType, TransactionType, TypeOfCustomerDoingTradeIn, StartDate and EndDate.
Below are the list of fields available :
ID : will be empty if new or will have a BNA id for each record.
FromDevice : text property and mandatory and accepts comma separated values.
ToDevice : text property and mandatory and accepts comma separated values.
MultiplierType : text property and mandatory. Below are the LOV :
Static/Bonus : Grade A-Z properties will accept values upto two decimal places.
Multiplier : Grade A-Z properties will accept integer values from zero to positive.
Any one of the Grade value should be populated.
TransactionType : text property and mandatory. Below are the LOV :
Small-Business, Consumer, Sole-Trader, Small-SME, Regional , Major
TypeOfCustomerDoingTradeIn : text property and mandatory and it accepts Comma separated values. Below are the LOV :
New, Upgrade, FlexiUpgrade, Adhoc, ADDITIONALLINE
Enabled : boolean property which accepts true/false.
Override : boolean property which accepts true/false.
StartDate : date time property and mandatory.
EndDate : date time property and mandatory. End date should be greater than start date.
Download : It downloads all the data available in selected catalogue version.
Upload : It allows to upload the data in bulk.
Clicking on upload button navigates to the below screen. | VODKB-200723-160306.pdf |
d37d5c616790-0 | 213
Upload Type has two options:
Incremental : Allows to create and update the entities.
Choose the downloaded file and click on upload which displays success message in case of no validation errors.
On submitting the page will navigates to the below screen which displays upload successful message. | VODKB-200723-160306.pdf |
4c08d54e6896-0 | 214
Click on Finish button.
Full : Allows to create, update and delete the entities.
Choose the downloaded file and click on upload which displays success message in case of no validation errors.
Click on submit to view the modified records as below. | VODKB-200723-160306.pdf |
0df39000dd81-0 | 215
On submitting the page navigates to the confirmation page which enters the path to delete the unlocked offers which are not available in the
uploaded file.
Click on Next which displays the entities that are deleting. | VODKB-200723-160306.pdf |
dd74ed58a40e-0 | 216
Next button navigates to the below delete confirmation page.
On submitting the page updates and deletes will be committed and displays the uploaded and deleted summary as below. | VODKB-200723-160306.pdf |
2e8d42e6fbb6-0 | 217
Click on Finish.
Push : The Unique Combinations of FromDevice, ToDevice, MultiplierType, TransactionType, TypeOfCustomerDoingTradeIn, StartDate
and EndDate will be pushed as different rows. | VODKB-200723-160306.pdf |
ad6bbdb814d6-0 | 218
Home
Home screen will be displayed as soon as user login. All draft and approved catalogue versions will be available as shown below. | VODKB-200723-160306.pdf |
33fa6ecd2dad-0 | 219
Manage Versions
User can create a catalogue version by navigating to Manage versions where all draft versions will be available. 'Open' link will be enabled
if the version is assigned to the logged-in user otherwise disabled.
Click on 'Create Branch' to create a new catalogue version which navigates to below screen.
Provide Catalogue Version and Comments then click on Submit to create new catalogue version.
Patch Release : A patch version will be created on selection of patch release which allows user to only update offer related artifacts.
TradeIn Release : A patch version will be created on selection of trade in release which allows admin user to modify
WBWDeviceMultiplierMatrix along with all artifacts.
For TradeIn user, TradeIn Release will be default selected and disabled as below. Only TradeIn menu is available for TradeIn user. | VODKB-200723-160306.pdf |
2c9329ffc9df-0 | 220 | VODKB-200723-160306.pdf |
7c96c1e817f2-0 | 221
Compare Versions
Navigate to Compare Versions menu to compare two catalogue versions. Select Compare Version ID and Compare To Version ID which
displays the screen as below. | VODKB-200723-160306.pdf |
e4c5ec6420c0-0 | 222
Push
Navigate to Push menu to push a catalogue version to target environment. Select App Name, Environment, Version ID and click on Deploy
Version button.
Click on Refresh button to get the latest status of push.
Push Audit Details displays all the push history. Pushed Artifacts will show successfully updated targets and Failed Artifacts will show the
failed targets.
Push will update all the respective decision data's and datatypes with the catalogue version data. | VODKB-200723-160306.pdf |
78f4aba05767-0 | 223
Assign
Assign menu will be available when draft catalogue version is selected. Click on Assign menu to assign a catalogue version to a particular
user.
Select Assign to option and Operator then click on Assign button which assigns catalogue to selected operator.
All the users who have access to application are available in operator selection. | VODKB-200723-160306.pdf |
346143a7a48d-0 | 224
Merge
Select the version which has to be merged to baseline version and click on Merge menu.
Branch version data will be compared with the latest approved baseline version and displays the changes as below.
Prefer Trunk checkbox will be available only when the record is updated in approved baseline version. Selecting prefer trunk will not merge
the changes that are made in branch version.
Selecting discard checkbox will not merge the changes that are made in branch version. | VODKB-200723-160306.pdf |
d35313fb3468-0 | 225
If a record is deleted from branch, it will be highlighted with cross mark in red that deletes the record from new baseline version as well after
merge.
If discard checkbox is selected, the record will be restored from approved baseline to new baseline after merge.
Click on Merge button to merge the changes.
A new temporary version will be created to validate, validation errors will be displayed if there are any errors otherwise displays below
screen. | VODKB-200723-160306.pdf |
3805f9eaec78-0 | 226
Provide the baseline version to create and click on submit button which merges all the changes from branch to given baseline version and
displays below confirmation page.
Click on Close button which navigates to assign page where baseline version can be assigned to any other user or submit to manager for
approval as below.
Once it is submitted to approval, baseline version is updated with Review (R) status and screen will be navigated to review page as shown
below. | VODKB-200723-160306.pdf |
6dabfcce9b76-0 | 227
Manager has an option to compare the changes with any other versions before approving.
If the manager selects Approve option and do submit, version will be approved and will not be available for further changes.
If the manager selects Reject then version will be updated to Draft ( D) status and will be available to continue with the further changes.
Manager can assign the trunk to any user when it is rejected. | VODKB-200723-160306.pdf |
e6c0918d7f08-0 | 228
Pull
Select the version into which the selected version data to be pulled and click on Pull menu.
User can pull the changes from any draft branch version and approved baseline version.
Click on Show Changes button of any version from which the data to be pulled.
Selecting discard checkbox will not pull the changes that are made in selected version.
If a record is deleted from selected version, it will be highlighted with cross mark in red that deletes the record from current version as well
after pull.
If discard checkbox is selected, the record will not be deleted from current version after pull.
Click on Pull button to pull the changes.
A new temporary version will be created to validate, validation errors will be displayed if there are any errors otherwise displays below
confirmation page. | VODKB-200723-160306.pdf |
762bd7b67652-0 | 229
Click on Close button which navigates to home page | VODKB-200723-160306.pdf |
e27548e7c76d-0 | 230
ChangeHistory
Navigate to Change History menu where the history of all catalogue versions will be displayed as shown below. | VODKB-200723-160306.pdf |
6c34d9e5c5e7-0 | 231
Handover Actions
Select Template menu and Handover Actions artifact which displays below.
Unique Validation : Action ID
Action ID : Text input and mandatory.
Action Type : Text input and mandatory. Saved action types will be available as possible values for next record.
Action Attributes : Mandatory. Attributes are sourced from action attributes screen.
Template Attributes : Optional. Attributes are sourced from template attributes screen.
Click on 'Add Attribute' in respective action/template attributes section to add action/template attribute to a handover action.
Action type 'Video' has static action attributes which cannot deleted as shown below. We can add more action attributes to the same
handover action.
Below section displays when we click on attribute. Section will be same for action attributes and template attributes. | VODKB-200723-160306.pdf |
5455adf7110f-0 | 232
Name : mandatory and will be disabled once it is saved for a handover action.
Default Value : displays default value provided at attribute level in read only.
Override : enable override flag to override the default value at handover action level.
Value : visible only when override is true to enter the overridden value.
Editable : enable editable flag to update the value at T2TV.
Click on delete icon to delete attribute.
Click on 'Update and Close' button to update the data. | VODKB-200723-160306.pdf |
a266e5c28032-0 | 233
Opti and Landing process
Opti during Landing :
User should work on branch and shouldn't merge to a baseline
Cannot use work items
Can push branch to respective release environments
Any new branch creation will be created on top of latest landing baseline, not on top of previous Opti baseline
Landing :
User should have access to VFUKLanding access group for purple view
User has to pull the latest Opti changes into Landing branch and merge to a baseline
Can use work items and package them to a baseline
Can push only to environments which has PM Push landing access
Opti has to continue to work on 3.7.x branch version until production is uplifted to landing release
Landing can do it's own changes and have to pull the Opti changes to a branch then merge to baseline where all Landing and Opti
changes will be available in new baseline
Once Opti is uplifted then changes can be done in Opti application and can perform merge/pull to create baseline in Opti | VODKB-200723-160306.pdf |
984bb2844b9b-0 | 234
PM Tool Access Groups
Below are the list of access groups available in PM Tool.
Administrators - user will have access to all functionalities
Managers - user will have access to all functionalities
CommercialManager - user will have access to only few Upgrades screens in Artifacts menu and other functionalities
ReleaseManager - user will have access to approve baseline version push(Immediate/Scheduled) from flows along with all other
functionalities
PrivilegedUser - user will have access to delete records in screens( Offers/Treatments…) along with all other functionalities
User - user will not have access to create branch. A manager has to create and assign to user to work on the catalogue but user will
have all other functionalities
ReadOnlyUser - user can view the pm tool in read only mode, cannot work on catalogue
TradeInUser - user will have access only to Home and TradeIn menu
AOSUser - user will have access to AOS menu in Artifacts along with other artifacts and functionalities. User cannot edit Source in
SourceConfig artifact
AOSAdmin - user will have access to AOS menu in Artifacts along with other artifacts and functionalities. User can edit Source in
SourceConfig artifact
Note : all functionalities = version creation/catalogue updates/merge/pull/push/flows | VODKB-200723-160306.pdf |
dd7ce8e7c278-0 | 235
MBB Configuration
Band Management :
Range Types MBBDeviceNetMafBanding and MBBSimNetMafBanding are added as part of 4.03 and 4.04
Handset :
DeviceType attribute should have Data Device value
New DeviceCategory (Short Text) attribute has to be created
When DeviceType is Data Device then DeviceCategory data will be downloded for VADR | VODKB-200723-160306.pdf |
81c193201cb7-0 | 236 | VODKB-200723-160306.pdf |
ad03251358e8-0 | 237
PM Tool Screens | VODKB-200723-160306.pdf |
34fba427c8f1-0 | 238
HBB MAF Band
HBB MAF Band will be available under Upgrades → Band Management
Process Type : Mandatory and unique with Tier/Threshold possible values in dropdown
Each process type can have multiple process type values
Plan Type : Mandatory and source from 'PlanType' product attribute
MAF Type : Mandatory and user input
Lower Boundary : Mandatory and accepts decimal
Upper Boundary : Mandatory and accepts decimal
Plan Type and MAF Type are combination unique for a Process Type
Data will be pushed to HBBMAFBands decision data | VODKB-200723-160306.pdf |
3375b2ba8ed0-0 | 239
HBB Pre To Post MAF Threshold
HBB Pre To Post MAF Threshold will be available under Upgrades → HBB
Unique : HBBSubscriptionLifeCycleBand, ApplicableChannel, ThresholdName,
ChurnThresholdType/MAFThresholdType/PlanThresholdType and CampaignType
HBB Subscription Life Cycle Band : Mandatory and source from ‘HBBDiscountLifeCycleBand’ range type in BandManagement screen
Applicable Channel : Mandatory and source from Channel screen
Threshold Name : Mandatory and ChurnPropensityBand/PreUpgradeMAFBand/PreUpgradePlanType are possible values
Campaign Type : User can enter data and same will be available for selection
Threshold Value : Integer
Churn Threshold Type : Available and mandatory for ChurnPropernsityBand ThresholdName. Source from
ModelPropensityToRangeMapping screen which has Model Id '7'
MAF Threshold Type : Available and mandatory for PreUpgradeMAFBand ThresholdName. Source from
HBBMAFBand screen which has Process Type ‘Threshold’
Plan Threshold Type : Available and mandatory for PreUpgradePlanType ThresholdName. Source from
‘PlanType’ product attribute
Data will be pushed to PreToPostMAFThreshold decision data | VODKB-200723-160306.pdf |
d135b813e110-0 | 240
HBB Tier Discount
HBB Tier Discount will be available under Upgrades → HBB
Unique : PlanType, MAFBand and ApplicableChannel
Plan Type : Mandatory and source from ‘PlanType’ product attribute
MAF Band : Mandatory and source from HBBMAFBand screen which has Process Type ‘Tier’ and based on PlanType value selected
Applicable Channel : Mandatory and source from Channel screen
Discount : Integer accepts zero and positive
Data will be pushed to DiscountByPlanType decision data | VODKB-200723-160306.pdf |
257d16070d2f-0 | 241
HBB Technology
HBB Technology will be available under Upgrades → HBB
Unique : Technology, PlanTechnology and Applicable Channel
Technology : Mandatory and source from ‘Technology’ product attribute
Plan Technology : Mandatory and user input
Applicable Channel : Mandatory and source from Channel screen
Description : User input
Enabled : Boolean
Data will be pushed to HBBTechnology decision data | VODKB-200723-160306.pdf |
349a6f7e758c-0 | 242
HBB Retention Discount
HBB Retention Discount will be available under Upgrades → HBB
Unique : LifeCycleBand, ChurnPropensity/CampaignType and ApplicableChannel
Life Cycle Band : Mandatory and source from ‘HBBDiscountLifeCycleBand’ range type in BandManagement screen
Churn Propensity/Campaign Type : User can enter data and same will be available for selection. Model Id ‘7' data from
ModelPropensityToRangeMapping screen will be available along with 'All’ for selection
Applicable Channel : Mandatory and source from Channel screen
Retention Discount : Integer accepts zero and positive
Post Contract Length : Integer accepts zero and positive
Data will be pushed to RetentionDiscount decision data | VODKB-200723-160306.pdf |
8a67ccb0101f-0 | 243
HBB Plan Prioritisation
HBB Plan Prioritisation will be available under Upgrades → HBB
Unique : LifeCycleBand, ChurnPropensity/CampaignType, ApplicableChannel and PlanTechnology
Life Cycle Band : Mandatory and source from ‘HBBPriorityLifeCycleBand’ range type in BandManagement screen
Churn Propensity/Campaign Type : User can enter data and same will be available for selection. Model Id ‘7' data from
ModelPropensityToRangeMapping screen will be available for selection
Applicable Channel : Mandatory and source from Channel screen along with ‘All’
Plan Technology : Mandatory and source from ‘Technology’ product attribute
Plan Price Order : Mandatory with Ascending/Descending possible values
Plan Type Order : Mandatory with Ascending/Descending possible values
Hero Plan ID1 : Mandatory and source from Tariff screen along with ‘CurrentPlan’ and ‘N/A’ values
Hero Plan ID2 : Mandatory and source from Tariff screen along with ‘CurrentPlan’ and ‘N/A’ values
Data will be pushed to HBBPlanPrioritisation decision data | VODKB-200723-160306.pdf |
01acef0f13e3-0 | 244
HBB Plan Eligibility Management
HBB Plan Eligibility Management will be available under Upgrades → HBB
Unique : FromPlanBand, ToPlanBand, FromProductLevelBand, ToProductLevelBand, FromPlanType, ToPlanType, HBBLifeCycleBand and
ApplicableChannel
From Plan Band : Mandatory and source from ‘PlanBand’ product attribute
To Plan Band : Mandatory and source from ‘PlanBand’ product attribute
From Product Level Band : Mandatory and source from ‘ProductLevelBand’ product attribute
To Product Level Band : Mandatory and source from ‘ProductLevelBand’ product attribute
From Plan Type : Mandatory and source from ‘PlanType’ product attribute
To Plan Type : Mandatory and source from ‘PlanType’ product attribute
HBB Life Cycle Band : Mandatory and source from 'HBBEligibilityLifeCycleBand' range type in BandManagement screen
Applicable Channel : Mandatory and source from Channel screen
Is Exclude : Boolean
Data will be pushed to EligibleHBBPlans decision data | VODKB-200723-160306.pdf |
a0e231c4ca5d-0 | 245
BandManagement
Band Management will be available under Upgrades → Band Management
Range Type : Mandatory and unique
Each range type can have multiple range type values
Range Name : Mandatory and user input
Band ID : Mandatory and integer
Description : Mandatory and editable only for HBB bands
BDCModelID : Mandatory and editable only for Churn band
Start Value : Mandatory and accepts positive integer
End Value : Mandatory and accepts positive integer
RangeName and BandID are individual unique for a Range Type
Data will be pushed to RangeMapping decision data | VODKB-200723-160306.pdf |
aeaa7582e264-0 | 246
SegmentOf1 Discount
Segment Of 1 Discount will be available under Upgrades → Discount Management
Discount Strategy Name : Mandatory and unique
Cohort : Mandatory and source from Cohorts screen which has ‘Segmentof1’ cohort type
Valid From Date : Mandatory
Valid To Date : Mandatory
Discount : Mandatory and accepts zero and positive integer
Channel : Mandatory and source from Channel screen
Team : Mandatory multiselect and source from DivisionMapping screen
Tariff Codes : Mandatory multiselect and source from Tariff screen
Data will be pushed to SegmentOf1DiscountStrategy decision data | VODKB-200723-160306.pdf |
303318147fd8-0 | 247
Cohorts
Cohorts will be available under Upgrades → Cohort Management
Cohort Name : Mandatory and unique
Cohort Start Date : Default to current date time
Cohort End Date : Non mandatory
Cohort Type : Mandatory with Commercial/Segmentof1/TradeIn possible values
Team : Multiselect with source from DivisionMapping screen
Is Cohort Active : Boolean with default to true
Add On Product Codes : Multiselect with source from AddOn screen
Tariff Product Codes : Multiselect with source from Tariff screen
Tariff Group : Source from TariffGroup screen
Star Rating : 1/2/3/4/5/6 are possible values
Tariff Discount Product Codes : Multiselect with source from Discount screen
Tariff Discount Flag : Boolean with default to true
Customer Type : Multiselect with PaymSIMO/PaymHandset/PaymLoan/MBBDevice/MBBSIMO possible values
Is Multi CTNs : True/False are possible values
From Contract Start Date : Date time
To Contract Start Date : Date time
From Contract End Date : Date time
To Contract End Date : Date time
Customer Intent : Source from Intents screen which has IsIntentCohort true | VODKB-200723-160306.pdf |
9806ef386036-0 | 248
Customer Intent Confidence Score : Low/High are possible values
Acquisition Channel : Static data
Most Used ISP : Static data
Last Seen Handset Manufacturer : Static data
Last Seen Handset Model : Static data
Is First Upgrade : True/False are possible values
Customer Life Cycle ID : Multiselect with source from ‘Customer Lifecycle Band’ range type in BandManagement screen
Is 3G Customer : Boolean
Upgrade Journey : User can enter data and same will be available for selection along with MobileBroadBand and Mobile Service possible
values
Three Month Average : Source from ‘Average 3M Data in GB Banding’ range type in BandManagement screen
Total Data Band ID : Multiselect with source from ‘Total Data Band’ range type in BandManagement screen
Churn Band : Multiselect with source from ‘Churn band’ range type in BandManagement screen
SIMO S15 Net MAF : Available when CustomerType has ‘PaymSIMO’. Multiselect with source from ‘S15 Banding-SIM’ range type in
BandManagement screen
SIMO Net MAF : Available when CustomerType has ‘PaymSIMO’. Multiselect with source from ‘Sim Net MAF Banding’ range type in
BandManagement screen
Handset S15 Net MAF : Available when CustomerType has ‘PaymHandset’. Multiselect with source from ‘S15 Banding - Handset’ range
type in BandManagement screen
Handset Net MAF : Available when CustomerType has ‘PaymHandset’. Multiselect with source from ‘Handset Net MAF Banding’ range
type in BandManagement screen
Data will be pushed to CustomerCohorts decision data | VODKB-200723-160306.pdf |
51bb35f9afdc-0 | 249
Source Config
Source Config will be available under AOS. User should have AOSAdmin or AOSUser access to view the screen
Source : Mandatory and unique. User should have AOSAdmin access to modify Source field. 'Default' source will not be modified
Rank : Integer accepts positive | VODKB-200723-160306.pdf |
7279a7f6b827-0 | 250
Product Config
Product Config will be available under AOS. User should have AOSAdmin or AOSUser access to view the screen
Product Id : Mandatory and unique. Source from AddOn and Discount screen.
Priority : Mandatory with High - 1/Medium - 5/Low - 10 possible values. Medium - 5 is default value
Enabled : Boolean
Each Product Id can have multiple sources
‘Default’ source and other source are mandatory for a Product Id
'Default' source cannot be deleted
Source : Mandatory multiselect
Each source will have below fields :
Start Date : Date time
End Date : Date time
Hour Window Start : Time in HH:MM format
Hour Window End : Time in HH:MM format | VODKB-200723-160306.pdf |
aa7ded23860e-0 | 251
S15 Same Or Higher
S15 Same Or Higher will be available under Upgrades → Recommendation Management
Unique : FromCustomerType, ToCustomerType, RecommendedDeviceStatus, ContractEndDateFrom, ContractEndDateTo and
CurrentDeviceStatus
From Customer Type : Mandatory with PaymSIMO/PaymHandset/PaymLoan/MBBDevice/MBBSIMO possible values
To Customer Type : Mandatory with PaymSIMO/PaymHandset/PaymLoan/MBBDevice/MBBSIMO possible values
Recommended Device Status : Mandatory with WithDevice/WithOutDevice possible values
Current Device Status : Available and mandatory for FromCustomerType ‘PaymLoan’ with WithDevice/WithOutDevice possible values
Contract End Date From : Mandatory and Integer
Contract End Date To : Mandatory and Integer
Team : Mandatory multiselect and source from DivisionMapping screen
Data will be pushed to UpgradeLifeCycleS15RuleConfig decision data | VODKB-200723-160306.pdf |
4ef455e49b8b-0 | 252
S15 Threshold
S15 Threshold will be available under Upgrades → Recommendation Management
Unique : SegmentStrategy, RecommendedPosition, FromProduct and ToProduct
Segment Strategy : Mandatory and source from SegmentStrategyMessageConfiguration screen
Recommended Position : Mandatory with 1/2/3 possible values
From Product : Mandatory with PaymSIMO/PaymHandset/PaymLoan/MBBDevice/MBBSIMO possible values
To Product : Mandatory with ToSIMO/ToHandset/ToSIMO30/ToMBBDevice/ToMBBSimo possible values
S15 Threshold Value : accepts double values
Applicable Channel : Mandatory and source from Channel screen
Data will be pushed to S15Threshold decision data
'Journey' button navigates to S15JourneyThreshold screen | VODKB-200723-160306.pdf |
6960be5a6bd9-0 | 253
S15 Journey Threshold
S15 Journey Threshold will be available through ‘Journey’ button in S15 Threshold screen
Unique : FromProduct and ToProduct
From Product : Mandatory with PaymSIMO/PaymHandset/PaymLoan/MBBDevice/MBBSIMO possible values
To Product : Mandatory with ToSIMO/ToHandset/ToSIMO30/ToMBBDevice/ToMBBSimo possible values
Apply S15 Threshold : Boolean
Data will be pushed to S15JourneyLevelThreshold decision data | VODKB-200723-160306.pdf |
36af3d3ad049-0 | 254
Offer
Offer will be available under Artifacts menu
Unique : OfferName and OfferID are individual unique
Offer Name : Mandatory and unique
Offer ID : Mandatory and unique
Description : Mandatory
Start Date : Mandatory
End Date : Mandatory
Business Purpose : Mandatory and source from BusinessPurpose screen
Business Segment : Mandatory and Source from BusinessSegment screen
Enabled : Boolean
Starting Propensity : Accepts decimal values
Offer Weight : Accepts decimal values
Offer Value : Accepts decimal values
Control Group Percentage : Integer accepts zero and positive
Pick Best Treatments Method : Dropdown with TreatmentRank/ChannelHierarchy/BestChannelModel
possible values
Payment Method : Dropdown available for BusinessPurpose ‘TradeIn’ with MonthlyCredit/BillCredit/BACS/Upfront/FlexiBillCredit possible
values
Max Best Treatments : Mandatory for PickBestTreatmentsMethod ‘ChannelHierarchy’
Apply Global Contact Strategy : Dropdown with Yes/No possible values
Mandatory : Dropdown with Yes/No possible values
Apply Offer Self Contention Strategy : Dropdown with Yes/No possible values | VODKB-200723-160306.pdf |