‘MANAGE VERSIONS’ SCREEN
This screen lists all the draft (not approved, work in progress) versions with an additional link ‘Open’, enabled, if the version is assigned to a
user. And a ‘Create Branch’ button.
Creating a version (branch)
A branch is always created from an approved trunk version.
Pull brings in changes from a trunk version that is approved/checked-in.


47
‘Create Branch’ button opens up above screen. Name the version, add comments. Clicking ‘Submit’ will create a branch version from the
latest approved trunk version.
As mentioned earlier, the ‘Open’ link for a user will be enabled if a version is assigned to the user. Clicking it selects the version.
Open a  version
After a version is created, in Main Menu > Manage Versions, user will see an ‘Open’ link. Clicking the link selects the version. A small pop
up on the upper right hand side of the screen.
A version that is not assigned can be selected from ‘Home’ screen.

‘COMPARE VERSIONS’ SCREEN
Comparing any two versions
Open link will be disabled if the catalogue is not assigned to the user making the changes.


48
OR


49
Select two versions and click ‘Compare’ button.
This will list all the artefacts that are different in the two versions + details of the changes in each version. This is only a read-only screen.
Click on the Artifact name and then click each entry for the artifact to see the differences.

‘PUSH’ SCREEN
Push a catalogue version to a Pega environment
Push updates the decision data and data types in the target environment with what is in the catalogue.
Select a version, target environment and click ‘Deploy Version’ button.
'Push Audit Details' section shows the push history. Latest push will show ‘In Progress’ at the start and clicking ‘Refresh’ button will refresh
the push status.


50
If a push has failed, as shown in the screenshot above, clicking on the row will show the artifacts that were pushed successfully and the
ones that failed.

‘CHANGE HISTORY’ SCREEN
Lists each change done. This is a read only screen.

For a version that is open and assigned to, user can see below additional menu items and screens.
‘ASSIGN’ SCREEN (MAIN MENU)
‘Assign’ button: To assign a catalogue version to another user.
‘Assign To Basket’ button: Work in progress for a future implementation, but the idea is to assign the version to a common area/basket so
that any user can pick it up. E.g. think of squad zones. Let the catalogue be assigned to ‘CrossSell’ squad so that any user working on that
squad can pick it up.

‘MERGE’ SCREEN
If the data in a branch is intended to go to Production, the branch must be merged to trunk for approval before pushing to Production.
Steps:
1) Select the branch version to be merged.
2) Click ‘Merge’ link on Main menu.
3) Before merging, best practice is to review the ‘Artifact Changes’ section that lists all the changed artifacts and relevant attributes, with the
branch and trunk value.
4) ‘Discard’ check box for an artifact will discard the branch changes i.e. will not be merged. E.g. if there are 10 new offers in branch but
now 3 not needed anymore, check ‘Discard’ for those 3 offers.Double check the target environment before pushing to avoid accidental push to Production.
A push will overwrite all local decision data changes that is done via PEGA designer studio as part of seed testing/local testing.


Best Practice: Although it can be done, a branch should NEVER be pushed to production directly. To maintain uniformity, it should be
merged to trunk first, before pushing to Prod. That way there is always a single version (trunk) that goes to production.


51
5) Also, for a specific attribute of an artifact, ‘Prefer Trunk’ checkbox gives the option of keeping branch or trunk value. E.g. in above
screenshot, for artifact Offer i.e. Tariff Migration, the attribute ‘Enabled’ has different branch and trunk values and if ‘Prefer Trunk’ is
checked, branch value will not be merged.
‘PULL’ SCREEN
To pull the data from an approved trunk version to a branch. This is useful when a trunk version has new data as the branch could have
been created earlier. So, pull the new data to branch for it to be up to date.
Steps:
1. Select the branch version
2. Click ‘Pull’ link on Main menu
3. Screen lists all the changed artifacts and relevant attributes with the branch and trunk value
4. For the next two steps, please understand that there is an artifact and then there are attributes for the artifact e.g. artifact =
SmartWatchOffer and artifact attributes e.g OfferValue, Enabled, StartDate etc.
5. ‘Discard’ check box is at artifact level and if checked pull will not bring in the changes from trunk for the whole artifact and keep branch
value.
6. ‘Prefer Branch’ check box is at artifact attribute level and if checked pull will not bring in the changes for that attribute only from trunk and
keep branch value.
WORKING ON A VERSION (ARTIFACTS MENU)
Once a version is opened/selected, click ‘Artifacts’ on the left hand side of the screen.
This will present all the artifacts of the catalogue with their screens.
Save, Clone button
For the first time, when there is no record for an artifact, screen will have empty fields. After entering data and comment, ‘Save’ button will


save the record. Some important fields will become disabled and cannot be changed.
Now for the next/new record, select an existing record and click ‘Clone’. All the fields are enabled, new data can be entered and ‘Save’ will
create this new record.
Some screens are for a specific functionality e.g. ‘Assisted Upgrade' and some are common e.g. 'Offer’.
Upload, Download button
All screens have the option of uploading all data at once from a csv using ‘Upload’ button. And ‘Download’ button, to download all data as
csv.


53
Proposition structure
PROPOSITIONS
Vodafone propositions are presented in a four-level structure. Let’s consider the NBA Batch functionality as an example to demonstrate this,
as below:
Offer e.g. SmartWatch
Offer Variation e.g. Android, Apple
Offer To Offer Variations e.g. SmartWatch-Android, SmartWatch-Apple
Treatment e.g. SmartWatch_Email, SmartWatch_SMS (Treatment is a combination of offer and channel)
Treatment Variation e.g. AndroidWatch, AppleWatch
Treatment To Treatment Variations: This is the combination of Treatment-TreatmentVar-OfferVar e.g. SmartWatch_Email-AndroidWatch-
Android, SmartWatch_Email-AppleWatch-Apple.
More information on how to create and add data to this heirarchy, along with details of other screens in PM Tool is detailed in following part
of the article.
Continued…


54
Intent related screens
Intent is the objective/purpose/wish of a customer. It is a combination of Level 1 and Level 2 intents. Example of an intent is Buy-Mobile,
Manage-Plan etc.
Level1 Intent
Select/Open a version > Artifacts > Screen: Level1 Intents
Step 1: Enter Level 1 intent name. This will be combined with Level 2 intent to give meaning to the actual intent.
Step 2: Enter comments, it’s mandatory.
Step 3: Click 'Save' button to save the record. Click 'Clear' button to clear and re-do before saving.
Level2 Intent
Select/Open a version > Artifacts > Screen: Level2 Intents
Step 1: Enter Level 2 intent name. This will be combined with Level 1 intent to give meaning to the actual intent.
Step 2: Enter comments.
Step 3: Click 'Save' button to save the record.


55
It is a good practice to keep an eye on the ‘Change History’ section at the bottom of each screen, just to keep track of the changes.

Intent
Intent is combination of Level 1 and Level 2 intents.
Select/Open a version > Artifacts > Screen: Intents
Data gets pushed to Pega Environment to Proposition Decision data: Pega Decision Data: Configure > Decisioning > Decisions >
Proposition Management > Heirarchy > NonPropositions > Intents
Also to decision data: IntentToBusinessPurpose.
Step 1: Select Level 1 intent (options presented are created in Level1 Intents screen)
Step 2: Enter numeric Intent Weight. Value is used in priority score calculation.
Step 3: Check box to enable/disable the intent.
Step 4: Enter BDC Model id. Required for model based intents. Based on the model id there are calculations for Intent confidence score
and Intent BDC Model propensity.
Step 5: Select Level 2 intent (options presented are created in Level2 Intents screen)
Step 6: Enter description of the Intent. Usually the actual intent name i.e. Level1Intent-Level2Intent e.g. Buy-Mobile.
Step 7: Enter BDC Model Multiplier. Required for model based intents. Value used in calculation of Intent BDC model propensity.
Step 8: Click on a business purpose in the ‘Available Business Purpose’ section to add to the intent. To remove it click the intent in ‘Existing
Business Purpose’ section. This step is pushed to a separate decision data: IntentToBusinessPurpose. Business purpose is applied to
intents with a ‘low’ confidence score.
Steps for ‘Comments’ and ‘Save’ are same for all screens. Thus not including these steps for the rest of the article.


56

Intent To Offer
This is one-to-Many mapping. An Intent can be  assigned to Multiple Offers . Select/Open a version > Artifacts > Screen: Intent To Offer
Data gets pushed to Decision Data: IntentToOffer.
Step 1: Select Intent (options presented are created in Intents screen).
Step 2: Select Offer to which intent needs to be linked. This is one-to-one mapping.
Intent Confidence Level Score
Confidence score for a confidence level is defined here. E.g. from below screenshot if an Intent passes the confidence level 1 rules, it is
assigned a score of 1. Similarly, other entries in the decision data could be ConfidenceLevel2 with score 20. So if an Intent passes
confidence level 2 rules, it gets a score of 20.
Select/Open a version > Artifacts > Screen: Intent Confidence Level Score
Data gets pushed to Decision Data: IntentConfidenceLevelScore.
Step 1: Enter Confidence Level name e.g. ConfidenceLevel1, ConfidenceLevel2 etc. Each confidence level has a set of rules that an Intent
needs to pass to get the score.
Step 2: Enter Confidence Score in whole number e.g 1, 21 etc.
Step 3: Make it Enabled by clicking the check box.
 pyName(UniqueID) =  Intent & Offer Name combination. This will allow to configure multiple offer for the same Intent in this decision
data.


58
Offer related screens
Offer is the proposition presented to customer after business eligibility rules are met.
Offer
Data gets pushed to Pega Environment to Proposition Decision data. Location: Configure > Decisioning > Decisions > Proposition
Management > Heirarchy > (relevant Business Purpose e.g. CrossSell) > Offers.
Navigate to PM Tool screen: Select/Open a version > Artifacts > Screen: Offer
Step 1: Offer Name: Enter meaningful name of the offer e.g. TariffMigration.
Step 2: Offer ID: Unique offer id.
Step 3: Description: Enter description of the offer.
Step 4: Start Date: Pick start date of the offer using the date picker component.
Step 5: End Date: Pick end date of the offer using the date picker component.
Step 6: Business Purpose: Select relevant business purpose. All business purpose entries created via ‘Business Purpose’ screen are
available in the drop down.
Step 7: Business Segment: Select relevant business segment. All business segment entries created via 'Business Segment; screen are
available in the drop down.
Step 8: Customer Segment: Select relevant customer segment. All customer segment entries created via ‘Customer Segment’ screen are
available in the drop down.
Step 9: Enabled: Check box to enable/disable offer.
Step 10: Starting Propensity: Enter a number, can be decimal e.g. 0.5, that is used in the priority score calculation. Also if no propensity is
returned by BDC model, value of starting propensity is used.
Step 11: Offer weight: Numeric value is used in priority calculation.
Step 12: Offer Value: Enter a number, usually a whole number, for offer value that is used in priority score calculation.


Step 13: Control Group Percentage: Numeric value without the percentage sign. For a value greater than zero, control group logic is
applied and in control group flag is set to Yes.
Step 14: Pick Best Treatments Method: Options presented are: ChannelHeirarchy, BestChannelModel, TreatmentRank. Pick best
treatment logic is appled based on this.
Step 15: Max Best Treatments: A numeric value determines the max best treatments (for email) for a parent offer that is used in parent
child bundling concept used in Batch NBA emails that displays more than one offer.
Step 16: Mandatory: Options: Yes, No. If an offer is madatory it should always be presented and must have a representation rate, step 20.
All mandatory offers are arbitrated separately from the non-mandatory ones.
Step 17: Apply Gloabl Contact Strategy: Options presented are: Yes, No. Based on the value contact strategy logic is applied.
Step 18: Apply Offer Self Contention Strategy: Options presented are: Yes, No. Based on the value offer self contention logic is applied.
Step 19: Apply Business Purpose Contact Strategy: Options presented are: Yes, No. Business Contact startegy should be applied only
for batch executions and it should be applied when ApplyBusinessPurposeContactStrategy is set to Yes.
Step 20: Representation Rate: How many days must elapse before an offer can be repeated. Valid values: Any value from -1, 0 or positive
integer). This value is used in offer self contention logic and compared to the number of days returned for a Selected or Pending response
from Pega Interaction History and Unica Campaign History.
Step 21: Fallow Period For Negative Response: How many days must elapse before an offer can be presented after it has been rejected


or is successful. Valid values: Any value from -1, 0 or positive integer). This value is used in offer self contention logic and compared to the
number of days returned for a negative response from Pega Interaction History.
Step 22: Fallow Period For Positive Response: Valid values: Any value from -1, 0 or positive integer). This value is used in offer self
contention logic and compared to the number of days returned for a positive response from Pega Interaction History.


contention logic and compared to the number of days returned for a positive response from Pega Interaction History.
Step 23: Propensity Attribute: This field is not mandatory and can be NULL. If populated, it should be the “key” name of ModelAttributes
JSON and the respective propensity value from ModelAttributes will be used for Propensity. Multiple “key” values are allowed on this field
which should be provided as comma (,) separated list. When multiple “key” is used, the respective Max propensity value will be used for
Propensity. If left blank, Propensity column from Model Score table will be used for Propensity.


59
Step 24: Propensity Source: Possible Values:
BDC: Indicates that the propensity will be sourced from a BDC model.
Default: StartingPropensity should be used as Offer Propensity. Default will work same as leaving it blank (i.e. not populated).
Step 25: Model Id: This field is displayed if PropensitySource is BDC.
Step 26:Priority Cutoff score: Enter any values for Priority Cutoff score,so that to select offer only when priority is more than cutoff score.
Step 27: To add a channel to the offer, click on it in the Available Channels section. To remove, click on it in the Existing Channels section.
Step 28: To add an execution mode to the offer, click on it in the Available Offer Execution Mode section. To remove, click on it in the
Existing Offer Execution Mode section.
Step 29: To add a rule to the offer, click on it in the Available Rules section. To remove, click on it in the Existing Rules section.
Step 30: Offer Expiry Interval : To add expiry interval to offer, select values from drop down Days, Months, Years, Set. To remove, select
‘Select’ from dropdown.
Step 31: Offer Expiry : To add offer expiry period to offer, put integer value for Days, Months, Years and select date from calendar for Set
options.
Step 32: FallowPeriodForOfferExpiryInterval : To add Fallow period for offer expiry interval to offer, select values from drop down Days,
Months, Years, Set. To remove, select ‘Select’ from dropdown. This will be enabled only after selecting value for Offer Expiry and Offer
Expiry Interval tabs.


Expiry Interval tabs.
Step 33: FallowPeriodForOfferExpiry : To add fallow period for offer expiry period to offer, put integer value for Days, Months, Years and
select date from calendar for Set options. This will be enabled only after selecting value for Offer Expiry and Offer Expiry Interval tabs.
 Please note rules added/removed in step 24 does not affect the actual rule implementations as this is for information only in the PM
Tool.


60

Offer Decision Mix
This is used in the logic that limits the the maximum offer(s) for an execution mode. Data gets pushed to Pega Environment to Decision
data. OfferDecisionMix
Navigate to PM Tool screen: Select/Open a version > Artifacts > Screen: Offer Decision Mix
Step 1: Select execution mode from drop down.
Step 2: Enter Decision Mix Context. GetNBA Execution Mode for IVR channel has 2 separate contexts - TradeIn and Standard IVR which
requires different MaxOffers configuration and hence DecisionModeContext has been added as new dimension for this configuration. This
can further to use such separation for all execution modes.
Step 3: Enter a number for Max Offers. Can have values: -1, 0 or any positive integer. Value of -1 means that offer decision mix logic for
max offers is not applied. Value 0 means no offers can pass through and a greater than zero value implies the number of offers that can
pass through for a particular execution mode.


61
Offer Variation
Represents the variation of an offer e.g. an offer is ExtraData, variations can be 1GB, 2GB etc.
Offer Variation
Data gets pushed to Pega Environment to Proposition Decision data. Location: Configure > Decisioning > Decisions > Proposition
Management > Heirarchy > (relevant Business Purpose e.g. CrossSell) > OffersVariations.
Navigate to PM Tool screen: Select/Open a version > Artifacts > Screen: Offer Variations.
Step 1: Enter offer variation name.
Step 2: Enter meaningful description.
Step 3: Pick start date using date picker component.
Step 4: Pick end date using date picker component.
Step 5: Check box to enable/disable.
Step 6: If Customer Interaction is checked rest of the fields in the section appear. If checked create customer interaction api is called to
send data to Siebel. Data in below steps 7 to 12 are as per requirements from Siebel.
Step 7: Priority options are: 1-ASAP, 2-High, 3-Medium, 4-Low.
Step 8: Catergy options are: Services, Buy, Recommendation, Account, Products, Billing, Leave, WebChat, Device Returned.
Step 9: Sub Category values are provided based on the category selected.
Step 10: Enter comments.
Step 11: Options are: Order raised, Quote Given, Information given, Call Dropped, Add/Remove Item, Fault Resolved.
Step 12: Enter customer interaction description.
Step 13: To add a rule, click on it in the Available Rules section to be added to Existing Rules and vice-versa to remove.

Offer To Offer Variations


Offer To Offer Variations
Data gets pushed to Pega Environment to Proposition Decision data. Location: Configure > Decisioning > Decisions > Proposition
Management > Heirarchy > (relevant Business Purpose e.g. CrossSell) > OfferToOfferVariations.


62
Navigate to PM Tool screen: Select/Open a version > Artifacts > Screen: Offer Variations.
Step 1: Offer Name: Select the offer for which the variation is. Offer ID is read-only and automatically populated.
Step 2: Offer Variation Name: Select the offer variation. Options provided here are created from the offer variation screen.
Step 3: Product Code: Enter product code, if there is needs to be a product code associated with the offer variation.
Step 4: Offer Dynamic Variable 1: Enter text, if there needs to be a customizable text for the offer variation (e.g. to be displayed in an
email or sms).
Step 5: Enabled: Check box to enable/disable.
Step 6: Rank: Enter a number as rank. Used to select the top offer variant.
Step 7: Propensity Attribute: This field is not mandatory and can be NULL. If populated, it should be the “key” name of ModelAttributes
JSON and the respective propensity value from ModelAttributes will be used for Propensity. Multiple “key” values are allowed on this field
which should be provided as comma (,) separated list. When multiple “key” is used, the respective Max propensity value will be used for
Propensity. If left blank, Propensity column from Model Score table will be used for Propensity.
Step 8: Propensity Source: Possible Values:
BDC: Indicates that the propensity will be sourced from a BDC model.
Default: StartingPropensity should be used as Offer Propensity. Default will work same as leaving it blank (i.e. not populated).
Step 9: Model Id: This field is displayed if PropensitySource is BDC.


63
Treatment related screens
Treatment is the combination of offer and channel. E.g. SmartWatch_Email, SmartWatch_SMS etc.
Treatment
Data gets pushed to Pega Environment to Proposition Decision data. Location: Configure > Decisioning > Decisions > Proposition
Management > Heirarchy > (relevant Business Purpose e.g. CrossSell) > category of treatments e.g. Email, SMS etc.
For sub channel related info selected here, data is pushed to decision data: TreatmentToSubChannels.
In PM Tool, select/Open a version > Artifacts > Screen: Treatment
Step 1: Select offer for whom treatment needs to be created.
Step 2: Select applicable channel e.g. Email, SMS etc.
Step 3: Select applicable sub channel if there exists a sub-channel for the main channel. Also, see the next section below - Sub Channel.
Step 4: Enter the exact offer name. _channel e.g. _Email will be automatically appended.
Step 5: Enter unique treatment id.
Step 6: Enter treatment description.
Step 7: Pick start date using date picker component.
Step 8: Pick end date using date picker component.
Step 9: Enter numeric value for weight, used in priority calculation.
Step 10: Check box to enable/disable the treatment.
Step 11: Displayed only for Email treatments. Represents number of max children meaning number of child treatments for the parent
treatment. This is used in pega bundling required for emails sent via Pega marketing that needs to display more than one offer. More info
next section - PEGA Email Bundling.
Step 12: If checked dedupe logic will be applied to the treatment.
Step 13: Enter a numeric value that depicts the percentage that falls in control group selection. Control group logic with be applied to this
percentage of treatments.


percentage of treatments.
Step 14: Numeric value for Contact list number.
Step 15: Rank of treatment in number used for prioritization logic.
Step 16: Click on a rule in ‘Available Rules’ section to be applied to the offer. It appears in the ‘Existing Rules’ section and vice-versa to
remove.
Some more fields are present in the screen which are displayed when a particular channel is selected.
For SMS: From ID: An id that usually represents the sender of the SMS.
For SMS: Social Hours: When checked, SMS will be sent to customer in pre-defined social hours.
For OutboundCC: Purge. Displayed only for outbound cc treatments. Text to Switch OBC purge files need to include any MSISDNs which
have subsequently recommitted to a new contract after the original request. Objective is to reduce unneeded calls being made.


64
ApplyTreatmentSelfContentionStrategy : If the value of ApplyTreatmentSelfContentionStrategy is yes, then contact policy feature at
treatment level is applied. Currently this feature is applicable only for IVR and App channels.
FallowPeriodForDismissedResponse : This field is to define the number of contention period days to be applied for dismissed outcomes
responses.
Sub Channel
In this section, click on an entry in ‘Available Sub Channels’ section to be applied to the treatment. It appears in the ‘Existing Sub Channels’
section and vice-versa to remove. E.g. below screen shows sub channels for OutboundCC channel. Similarly, AppPush channel has sub
channels e.g. InApp, Inbox, Push.
Sub Channel screen
Select/Open a version > Artifacts > Screen: SubChannel
Step 1: Select channel.
Step 2: Zip. For OutboundCC channel. If checked, outbound file will be zipped.
Step 3: Enter sub channel description.
Step 4: Apply Templates. Applies to IVR channel.
Step 5: Enter sub channel name.
Step 6: Encrypt. For OutboundCC channel. If checked, outbound file will be encrypted.


65

About PEGA Email treatment bundling
Email generated by Pega Marketing that displays more than one offer needs PEGA parent child bundling. Lets consider below cross sell
offers to be sent in the email.
MobileAddmobile
AddMobileSIMO
AddTablet
AddMobilewithhandset
AddSmartwatch
Then the parent child grouping for email treatment will be as follows:
MobileAddmobile_Email (Parent): This is a dummy treatment, required for bundling.
AddMobileSIMO_Email (Child)
AddTablet_Email (Child)
AddMobilewithhandset_Email (Child)
AddSmartwatch_Email (Child)
Similarly, there are treatments for other channels e.g. SMS, that does not need bundling.
The above grouping can be configured in the below screen.

Parent Child Treatments
Corresponding Pega decision data: ParentChildTreatments
In PM Tool, select/Open a version > Artifacts > Screen: Parent Child Treatments
Step 1: Bundle Parent Treatment: Select parent email treatment.
Step 2: Description: Enter description.
Step 3: Bundle Child Treatment: Add Child email treatment link click adds a text box to add a relevant child treatment.
Step 4: Rank: Possible Values - positive Integer, this indicates the default order of the child treatments for the parent.
Step 5: Delete: Click on the bin icon to delete a child treatment.


67
Treatment Variation
Represents the variation of a treatment e.g. for a treatment that is AddSmartwatch_Email, variations can be AppleSmartwatch,
AndroidSmartwatch etc.
Treatment Variation
Data gets pushed to Pega Environment to Proposition Decision data. Location: Configure > Decisioning > Decisions > Proposition
Management > Heirarchy > (relevant Business Purpose e.g. CrossSell) > TreatmentVariations.
Navigate to PM Tool screen: Select/Open a version > Artifacts > Screen: Treatment Variations.
Step 1: Enter treatment variation name.
Step 2: Pick start date using date picker component.
Step 3: Pick end date using date picker component.
Step 4: Check box to enable/disable.
Step 5: Enter weight in number, used to calcualte .pxPriority and then assign the value to dedupe score needed in dedupe logic.
Step 6: Enter treatment variation description.
Step 7: Enter value model in number, used to calcualte .pxPriority and then assign the value to dedupe score needed in dedupe logic.
Step 8: Value is used to select treatment variant based on BDC Model Data. BDC model will provide same value as this for mapping.
Step 9: To add a rule, click on it in the Available Rules section to be added to Existing Rules and vice-versa to remove.
Treatment To Treatment Variations (TTV)
Corresponding proposition decision data in Pega under each business purpose: TreatmentToTreatmentVariations (location: Pega
Designer Studio > Configure > Decisioning > Decisions > Proposition Management > Hierarchy > (relevant Business Purpose e.g.
CrossSell) > TreatmentToTreatmentVariations)
In PM Tool Select/Open a version > Artifacts > Screen: Treatment To Treatment Variations


In PM Tool Select/Open a version > Artifacts > Screen: Treatment To Treatment Variations
TTV is a combination of Treatment-TreatmentVariation-OfferVariation e.g. MobileAddmobile_Email-AdCons-OfferVariantDefault.
Step 1: Select existing treatment.
Step 2: Select existing offer variation.
Step 3: Check box to enable/disable.
No business rules are applicable at this level.


68
Step 4: Select existing treatment variation.
Step 5: Enter rank in number. Value used to pick top 1 treatment variant based on rank of all eligible treatment variants.
Step 6: Does the same functionality as the offer variation checkbox. Please check offer variation page Step 6 for more details. If checked,
calls create customer interaction api and sends data to Siebel.
Step 7: FUTList (Text) - Comma Separated Values of FUT Groups. Defines a list of customers who are flagged as FUT should only be
getting treatments flagged for testing. If a treatment is not flagged as FUT then the FUT call should not happen and logic not executed.
Step 8: Treatment Dynamic Attributes: See below:
For Adcons email, below treatment dynamic variables holds data for specific attributes of the email.
TreatmentDynamicVariable1 = EmailSubjectLine
TreatmentDynamicVariable2 = ClickThroughURL
TreatmentDynamicVariable3 = OfferHeader
TreatmentDynamicVariable4 = ImageURL
TreatmentDynamicVariable5 = EmailCopy
TreatmentDynamicVariable6 = EmailCopy1
TreatmentDynamicVariable7 = EmailCopy2
TreatmentDynamicVariable8 = NormalPrice
TreatmentDynamicVariable9 = UpfrontPrice
TreatmentDynamicVariable10 = Price
TreatmentDynamicVariable11 = Product codes for different treatment variants for Adcons handset offer.
TreatmentDynamicVariable12 = MobileImageURL
TreatmentDynamicVariable13 = Not used yet. Available for use.
TreatmentDynamicVariable14 = Not used yet. Available for use.
TreatmentDynamicVariable15 = Not used yet. Available for use.
TreatmentDynamicVariable16 = Not used yet. Available for use.
TreatmentDynamicVariable17 = Not used yet. Available for use.
TreatmentDynamicVariable18 = Not used yet. Available for use.
TreatmentDynamicVariable19 = Not used yet. Available for use.


TreatmentDynamicVariable19 = Not used yet. Available for use.
TreatmentDynamicVariable20 =  Not used yet. Available for use.
Below screen is same for Email, SMS, OutboundCC, InboundCC, Retail, DirectMail and WEB treatments.


69
Below is a snapshot of AppPush treatments.
For IVR, enter the SMS template in “Treatment Dynamic Variable1” field for PostNLCS - SMS Treatments.


70
T2TV Actions and T2TV Attributes
T2TV Actions
To Associate Actions With T2TV, first enable it in the Channel screen.
Step 1:  Add the outcomes as per the catalogue if it’s a new outcome.
Step 2: To create a new T2TV Actions in PM Tool, switch to Templates tab.


71
Step 3: Navigate to PM Tool screen: Action Attributes
             Add the attributes as per Offer Catalogue. Ex: DefelctionType, RecommendedRouting

Step 4: To Add Different Templates of Actions, navigate to PM Tool screen:  Actions.
            a) Enter the name of the Action Template.
            b) Add the required Attributes, which we need in the Template.
            c) Check the Editable Check Box, so that we can add values to that Attributes.


72

Step 5: To link Actions with T2TV, navigate to PM Tool screen: Treatment To Treatment Variations.
            a) Click on the Outcomes.
            b) Select the ActionID(Action Template) created in previous screen.
            c) Enter the values for Action Attributes as per offer catalogue.

T2TV Attributes
To Associate Attributes With T2TV, first enable it in the Channel and Subchannel screens.


73
Step 2: In order to create new T2TV Attributes in PM Tool, switch to Templates tab.


74
Step 3: To add the required attributes as per Offer Catalogue, navigate to PM Tool screen: Template Attribute.

Step 4: Navigate to PM Tool screen: Template.
             a) Enter the name of the Template (based on the Template Attributes). For Example for the template without MSG_ID in Attributes
we name it as IVR_PreNLCS_Template_No_MsgId.
                 A new template would be created only if the existing templates don’t include the required attributes provided in the Offer
Catalogue for the new T2TV Attributes.
             b) Select Channel and SubChannel.
             c) Add the Template Attributes as per Offer Catalogue.


75

Step 5: To link Attributes with T2TV, navigate to PM Tool screen: Treatment To Treatment Variations.
            a) Click on the SubChannel.
            b) Select the TemplateID (Template) created in previous screen.
            c) Enter the values for Template Attributes as per offer catalogue.


76
Control Group
What is Control Group ??
Bit more info about the control group percentage/selection field in the offer and treatment screens.
This step provides control for all relevant outbound treatments to be able to measure the marketing effectiveness of the treatment.
The treatments are not delivered to customer, but marked as "in Control Group" and stored in IH for reporting purpose.
This step is omitted for inbound treatments.
For Batch NBA, Control Group percentage value is set at ‘Offer’ level.
Offer screen > ‘Control Group Percentage’. Set value 1 to 100, without % symbol.
Steps:
Step 1: In the decisioning logic, generate random number in range 1 to 100.
Step 2: Not in control group if random number > ControlGroupPercentage
Step 3: In control group if random number <= ControlGroupPercentage
Step 4: For records in control group, only write to interaction history (IH) and do not perform any other action e.g. do not send the customer
an email or sms as intended by batch NBA process.
Step 5: For records not in control group, write to interaction history (IH) + perform actions e.g. send the customer an email or sms as
intended by batch NBA process.


77
Volume Constraint
Idea of volume constraint is to limit the number of records selected for Outbound call centre channel.
Value is set for outbound treatments e.g. SmartWatch_OutboundCC = 5000. In this case, only 5000 records will be selected if there are
more than 5000 records.
Select/Open a version > Artifacts > Screen: Volume Constraints
Step 1: Select outbound treatment
Step 2: Select sub channel
Step 3: Enter description
Step 4: Enter volume limit in number


78
Event
Event related screens
E v e n t s
This screen gives the ability to configure varying propostion data for event to intent mapping. It is an extension of the Intent screen.
Objective is to identify real time events and map them to existing intents using primary and secondary contexts.
Corresponding Pega decision data: EventToIntent
Step 1: Enter Primary context. This is mapped to the primary context coming in from real time context.
Step 2: Secondary context. This is optional and will be mapped to the primary context coming in from real time context.
Step 3: Event to an existing Intent mapping with the option to provide data source of the intent, confidence score and event recency in
hours which as per requirement is compared against the event timestamp.
Step 4: Add any other event attributes as required with an override check box which if checked will overriede that particular attribute coming
in the real time context with the default value.
When configuring IVR apptags, enter the apptag name in “Primary Context” field and follow the steps above.


79
For Tealium Events, enter the URL  in “Primary Context” field and follow the steps above.


80
Arbitration Control Parameters
Values defined here are used in calculation of priority score in strategy: CalculatePriority. The coefficient values when multiplied with the
weight of an entity can increase the value. E.g. screenshot below, the IntentWeightCoefficient e.g. with a value = 3, when multiplied to the
weight of an intent can increase the weight or keep it same if kept = 1.
Corresponding Pega decision data: ArbitrationControlParameters
Select/Open a version > Artifacts > Screen: Arbitration Control Parameters
Pushed to decision data: ArbitrationControlParameters
Step 1: Enter control parameter name.
Step 2: Enter control parameter value in number.


81
Configuration screens
About all configuration related screens.
Event Type Config
Values are pushed to a Pega data page. An example where values from this screen are used is ramp up logic.
An instance
Select/Open a version > Artifacts > Screen: Event Type Config
Step 1: Enter Event type.
Step 2: Enter sub event type for the event type.
Step 3: Enter number 0 to 1. 0 means the event functionality is not processed for the customer. 1 means processed for the customer.
Step 4: CIS flag.
Step 5: If checked, capture response functionality will be executed and record will be written to IH.
Step 6: If checked, event is processed else not.
Step 7: Process Event flag.
Step 8: Store Raw Event flag.

Bundle Event NTID Map
Select/Open a version > Artifacts > Screen: Bundle Event NTID Map
Step 1: Enter NTID.
Step 2: Enter NTID Weight in number.
Step 3: If checked, ntid is processed, else not.
Step 4: Enter NTID description.
Step 5: Release Rate: Used in ramp up logic. For a value 0, the functionality of that NTID is not served to customer. It is processed for a
value greater than 0.


82

Split Variant Percentage
Select/Open a version > Artifacts > Screen: Split Variant Percentage
Entries here are used inside screen ‘Split Config’ in the drop down ‘Split Scope’. Explained below.
Step 1: Enter percentage in number without % sign.
Step 2: Enter remaining percentage in number without % sign.
BDC vs Adaptive
BDC is a Vodafone model and Adaptive is a Pega model. They are used in offer recommendation in Text to Switch functionality. From the
above screen shot, BDC is allowed to recommend 90% of the time and Adaptive the remaining 10%.
Split Config
Select/Open a version > Artifacts > Screen: Split Config
Currently this is used in Text to Switch functionality for offer ‘SuperSavesUpgradeDiscount’. Values are pushed to decision data:
BDCvsAdaptiveSplit.
Step 1: Select offer.
Step 2: Select treatment.
Step 3: Select offer variant.
Step 4: Select the split score. Entries created in screen ‘Split Variant Percentage’ will be listed here.


83
ModelPropensityToRangeMapping
Select/Open a version > Artifacts > Screen: ModelPropensity To Range Mapping
Data gets pushed to Decision Data: ModelPropensityToRangeMapping.
Step 1: Enter model id.
Step 2: Enter description.
Step 3: Select range from High, Medium and Low.
Step 4: Enter start value of the range in number.
Step 5: Enter end value of the range in number.


84
Other screens
About other screens present in PM Tool.
Business Config
Holds business configuration values e.g. url for a contact us page, web chat url etc. Data is pushed to a Pega data page:
D_VFUKFWAOMFWDataAOMBusinessConfig.
In PM Tool, select/Open a version > Artifacts > Screen: Business Config
Step 1: Enter config name.
Step 2: Enter config type.
Step 3: Enter config value.
When configuring IVR apptags
- Enter the apptag name in “Config Type” field and  add “_” character at the end of the apptag.
- Enter the parameter name in “Config Name” field (Ex: WebchatURL).
- Enter the value for the parameter in “Config Value” field


85
When configuring  the Reconfigure VolumeConstraints in Batch Mode

Business Purpose
Values from this screen are used in other screens e.g. in Offer screen, while adding an offer, values created in this screen are available in a
drop down named ‘Business Purpose’ and selection is mandatory.
In PM tool, Select/Open a version > Artifacts > Screen: Business Purpose
Step 1: Enter name of the business purpose e.g. CrossSell, Retention etc.
Step 2: Enter description for business purpose.
Step 3: Enter ranking score in number. This is used in priority score calculation formula.
Step 4: Pick start date using date picker component.
Step 5: Pick end date using date picker component.
Step 6: Check box to enable/disable.
Step 7: Not yet used.
Step 8: Applies to execution mode, Batch and TIL. Valid value is a number (integer). Objective is to check that if a customer is in ‘Target’ for
an offer, it should not be in ‘Control’ (in subsequent batch runs) for that offer until control quarantine period for the business purpose is over.
Or if a customer is in ‘Control’ for the offer, it should not be eligible for any other offers from the same business purpose until control
quarantine period for the business purpose is over.
Step 9: Valid values are: -1, 0 or positive integer: Offer is eligible by CrossOverRate only if days since last business purpose communication
from Pega IH > CrossOverRate
Step 10: Used in the logic for global contact strategy for marketing offers. Saturation rate is maximum contacts per month. Valid value is a
postive integer. From Pega IH for outcome Selected or Pending, identify the count of communications for the offer and store in attribute


.CountSinceSaturationRatePeriod. Then offer is eligible by SaturationRate only if .CountSinceSaturationRatePeriod < .SaturationRateCount
defined here.


86

Business Segment
Values from this screen are used in other screens e.g. in Offer screen, while adding an offer values created in this screen are available in a
drop down name ‘Business Segment’ and selection is mandatory.
Select/Open a version > Artifacts > Screen: Business Segment
Step 1: Enter business segment.
Step 2: Enter business segment description.

Customer Segment
E.g. Prepaid, Postpaid, as defined by the business. Values entered here are displayed in a drop down in offer screen and one must be
selected during offer creation.
Select/Open a version > Artifacts > Screen: Customer Segment
Step 1: Enter customer segment name.
Step 2: Enter customer segment description.
Channel
Select/Open a version > Artifacts > Screen: Channel


87
Step 1: Enter channel name e.g. Email, SMS, IVR etc.
Step 2: Enter channel rank in number. This is used in logic to pick the best treatment for Offer by channel hierarchy. Lowest number on the
top.
Step 3: Number of non mandatory communications for the channel. This data is sent to Pega decision data: ChannelDecisionMix.
Step 4: Acceptable outcomes for the channel defined here.
Step 5: Enter description for channel.
Step 6: Select direction: Values presented: Outbound or Inbound.
Step 7: Templates for IVR channel.
Step 8: If checked, means sub channel is available, e.g. for outbound call centre channel a sub channel could be Webhelp, Resq etc.
Step 9: Apply Actions. Used in IVR channel.

Channel Contention
Defines the contention period for a channel. E.g. if channel for outbound call centre has 5 days as contention period, it means after a
customer becomes eligible for an outbound call, for the next 5 days customer should not get eligible for another outbound call. Eligible after
5 days. Data is pusded to Pega decision data: ChannelContention.
In PM Tool, select/Open a version > Artifacts > Screen: Channel Contention
Step 1: Drop down lists all the channels created via ‘Channel’ screen. Select one. Options are: Retail, Email, IVR, WEB, DirectMail, SMS,
OutboundCC, InboundCC, AppPush.
Step 2: Enter number of days.

Channel Purpose Eligibility
Defines the business purpose and eligibility rule(s) for each channel.
Select/Open a version > Artifacts > Screen: Channel Purpose Eligibility


Select/Open a version > Artifacts > Screen: Channel Purpose Eligibility
Step 1: Drop down lists all the channels created via ‘Channel’ screen. Select one. Options are: Retail, Email, IVR, WEB, DirectMail, SMS,
OutboundCC, InboundCC, AppPush.


88
Step 2: Drop down lists all the business purpose entries created via ‘Business Purpose’ screen. Select one. Options are: Reward, Retain,
Care, Service, Engagement, Acquistion, TradeIn, Retention, Upsell, CrossSell, Renew.
Step 3: Click on rule(s) in Available Rules section to associated with the Channel-Business Purpose.

Channel Control By Execution Mode
This controls if a particular channel needs to be enabled or disabled for an execution mode. E.g. for execution mode ‘Batch’ lets say SMS
channel is disabled and Email channel is enabled. Thus, customer correspondence will be via email channel and not via SMS channel.
Corresponding Pega Decision Data: ChannelControlByExecutionMode.
In PM Tool, Select/Open a version > Artifacts > Screen: Channel Control By Execution Mode
Step 1: Select Channel. Options are: Retail, Email, IVR, WEB, DirectMail, SMS, OutboundCC, InboundCC, AppPush.
Step 2: Check box to enable/disbable.
Step 3: Select Execution Mode. Options are: TIL, GRPL, ProcessEvent, NBAA, GetNBA (for IVR), Batch
Sub Channel Control By Execution Mode
This controls if a particular sub channel for a channel needs to be enabled or disabled for an execution mode. E.g. from below screenshot,
for execution mode ‘ProcessEvent’ lets say ‘Webhelp’ target sub channel is enabled and rest are disabled. Thus, the outbound calling file
will be sent to Webhelp sub channel only.
Corresponding Pega Decision Data: SubChannelControlByExecutionMode.
In PM Tool, select/Open a version > Artifacts > Screen: Sub Channel Control By Execution Mode


In PM Tool, select/Open a version > Artifacts > Screen: Sub Channel Control By Execution Mode
Step 1: Select Channel. Options are: Retail, Email, IVR, WEB, DirectMail, SMS, OutboundCC, InboundCC, AppPush.
Step 2: Select Execution Mode. Options are: TIL, GRPL, ProcessEvent, NBAA, GetNBA (for IVR), Batch.
Step 3: On selection of a channel, target sub channel is populated, select as required. E.g. for Channel = OutboundCC, sub channels
populated are: Resq, Webhelp, Concentrix, Stoke.


90
Upgrade Screens -How To
In this section, we tried to keep all AU related PMTool screens and explained how to configure related data.


91
Division to Team mapping

How to reach the Division Mapping screen?
Select/Open a version > Artifacts > Screen: Assisted Upgrade -> Team Management > Division Mapping.

Data gets pushed to Decision Data: D i v i s i o n T o T e a m .
We have multiple sections under this screen.
Section1: Will Contain the existing list of Teams. To populate a new value in this list we need to raise request to PM tool dev team. We can
only assign division values to the available Teams.
Section2: Will display the Team List, and We can add new Division for selected Team.

Steps to Add/Update as fallows.


92
 Step 1: Select Team.
Step 2: Enter New Division.
Step 3:  To update we can Enter Division from the list.
Note: Each combination of Team and Division will load into a new record in our Decision Data.


93
Tariff Groups
How to reach Tariff Groups Screen?
Select/Open a version > Artifacts > Screen: Assisted Upgrade -> Recommendation Management > Tariff Group.

Data gets pushed to Decision Data: Tariff Groups.
We have multiple sections under this screen.
Section1: Will Contain the existing list of Tariff Groups. To populate a new value in this list we need to raise request to PM tool dev team.
We can only assign values to the selected Tariff Group.

Section2: Will display the Tariff Group List, Band Id along with Start and End values for selected Tariff Group.
We can add/Update record for selected Tariff Group.


94
Steps to Add/Update as fallows.
 Step 1: Select Tariff Group.
Step 2: Enter Rank value.
Step 3: Enter Max Data for Selected Tariff Group.


95
Band Management
How to reach Band Management Screen?
Select/Open a version > Artifacts > Screen: Assisted Upgrade -> Band Management.

Data gets pushed to Decision Data: R a n g e M a p p i n g.
We have multiple sections under this screen.
Section1: Will Contain the existing list of Range Types. To populate a new value in this list we need to raise request to PM tool dev team.
We can only assign range values to the selected Range Type.

Section2: Will display the Range Name, Band Id along with Start and End values for selected Range type.
We can add/Update record for selected Range Type.


96
Steps to Add/Update as fallows.
 Step 1: Enter Range name.
Step 2: Enter Band Id
Step 3: Enter the Start Value.
Step 4: Enter the End Value.


97
Cohorts Management
How to reach Cohorts Screen?
Select/Open a version > Artifacts > Screen: Assisted Upgrade -> Cohort Management > Cohorts.

Data gets pushed to Decision Data: Customer Cohorts.
We have multiple sections under this screen.
Section 1: Will Contain the existing list of Cohorts. We will populate the records with few details on the screen.
Section 2: Cohort Details
 We can add a new record for Cohort with respective details.

Steps to Add/Update as fallows.


98
 Step 1: Enter Cohort name which should be unique.
Step 2: Cohort Id will get generated by application.
Step 3: select Start date and end date to define active period.
Step 4: select Cohort Type from list items provided by Pmtool team.
Step 5: select Team to which we need to associate this cohort.
Section 3: Product Holding Details for cohort
 We can associate product level information for Cohort with respective details as below.
Step 1: Enter Addon Product code which needs to be associated to cohort. (Multi select)
Step 2: Enter Tariff Product code which needs to be associated to cohort. (Multi select)
Step 3: select Tariff Group from the selected list which will get populated from Tariff Groups Screen.
Step 4: select Star rating values from the selected list which will get populated from Tariff Groups Screen.
Section 4: Customer Information and Band Details
 We can associate Customer information for Cohort  and with respective Customer details Band detail screen will get populated relatively.


99
In the above screen we selected customer type is PaymSIMO, so SIMOS15 and SIMO net MAF details are displayed in Band section.
Similarly, for PaymHandset set respective Band details will get populated.
Steps to enter customer and Band Details.
Step 1: Enter Customer type which needs to be associated to cohort. This is a selected list from pm tool team.
Step 2: Enter valid Dates respective to contract details.
Step 3: Enter Customer Intent from selected list where Customer intent will be coming from intent screen when it is set to True for
Iscohortavailable flag
Step 4: Select life cycle id and other Band related Ids from the selected local list which are directly populated from the Band Management
screen.
The related values are valid data which has been set in band management screen.


100
SegmentStrategy
Segment Strategy provides the list of segments for all or specific teams applicable only for InboundCC.
Data gets pushed to Pega Environment to Proposition Decision data.
Location: Records > Decisioning > Decision > Decision Data > IntentToSegmentStrategy (Instance Name).
Navigate to PM Tool screen: Select/Open a version > Artifacts > Screen: Segment Strategy.
There are two sections on the screen.
Section 1: Existing list of records is presented below.
Section 2: To add new data follow the below steps.
Step 1: Select the segment strategy from the drop down. Options available are Grow, Retain, Save.
Step 2: Select the team from drop down, options available Omni, Save, Super Save, All. Populated from Assisted Upgrade > Team
Management > Division Mapping.
Step 3: Select the data usage from the dropdown which can be Low or High,
Step 4: Select the confidence score range from the drop down which can be High, Low, Medium.
Step 5: Channel will be automatically populated as InboundCC.
Step 7: Select the Churn Band field which can be from 1 to10 and All.
Step 8: Select the Intent from the drop down configured in the Intent section.
Note:
i) Mandatory fields are marked with (*).
ii) pyName (UniqueID)= auto generated.


102
Commercial Recommendations
Commercial Recommendations decision data provides the list of commercial recommendations with tariff, addon, discount, and handset
codes.
Select/Open a version > Artifacts > Screen: Assisted Upgrade>Recommendation Management>Commercial Recommendation.
Data gets pushed to Pega Environment to Decision data > Commercial Recommendations.
There are two sections on this screen.
Section1: Will Contain the existing list of commercial recommendations.
Section2: To add a new record, follow the below steps.
Step 1: Enter the recommendation name.
Step 2: Select applicable Cohort Name Eg., Sky MultLine CTN SIMO. This information is populated from Assisted Upgrade > Cohort
Management > Cohorts screen.
Step 3: Enter the recommended tariff code.
Step 4: Enter the recommended discount code(s).
Step 5: Pick recommended start date using the date picker component.
Step 6: Pick recommended end date using the date picker component.
Step 7: Enter handset code(s).
Step 8: Select the applicable recommended position from the drop down.
Step 9: Check box to enable/disable.
Step 10: Enter the recommended addon code(s).
Step 11:  Select applicable team(s) from the drop down.


103
Note: i) Mandatory fields are marked with (*).
ii) pyName(UniqueID)= auto generated.


104
Pick N Mix and Discounts Blocks
Discount Blocks
Discount blocks will be used in Pic and Mix screen.
Navigate to PM Tool screen: Select/Open a version > Artifacts > Assissted Upgrade<Recommendation Management>Discount Blocks

1. Discount Block: Enter Name of the Discount Block.
2. Discount Block Percentage: Numeric value without the percentage sign.
3. Discount Block Description: Enter description of the Discount Block.
Pick N Mix
Data gets pushed to Pega Environment to Recommendation Blocks Decision Data which is to used identify Tariff block and Discount block
for customer with segment Strategy
Navigate to PM Tool screen: Select/Open a version > Artifacts > Assissted Upgrade> Recommendation Management >Pick n Mix
1. Segment Strategy: Select Segment Strategy from drop down with available options Grow/Save/Retain.
2. Discount Flag: Check box to enable/disable.
3. Recommendation Position: Enter a numeric value to defines position for recommendation.
4. Tariff Block: Selecting Tariff Block (available options are T1,T2,T3 and T3). Tariff Block Description is read-only and automatically
populated.
5. Discount Block: Selecting Discount Block (options presented are created in Discounts Block screen) from drop down. Discount Block
Description is read-only and automatically populated.
by clicking Add Recommendation Block enables to add more combinations of Recommended position, tariff blocks and discount
blocks


105
Upsell Discount Config
In this screen we define Teams and also selecting which Discount Logic to be applied for any team which will be pushed to
AssistedUpgradeTeamDiscountConfig Decision Data.
Navigate to PM Tool screen: Select/Open a version > Artifacts > Assissted Upgrade>Discount Management> Upsell Discount Config.
1. Team: Enter Name of the Team.
2. For each pair(read only) enter Discount Percentage value without Percentage (%) symbol and Upsell Amount.
Click Add Upsell Discount pair we enable to add new pair of Upsell Discount and amount.Value for Pair will be we auto generated.
This data along with Team will be pushed to AssistedUpgradeUpsellDiscountConfig Decision Data.
3. Discount Logic: Select type of Discount Logic(s) to be applied for Team, click on it in the Available Discount Logic section. To remove,
click on it in the Existing Discount Logic section.


106
Team Price Matrix
This screen will provide discounts and Tariff Details that are available for PriceMatrix discount logic
Data gets pushed to Pega Environment to three Decision Data based on Team (OmniPriceMatrix/SavePriceMatrix/SuperSavePriceMatrix)
Navigate to PM Tool screen: Select/Open a version > Artifacts > Assissted Upgrade>Discount Management>
1. Team: Select a team from dropdowm(Options Omin,Save and SuperSave).Based on selected team data will get pushed to respective
Decision Data.
2. Tariff Name: Enter meaningful tariff name.
3. Tariff Group: Enter Tariff Group that Tariff belongs.
4. Data Allowance: Enter amount of Data.
5. Tenure: Enter tenure for the tariff
6. Star Rating Applicable: Enable/Disable star rating to be applied for that Tariff. Enabling it we need to enter combination of StarRating
and Discount
StarRating : Enter Numeric values for Star Rating to apply discount
Discount : Enter any values for the discount without percentage symbol(%)
We can have multiple combinations of StarRating and Discount.
7. Discount : when Star Applicable Disabled, enter discount without any percentage(%) symbol
8. Tariff Code: Enter the code for the Tariff.


107
Segment Of 1 Discount
This screen will provide discounts and Tariff Details that are available for discount logic type Segmenof1.
Data gets pushed to Pega Environment to SegmentOf1DiscountStrategy Decision Data
Navigate to PM Tool screen: Select/Open a version > Artifacts > Assissted Upgrade>Discount Management>Segment of 1 Discount
1. Discount Strategy Name: Enter meaningful name for Discount.
2. Cohort: Select Cohorts from Dropdown (options presented are cohorts with cohort type Segmentof1 created on Cohorts Screen ).
3. Valid From Date: Pick start date, using the date picker component.
4. Valid From Date: Pick End date, using the date picker component.
5. Discount: Enter value for discount in percentage without percentage(%) symbolto be applied.
6. Channel: Select Channel from drop down.
7. Team: Enter a team to make tariff(s) and Discount available for that team. We can have multiple teams.
8. Tariff Codes: Enter Tariff codes.(can have multiple Tariff codes).


108
S15Threshold
Data gets pushed to Pega Environment to S15Threshold Decision Data.
Decision Data Change- New attribute "Team" added to DD UpgradeLifeCycleS15RuleConfig
New attribute added to Tariff Products- EnableEUMafControl -- This attribute is to flag Tariffs to enable/disable  EU S15 control.
Navigate to PM Tool screen: Select/Open a version > Artifacts > Assissted Upgrade>Recommendation Management>S15Threshold

1. Segment Strategy: Select Segment Strategy from drop down with available options Grow,Save and Retain
2. S15Threshold value: Enter Numeric value.
3. Recommended Positon: Select recommended position from drop down.


109
AddOn Group
In this Screen we define Addon that are to be considered for calculating NetMaf Addon Cost and S15Addon Cost.
Data get pushed to NetMafAddonListConfig Decision Data
Navigate to PM Tool screen: Select/Open a version > Artifacts > Assissted Upgrade>Discount Management>AddOn Group
1. Name: Enter meaningful name for Addon Group
2. Enabled: Check box to enable/disable the Addon Group.
3. Add On Code: Enter Add On(s) Code that need to be considered to calculate Addon Cost(s)
4. S15 Flag: Enbled / Disable S15Flag.Enabling it to any Addon, to be used in Calculating S15AddOn Cost.
5. NetMafFlag: . Enbale/Disable Net Maf Flag.Enabling it to any Addon to be consider in Calculating AddOn Cost.
To add more Addons to the group click Add Add On (6)


110
HBB Screens
How to reach HBB Screens?
Select/Open a version > Artifacts > Screen: Upgrades -> HBB.
We have multiple screens under this screen.
Section 1: HBB Package Rank:
The business will decide the Ranking for each new plan group, we will be defining the plan group with the combination of Plan and product
level banding.
Step 1: Enter Plan Band.
Step 2: Enter Product Level Band.
Step 3: Enter Plan Group.
Step 4: Enter Package Rank.

Section 2: HBB Plan Eligibility Management
 This screen is to define Exceptional cases for Eligibility rules. As a config manager, if any of the Plan group is not falling under the
Universal rule defined for HBB, we can explicitly include/exclude based on this configuration.


111
Steps to Add/Update as fallows.
Step 1: Enter From Plan Band.
Step 2: Enter To Plan Band
Step 3: Enter From Product Level Band.
Step 4: Enter To Product Level Band.
Step 5: Enter HBB Life Cycle Band.
Step 6: Enable/Disable IsExclude.

Section 3: HBB Plan Prioritisation List
Business-defined Priority rank values will be configured here, Priority rank will be for each plan group, churn, and life cycle band
combination.
Steps to Add/Update as fallows.
Step 1: Enter From Plan Band.
Step 2: Enter To Plan Band
Step 3: Enter From Product Level Band.
Step 4: Enter To Product Level Band.
Step 5: Enter Churn Propensity.
Step 6: Enter HBB Life Cycle Band.
Step 7: Enter Rank.


112
Section 4: HBB Retention Discount:
Business-defined Retention Discount values will be configured here, Priority rank will be for each plan group, churn, and life cycle band
combination.
Churn propensity value ALL will be defined for the same discount across the churn values. else, respective churn values need to consider.
Steps to Add/Update as fallows.
Step 1: Enter From Plan Band.
Step 2: Enter To Plan Band
Step 3: Enter From Product Level Band.
Step 4: Enter To Product Level Band.
Step 5: Enter Churn Propensity.
Step 6: Enter HBB Life Cycle Band.
Step 7: Enter Retention Discount.
Step 8: Enter Post Contract Length.

Section 5: HBB Technology:
 This screen will provide the capability to enable and disable the technology.
and configuration should match with the Plan technology value from the Digital API request.
Step 1: Enter Technology.
Step 2: Enter Plan Technology. (New one in 3.5)
Step 3: Enable/Disable Enabled.


113

Pre-requisite for Above HBB Screens:

Configuration of Product Attributes:
Plan Bands and Product Level Bands, Technology will be loading from the Product Attributes Screen. (Existing screen/Functionality)

Example: Product Level Band
HBB Life Cycle Band should be configured in Band Management Screen (Existing screen/Functionality).

 ProductLevelBan
dNumber Band for each
plan bandSingle Value empty Tariff 1
PlanBand Number Band to group
plans Based on
the speedSingle Value empty Tariff 3
RetentionPriceFlo
orNumber Plan group price
floorSingle Value Y Tariff 19
Technology Text Technology Single Value N/A Tariff SOGEA
Technology
SpeedNumber Speed of the
TechnologySinge Value N/A Tariff 30 Name Type Description  Single/Multiple Default Product Type Sample Value


115
Manage Work Items
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. A work item can consist of one of more offers and all artifacts
related to those offers. Multiple work items can be created at any point of time allowing parallel development towards a new baseline
release. Offers/Treatments managed within a work item are locked into it and other work items cannot edit those Offers/Treatments until the
lock is released by including the work item in a release. Only Offers 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 artifacts related to the business purpose(s)
effected in the work item will be refreshed in the target environment upon push.

Below are few useful links to other pages:
Create a work item
Search Offer
Create new Offer
Assign to Manager
Manage Offers
Manage Treatments
Reopen Offer/Treatment in Edit
Work item Flow


116
Create a work item
Work items are shown in Offer Flows 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.


117
Assign work item to 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.


118
Discard 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 Offer/Treatment changes
have to be reverted out of many items In Edit list. For this requirement, consider using Rollback changes to Offer/Treatments


119
See Offers/Treatments in Edit
When the work item is opened, the landing page shows the Offers and Treatments in Edit. All items changed in this work item will be added
to In Edit list.
Below is the list of Offers in landing page.
Below is the list of Treatments in landing page.


120
Rollback changes to Offer/Treatments
If all changes in work item are not required, one could Discard work item changes .  Sometimes it may be necessary to remove one of
the Offer/Treatment from the work item as the changes are no longer required for a given Offer/Treatment. Restore feature allows rolling
back changes done for a given Offer/Treatment. The Restore Icon in Landing Page performs Rollback.
When Restore is invoked for an Offer, changes done in all entities related to the Offer will be rolled back to their original values present at
the time of creating the work item. Deleted Offers can also be restored using this action. Similar icon is available for Treatments also.
Restore action cannot be undone. All changes done for the Offer/Treatment will be removed from work item.


121
Reopen Offer/Treatment in Edit
When an Offer/Treatment is edited in a work item, it gets added to In Edit list. This item no longer appears in Search as its already in the
edit list. This In Edit list is visible in landing page as shown below.
Clicking on the Manage icon open the Offer/Treatment in Review mode.
Edit button is provided in the review page which allowing editing Offer/Treatment.


122
Push 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 Offers/Treatments modified within the work item are updated in Dev2 (Delta Push). Other
Offers/Treatments existing with the squad are not modified with this push.


123
Assign to Manager
Open work item and submit using Submit button. This action performs compare and  shows the comparison view.
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 ‘Submit’ button at the bottom of the screen. The work item status changes to ‘Ready For Release’ and will
be routed to the Manager.


124
Approve 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.
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.
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 below.


126
Change 'Assigned to Release' 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.


127
Pull functionality
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.


128
Discard and Prefer Branch option will be available in order to keep the work item changes as is without pulling from the baseline version.
On submitting the page will pull the changes and navigates to the landing page once completed.
Pull icon will be available until all the changes related to that entity are propagated to the work item.


129
Manage Offers
Below artifacts are managed as part of the work item:
 Offer
Offer Variation
Offer to Offer Variation
Intent to Offer Mapping


130
Search Offer
From the landing page, click on the “Manage Offers” button in Offers tab to search for the offers.
This navigates to the page where all the offers are displayed by default.
Step1 : Click on search to retrieve the data based on selection of an offer/business purpose/offer variant.
Step2 : It allows to enable/disable an offer without editing. Enabled option will be disabled if it is locked in other work item.
Step3 : It shows the details of an offer and its variants in review from where it allows to edit an offer/variants if it is not locked in other work
item as shown below.


131
Step4 : It allows to clone a locked/unlocked offer which navigates to below page.
Step5 : It allows to delete an offer which deletes all its related entities (Treatments, Variants…etc). Delete option will be disabled if it is
locked in other work item.
Step6 : Displays the user name and work item in which that particular offer is modified.
Step7 : “Create Offer” opens a page to create an offer as shown below.
Step8 : Only unlocked offers will be downloaded and uploaded by using Download and Upload buttons.


132
Delete Offer
Delete option is available in search offer page. It deletes an offer and its related treatments, variants…etc from the work item.
The deleted offer will be added to the list in Landing page and marked it as deleted as shown below.
Offer/Treatment removed in a work item can be restored by Rollback changes to Offer/Treatments .


133
Create new Offer
Click on “Create Offer” button in search page.
This navigates to an offer page to create a new offer as shown below. It will be available in Landing page once created for further
modifications.


134
Edit existing Offer
An offer can be edited from the review page if it is not locked in other work item.
This opens a page where an offer details can be edited as shown below.


135
Edit Intent to Offer mapping
Click on “Manage Intent Mapping” which is available in offer page. It will be visible at the time of offer edit and after new offer is saved.
This opens a page to manage intents for an offer and displays the intents which are already mapped as shown below.
Select a intent from ‘Intent’ list which will be added under Intent Mapping to map multiple intents to an edited offer. Enabled option will be
reflected at intent level and not at the intent to offer level.


136
Enable/Disable Offer to Offer Variation
Offer to offer variations for an offer will be displayed in offer review page at which an option is available to enable/disable without editing as
shown below.


137
Add/Edit Offer Variation
For new offer, "Add Default variant" button is available in the offer page after record is saved to create "OfferVariantDefault" variation to an
offer as shown below.
For Existing offer, offer variation and offer to variation can be created by clicking on "Add Variant" button and can edit/delete existing
variation from the review page.
This opens offer variation page where it allows to create a new variation and offer to variation or modify the existing one.


138
Step1 : When existing variation is selected from the list, all the details will get populated.
Step2 : New/Existing offer to variation for an offer will be displayed as shown.
Offer variation and offer to variation will be saved by clicking on ‘Save’ button.
Once offer to variation is created, it will be added to the list in the review page.


139
Clone Offer
An offer can be cloned from below three screens. Clone option will be available for locked/unlocked offer.
Clicking on clone icon/button allows to clone a particular offer which navigates to edit screen in order to create a new offer by changing it’s
unique fields.


140
Clone Offer Variation & Offer To Variation
A offer variation and offer to variation can be cloned from below screen. Clone button will be disabled for locked offer.
Clicking on clone button allows to clone a particular offer variation and offer to variation for an offer.
Offer variation will be mapped to an offer by selecting existing offer variation or with new offer variation in clone.


141
Upload/Download Offer
Upload and download option for offer is available in manage offers screen as below.
Download : It downloads all unlocked offers along with the offers in edit within the work item. User can download the offers based on
search provided.
Upload : It allows to upload the offers data in bulk. The modified offers will be added to in edit list and locked with the work item.
Clicking on upload button navigates to the below screen.
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.
Click on submit to view the modified records as below.


142
On submitting the page will navigates to the below screen which displays upload successful message.
Click on Finish to navigate to the manage offers screen.
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.


143
Click on submit to view the modified records as below.
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.


144
Click on Next which displays the offers and its related entities that are deleting.
Next button navigates to the below delete confirmation page.


145
On submitting the page updates and deletes will be committed and displays the uploaded and deleted summary as below.
Click on Finish to navigate to the manage offers screen.


146
Upload/Download Offer To Variation
Upload and download option for offer to variation is available in offer review screen as below.
Upload button will be disabled for the locked offer.
Download : It downloads offer to variation data of respective offer.
Upload : It allows to upload the offer to variation data in bulk. The respective offer will be added to in edit list and locked with the work item
when offer to variation is uploaded with the modified data.


147
Manage Treatments
Below artifacts are managed within work item:
Treatments
Treatment Variations
Treatment to Treatment Variations
Bundle Mapping


148
Search Treatment
From the landing page, click on the “Manage Treatments" button in Treatments tab to search for the treatments.
This navigates to the page where all the treatments are displayed by default.
Step1 : Click on search to retrieve the data based on selection of an treatment/channel/treatment variant.
Step2 : It allows to enable/disable the treatment without editing. Enabled option will be disabled if it is locked in other work item.
Step3 : It shows the details of a treatment and its variants in review from where it allows to edit an treatment/variants if it is not locked in
other work item as shown below.


149
Step4 : It allows to clone a locked/unlocked treatment which navigates to below page.
Step5 : It allows to delete a treatment which deletes all its related entities (constraints, Variants…etc). Delete option will be disabled if it is
locked in other work item.
Step6 : Displays the user name and work item in which that particular treatment is modified.
Step7 : “Create Treatment” opens a page to create a treatment as shown below.


150
Step8 : Only unlocked treatments will be downloaded and uploaded by using Download and Upload buttons.


151
Delete Treatment
Delete option is available in search treatment page. It deletes a treatment and its related constraints, variants…etc from the work item.
The deleted treatment will be added to the list in Landing page and marked it as deleted as shown below.


152
Create new Treatment
Click on “Create Treatment” button in search page.
This navigates to treatment page to create a new treatment as shown below. It will be available in Landing page once created for further
modifications.
When a sub channel which has ApplyTemplates true is selected then all the sub channels which has ApplyTemplates false will be disabled
and other sub channels which has ApplyTemplates true will be enabled for multi selection.
When a sub channel which has ApplyTemplates false is selected then all the other sub channels will be disabled which behaves as a single
selection.


153
Edit existing Treatment
Treatment can be edited from the review page if it is not locked in other work item.
This opens a page where the treatment details can be edited as shown below.
When a sub channel which has ApplyTemplates true is selected then all the sub channels which has ApplyTemplates false will be disabled
and other sub channels which has ApplyTemplates true will be enabled for multi selection.
When a sub channel which has ApplyTemplates false is selected then all the other sub channels will be disabled which behaves as a single
selection.


154
Assign to Bundle
Click on “Assign To Bundle” which is available in treatment edit. It will be visible only when treatment is saved with HasChildren 'Y'.
This opens a page to manage child treatments for a treatment and displays the treatments which are already mapped as shown below.
Step1 : Displays the treatments which has HasChildren 'Y' in the list for selection.
Step2 : Allows to delete a child treatment for a bundle or modify the child details.
Step3 : "Add Child" button is visible when the edited treatment is the bundle name.
Click on “Add Child” button to add a new child treatment which navigates to below page. Displays all the bundle related channel treatments
except the bundle in the list and for selection as well.


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.


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.


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.


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.


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.


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.


161
Once treatment to treatment variation is created, it will be added to the list in the review page.


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.


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.


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.


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)


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.


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.


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.


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.


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.


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.


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.


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.


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.


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.


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.


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.


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.


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.


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.


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.


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.


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.


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.


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.


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.


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.


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.


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


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.


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.


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.


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.


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).


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.