3970
STF Flow
This document briefs on managing the Entities, Graphs and Mock services(if applicable) under Buckets.
Upgrades
The Upgrade journey will have different customer flows and every flow will start with getting customer details along with recommendations
that needs to be shown.
Get Customer API calls involves
Creating new customer data in Spine which need STF to create data in spines for new customers
External API calls GetProcessedServiceList(GPSL), GetCustomerPartyList(GCPL), CustomerRetentionEligibility(CRE) which need
STF to create data in clipboard pages and datasets
AOM API calls GetRecommendations which we get data from Dataflows / Strategies
GetProductList API is called for each product type so we can create a mock service in STF. Response for service will be returned based
on product type.
GetStockAvailability is called for each product so we can create a mock service in STF. Response for service will be returned based on
product Id.
So we will have an STF Bucket for each flow and below are different customer flows
MBB
PAYM
Watch

MBB GetCustomer for MBB CustomerForMBB DB Table
AccountForMBB
ModelForMBB
… etc
GPSL for MBB GPSL Response entities Clipboard pages and dataset
GCPL for MBB GCPL Response entities Property sets for clipboard pages
CRE for MBB CRE Response entities Clipboard pages and dataset
PAYM GetCustomer for PAYM CustomerForPayM DB Table
AccountForPayM
ModelForPayM
… etc
GPSL for PAYM GPSL Response entities Clipboard pages and dataset
GCPL for PAYM GCPL Response entities Property sets for clipboard pages


GCPL for PAYM GCPL Response entities Property sets for clipboard pages
CRE for PAYM CRE Response entities Clipboard pages and datasetB u c k e t G r a p h E n t i t y C o m m e n t s


3971
Watch GetCustomer for Watch CustomerForWatch DB Table
AccountForWatch
ModelForWatch
… etc
GPSL for Watch GPSL Response entities Clipboard pages and dataset
GCPL for Watch GCPL Response entities Property sets for clipboard pages
CRE  for Watch CRE Response entities Clipboard pages and dataset
GSA GSA for product Mutliple entities Need to have some default


3972
PRPC Features


3973
8.5.3 - New Features
Case Management
Save time and effort with automatic draft off mode for processes in case types (8.5) - the system now automatically turns off draft mode
for any processes that contain no configuration issues, instead of having to manually turn draft off mode in Dev Studio . -1--Needs to
Explore
Obtain approvals from email and push notifications from App Studio (8.5) - Previously composing an email message and adding
attachments required switching to Dev Studio. -1--Needs to Explore
Determine a relevant case approver by using business logic (8.5) - Previously business logic was available only for routing assignments,
and now you can use this option for routing approval steps as well.-1--Needs to Explore
Capture initial data faster with the default Create stage (8.5) - Case Designer now adds a default Create stage to your case life
cycle every time you create a new case type, both in App Studio and Dev Studio. -2--Needs to Explore

Save time and effort with automatic draft off mode for processes in case types (8.5)
The system now automatically turns off draft mode for any processes that contain no configuration issues, instead of having to manually
turn draft off mode in Dev Studio.
When you add a process to your case life cycle, by default the process is in draft mode. Draft mode provides an option to test the case type
before you advance with your application development, even if processes in your case life cycle contain configuration issues. When a
process is in draft mode, you can check its run-time behavior by running the process or previewing it in a user portal, even if the process
contains errors. However, to ensure that the process works correctly after you deploy your application in a production environment, you


need to turn off draft mode before moving relevant rulesets to the production environment.

Obtain approvals from email and push notifications from App Studio (8.5)
Determine a relevant case approver by using business logic (8.5)
Capture initial data faster with the default Create stage (8.5)
Pega Infinity on cloud
Stay current with seamless upgrades to Pega Infinity (8.5)
Deploy Pega Infinity with configuration enhancements and convenient images (8.5)


3974
Conversational Channels
Improve the performance and automation of your email bot with reports and archiving (8.5)-- 2-Needs to Explore
Build a chatbot and email bot in App Studio more easily (8.5)--3-Needs to Explore
Save time while working in the Email Manager and Case Manager portals (8.5)--2-Needs to Explore
Data Integration
Track status of business processes and data easily by importing Excel files (8.5)
Access and curate your data by using enhanced data APIs (8.5)--1-Needs to Explore
Call authenticated APIs from any application (8.5)--3-Needs to Explore
Decision Management
Enhance your revision management process with Deployment Manager pipelines(8.5)
Increase the flexibility of your business change management process with improvements to revision management (8.5)
Test your next-best-action configuration with multilevel simulations (8.5)
Predict long-term business outcomes in Prediction Studio (8.5)
Broaden your selection of topic detection models by connecting to third-party services (8.5)
Make your strategies compatible with the optimized strategy execution engine by using a check utility (8.5) – 3-Needs to Explore
Limit the number of active data flow runs (8.5)--3-Needs to Explore
Enhance your data sets with Apache HBase 2.1 and Hadoop 3.0 (8.5)--1-Needs to Explore
DevOps and Automated Testing
Delay the execution of a step within a test and rerun failed scenario tests for enhanced scenario test stability (8.5)--2-Needs to Explore
Avoid duplicating application test efforts by merging test coverage reports (8.5)-3--Needs to Explore
Mobile
Customize your mobile app to reflect your brand's identity (8.5)
System Administration


Mobile
Customize your mobile app to reflect your brand's identity (8.5)
System Administration
Identify performance issues with queue processor and job scheduler activities (8.5)--1-Needs to Explore
Limit upgrade downtime with data schema upgrade improvements (8.5)-1--Needs to Explore
User Experience
Build a better user experience with the improved Cosmos UI theme (8.5)-1--Needs to Explore
Modernize your interface with React UI (8.5)-2--Needs to Explore
Low-code Application Development
Plan your Microjourneys more conveniently in an improved Case Designer (8.5)-1--Needs to Explore
Define fields in data objects intuitively (8.5)-1--Needs to Explore


3975
Search for Pulse messages in spaces (8.5)-3--Needs to Explore
Find items quickly in App Studio (8.5)-3--Needs to Explore
Create conditions in an enhanced condition builder (8.5)-1--Needs to Explore
Navigate easier across business logic-based routing cards (8.5)-1--Needs to Explore
Develop applications faster with nested Declare Trigger rules (8.5)-1--Needs to Explore


3976
Case Management


3977
Obtain approvals from email and push notifications from App Studio
In App Studio you can now completely configure an approval email in a no-code and user-friendly way, so that users of your application can
approve or reject cases without logging in to an application, and as a result, speed up case resolution.
Previously composing an email message and adding attachments required switching to Dev Studio.


3978
Determine a relevant case approver by using business logic
Previously business logic was available only for routing assignments, and now you can use this option for routing approval steps as well.
Instead of manually selecting a person or work queue to receive an approval request, you can now define conditions that determine, at run
time, who approves a case. Apart from operators and work queues, you can also consider the skill set, availability, and workload of the
approver.
By using business logic, you create a flexible application that dynamically adjusts work to current circumstances, so that you can still
resolve a case even if the approver is difficult to determine. To ensure that unique and complex cases reach a resolution, you can create an
entire set of conditions. In addition, you can specify a routing method that your application applies when no condition evaluates to true. The
following figure shows a scenario in which a job candidate applies for a different position than French translator, and the urgency of the
case is lower than 85. Consequently, the application routes the approval step to a specific manager:


3979
Capture initial data faster with the default Create stage
To speed up case creation and accommodate the most frequent business needs, Case Designer now adds a default Create stage to your
case life cycle every time you create a new case type, both in App Studio and Dev Studio. The Create stage includes a view with fields that
users fill in to capture required data before case processing starts.
After case created:
Create step has header but UI is not created automatically

A default Create stage facilitates the application development process by making a case life cycle independent of the p y S t a r t C a s e starting
process. As a result, your application is more granular and easier to maintain.
The Create stage also enhances workload management, because users can now discard any case that is in the Create stage, before the
case processing starts. A discarded case has a Resolved-Cancelled status, and, worklists and work queues consequently omit such


3980
discarded cases.
After you upgrade to Pega Platform™ 8.5, you can choose to include the Create stage in your existing case types. If you decide not
to include the Create stage, all of your case types still continue to operate correctly.
For more information, see The Create stage.


3981
Save time and effort with automatic draft off mode for processes in case types
To reduce development time and effort, when you save a case type, the system now automatically turns off draft mode for any processes
that contain no configuration issues, instead of having to manually turn draft off mode in Dev Studio . When a process is in draft mode, you
can check its run-time behavior by running the process or previewing it in a user portal, even if the process contains errors. However, to
ensure that the process works correctly after you deploy your application in a production environment, you need to turn off draft mode
before moving relevant rulesets to the production environment. For an application that consists of multiple case types with multiple
processes, this activity can be tedious and time-consuming. Additionally, you need to switch to Dev Studio to manually turn off draft mode.
For greater convenience, saving a case type in App Studio and Dev Studio now automatically switches off draft mode for processes that
contain no configuration issues so that you can seamlessly deploy your application on a production environment.
Additionally, to ensure that your processes are correct, Case Designer now displays a message that lists errors in your case type. You can
quickly check what the issues are and locate the processes that needs fixing, as in the following example:

For the above case, when we create the view for Test step and save the case, the warning is removed automatically


3982
Low-code Application Development


3983
Nested Declare Trigger rules
Pega 8.5 supports nested Declare Trigger rules which means you can configure a Declare Trigger on the output of another trigger which
means when the first declare trigger rule is triggered it will update another value and then the second trigger rule will be the trigger that can
be used in process automation like sending notifications or update some other child table when a specific value is updated in Database
You can nest only the Save and Save and types of Declare Trigger rules that run immediately.
For faster application development, you can now define complex correlations between events in your case types by nesting Declare Trigger
rules. Declare Trigger rules invoke activities when a specified action takes place in a case. By nesting Declare Trigger rules, you avoid
implementing unclear logic in your application. You can nest as many levels of rules as your business use case requires. For example, in an
application for reviewing job candidates, you can create a Declare Trigger rule that starts a child case every time a candidate requires a
background check. When the background check is finished, the second Declare Trigger rule prompts your application to create a document
with the results and attach it to the case. Then another Declare Trigger rule invokes an activity that sends an email with the background
check results to the job candidate.
Below are the sample Declare Trigger rules which will be invoked when FirstName and FullName column is updated.
In this example, CalculateFullName Trigger Rule will be invoked when First Name is updated in the Database and
CalculateFullName  Activity is invoked to perform the required task/job which updates the FullName Property in Database which then
invokes the CalculatePetName Trigger Rule will be invoked when Full Name is updated in the Database and CalculatePetName
activity will be invoked


3985
Define fields in data objects intuitively


3986
Create conditions in an enhanced condition builder (8.5)
You can now increase the precision of your conditions by applying a new comparator in both App Studio and Dev Studio. With the new
comparator called instances include you can specify the number of fields in a group, such as phone models, and fields in an ordered list,
such as a list of addresses of a customer, that meet the condition that you configure in when rule. For example, as a sales representative,
you need to provide at least three black phones of a specific brand to your customer. By creating a when rule with two conditions, one for
the color, and one for the brand, and setting the instances include a comparator to is greater than or equal to 3, you can seamlessly and
quickly filter the results of Phone field group instances, as in the following example:

Below when rules will filter out all the IVR Model data from the ModelscoreList Property on Subscription.


3987
Estimate projects automatically in App Studio (8.5)
To help with planning development work, Pega now provides an automated Estimator tool in App Studio.
To open the Estimator tool:
In the navigation pane of App Studio, click Overview.
In the Application profile section, click Manage.
In the Application profile workspace, click Estimator.
In the estimator view,  you provide the following required values. The project estimator calculates the expected development duration:
Release -  select the release for which you want to calculate the estimate.
Delivery - select the implementation method that your development team uses - Scrum/Agile, Waterfall/Other.
Scrum maturity - select a value that describes the customer's experience with scrum projects - Low, Medium, High.
Number of teams - how many teams can work on the project.
Staffing model -  select a value that indicates the level of cooperation between the customer and Pega - co-production, non co-
production.
Environment - select the environment on which you want to deploy the application - Pega cloud, Existing on prem, New on prem.
Organization complexity - select an option that indicates how many levels and regulations your organization has - Low, High.
Data import effort -  select an option that describes the complexity level of the effort required to migrate data from the legacy system to
the new Pega system - Low, Medium, High.
Once you click Calculate estimate, the estimator calculates the expected development duration in hours and weeks, with a division
between Pega and customer hours. The estimator also includes detailed information about the number and complexity of the items in your
application, such as case types, personas, data objects, and features.
Pega link - Estimate projects automatically in App Studio (8.5) | Pega .


3988
System Administration


3989
Identify performance issues with queue processor and job scheduler activities
Improve the performance of your application’s activities, which often access databases or external services, by analyzing new alert
messages. When a queue processor activity or a scheduled job runs longer than the threshold value, Pega Platform™ now saves an alert
in the performance alert log. You can analyze these alerts directly in the log or by using Pega Predictive Diagnostic Cloud™ (PDC) to
identify and address potential performance issues with long-running processes.
For example, for a Queue Processor rule for sending emails to users, the Long-running queue processor threshold for the rule is 5000
milliseconds or 5 seconds. When the rule runs as scheduled, email processing takes 25 seconds, which exceeds the threshold. Pega
Platform saves the PEGA0117 alert: Long-running queue processor activity to the log file. Upon investigation, you discover that the cause
for the excessive processing time is an issue with network latency and the email server’s responsiveness. Therefore, you restart the email
server. The next time the send email queue process runs, the activity ends after 4.5 seconds, which is within the threshold, and no alert is
generated.
The following figure shows the threshold configuration for the Queue Processor rule:

The Long-running queue processor threshold for a dedicated queue process


3990
For more information about the possible reasons for the alerts, examples of the alerts, and steps involved in resolving issues, see:
PEGA0117 alert: Long-running queue processor activity
PEGA0118 alert: Long-running job scheduler activity


3991
Automatically update dependent applications to be built on the latest application
versions in an archive
When you import a product archive, you can now automatically update dependent applications to be built on the latest versions of the
dependent applications that you select. This can save time and reduce the errors that can occur when you manually update applications to
use new built-on application versions.
For example, if you are creating a product archive from the HR Services app, which contains MyDemoApp and Applicat, you can specify
that you want to update dependent applications for MyDemoApp and Applicat on the HR Services Product rule form, as shown in the
following figure:
Applications that are built on earlier versions of Applicat and MyDemoApp are automatically updated to be built on the latest versions after
you import the archive.


3992
Enhance your data sets with Apache HBase 2.1 and Hadoop 3.0 (8.5)
Pega Platform™ now supports Apache HBase to release 2.1 and Apache Hadoop Distributed File System (HDFS) to release 3.0. If you
store your enterprise data in HDFS and HBase clusters, you can use Pega Platform to perform read and write operations on the data in an
external Apache Hadoop ecosystem.
A Hadoop ecosystem provides a framework for dynamic, real-time processing of high-volume data. With Pega Platform, you can
access these large data sets and define them as data sources for your decision strategies and data flows.
The following diagram shows how Pega Platform connects to an external Hadoop ecosystem to read and write the data that is stored in
HBase and HDFS clusters:
1. Create an Instance of D a t a - A d m i n - H a d o o p Rule
2. Fill In Connection Details such as Hostname and select the configuration whether It is HDFS or HBase


3993
3. Refer Below Link for creating Data Set on HDFS

https://community.pega.com/knowledgebase/articles/decision-management/85/creating-hdfs-data-set-record
4. Refer below link for configuring hadoop settings for HDFS Connection
https://community.pega.com/knowledgebase/articles/decision-management/85/configuring-hadoop-settings-hdfs-connection


3994
Access and curate your data by using enhanced data APIs (8.5)
You can now easily access data in your UI React tables and organize your data efficiently with enhanced data APIs. By using data APIs,
you can sort, filter, and group data that you retrieve from Pega Platform™. For example, you can specify the maximum results that you
retrieve from a data page or sort the results by name.
Data APIs now include the following endpoints:
/data_views/{ID} - For fetching data from a data page
 /data_views/{ID}/count - For retrieving the total result count
/data_views/{ID}/metadata - For getting model information for a given data view ID
/data_objects - For getting a list of data objects for cases and data types, as well as default data pages
You can access the data APIs in Dev Studio, App Studio, and Admin Studio. The following figure shows the data APIs in Dev Studio:
Open PEGA API DX
1. Click on the below to launch to Pega API
2. Switch to V2 DX API from the Drop Down List available on Top Left Corner


3995
3. Navigate to Data Section to for Data APIs
4. Creare a Security Token using OAUTH 2.0 Client Registration to regiter the client authentication if the service package authentication is
OAUTH2
5. Click on Authorize button to populate authozation details as part of the service request.
6.  Enter Client ID & Client Secret that is registered as part of client registration step.


3996

7. Follow the steps mentioned in below article link which explains on how to create data view from  different sources.
https://community.pega.com/knowledgebase/articles/data-management-and-integration/85/updating-connection-details-and-mapping-data-
object
8. Request URL
https://pega.data.test.vodafoneaws.co.uk/prweb/api/application/v2/data_objects
Curl Command to Invoke the Service:
 curl -X GET "https://pega.data.test.vodafoneaws.co.uk/prweb/api/application/v2/data_objects" -H "accept: application/json" -H
 "Authorization: Bearer
eyJraWQiOiJkMmM4NTVjMTQ1NWI5YzQzOThkYTk4Mzk5MTU3ZDMzZCIsInR5cCI6IkpXVCIsImFsZyI6IlJTMjU2In0.eyJhdWQiOiJ1cm46
MTI0NzIyMDM0ODgzNzk4NjkwNDkiLCJzdWIiOiJyYWplbmRhcnJlZGR5LmFsbGFsYUBhZHF1cmEuY29tIiwiYXBwX25hbWUiOiJBT01GVy
IsIm5iZiI6MTYxNzYzNjU1MywiYXBwX3ZlcnNpb24iOiIwMS4wMy4wMSIsImlzcyI6InVybjpwZWdhLmRhdGEudGVzdC52b2RhZm9uZWF3cy


Gt5NCEP9aTZ5UKOEPvqECSHhNLdB1XVpQZbqVztlWaDuURFYxZ4S3mOzLHgIZH2Jy2JK25tQolCUuQhX8Q4xnXJaWHqPyqaRi2N0Ax
6PXTDL-eU5HCCechozJj7Q4eUPVknxjgoGnAlQ8IToDmyxKCmm9ciFrutRnaTJjBvcFyfq02kQkH2BYXG47l1BV527-JTZ-


3997
mdyHEyHon11aUjrzcbhDMt-
bAXWiSQ0WSeObB7i31VP6rLraSLsNsL4z7mp3bUpbNy0SvDVwVAPAFakB4XyWabuNp7A23x_lanSkyqTgvQKcmPpbgW3Oy7Gs_j6uz8
Enj7TF3-ZYrN1LnsBLcDkCsLMdny105nH7CZw"
Response JSON of Get Data Objects
 response_1617 …
05 Apr 2021, 04:02 PM43.json


3998
Decision Management


3999
Limit the number of active data flow runs (8.5)
You can now control how many data flow runs can be active at the same time by using the m a x _ a c t i v e _ r u n s dynamic system settings.
Configure a maximum number of concurrent runs that are allowed for a node type to ensure the optimal use of system resources. For
example, you can minimize the impact of multiple batch data flow runs on your system capacity.
If the limit is reached, the system queues subsequent runs and waits for active runs to stop or finish before queued runs can start. When the
Data Flow service has enough capacity, which means that there are fewer active runs for the node type than the configured limit, the oldest
queued runs start automatically.
Set the value to a number greater than zero to define a limit, for example, 10. You can use the special value –1 to indicate that the system
can schedule an unlimited number of runs in the service.

Go to Records → SysAdmin → Dynamic System Settings and search for max_active_runs on setting purpose column. Update any node
type to define a limit on DF run execution at the same time

If DF’s exceed the capacity which is defined in DSS, the upcoming DF’s are queued as below. Once the previous one is completed, the next
DF in the queue starts to run. Please note that below 2 DF’s are in Batch service so that It does not run more than 1(as defined in the DSS
above) DF at the same time

Please see that once the DF which is InProgress is completed, the queued DF is initialized as below


4001
Call authenticated APIs from any application (8.5)
You can call an API with any application to which a user has access, instead of with only the default application. This enhancement makes it
easy to switch between applications in the React UI, and to make API calls within your Pega application.
When you specify the application name in your application alias URL, at run time, the REST service chooses the access group in the
operator record that most closely corresponds with that application. Additionally, you can develop REST services without changing the
access group in the service package.
The following figure shows the application alias URLs available for each application to which an operator has access.
Invoking a REST service rule
Call a REST service rule from an external system to invoke an action in your application or retrieve data from Pega Platform. For example,
you can call a REST service to get the details of a case or assignment. You can specify the application context in which to run the API by
using the application alias URL.
1. To call a REST service rule, use api in the URL, and append the three-part key to the rule to the URL. Use the following syntax:
https://appname.pegacloud.io/contextroot/api/packageName/version/resourcepathURL
Although you can still call a REST service by specifying /PRRestService, as a best practice, use api.
2. To call an authenticated REST service in the context of the access group of a specific application, specify the application alias in the
endpoint URL:
If your application does not have an application alias, the system uses the application identifier.
For non-multitenant environments, enter: http://host/prweb/<servletname>/app/appAlias/api/<service package>/...


For multitenant environments, enter: http://host/prweb/<servletname>/app/appAlias/api/TenantHash/<service package>/...
For calls without a servlet, enter: http://host/prweb/app/appAlias/api/<service package>/...
For API service packages, enter: http://host/prweb/app/appAlias/api/...
For example:
The following access groups are listed in your operator record. To run a service in the context of the AG2 access group, invoke the following
application alias URL: http://host/prweb/<servletname>/app/app2/api.
AG1 application1 app1
AG2 application2 app2
AG3 application3 app3Access group Application Application alias


4002
Result:
The system chooses the first access group listed in the operator record that matches the application alias. The service then runs in the
context of the selected access group.


4003
Data Integration


4004
Control empty behavior in your JSON data transform
In a JSON Data Transform, you can now set the new field ‘Empty Behavior’ to control the mapping results when a property does not exist,
exists with an empty value, or exists with a non-empty value.
You can set ‘Empty Behavior’ with one of the following:
Default value – The serializer maintains the preexisting value. This configuration supports backward compatibility with releases that
precede Pega Platform™ 8.5.
Null – Represents a null value in JSON when the associated ClipboardPage or ClipboardProperty exists with an empty value or does
not exist.
Skip – Skips mapping in JSON when the associated ClipboardPage or ClipboardProperty exists with an empty value or does not exist.

Pega link - Control empty behavior in your JSON data transform (8.5)


4005
User Guide
How to Run the Loader Case
How to run BDC loader and add new BDC model files
Offers Landing Pages
Simulation
How to Run a Loader Case - Loading files
How to create a Renegotiation case with mock dataExpand all   Collapse all


4006
How to Run the Loader Case

[ Spine Loader  ] [ Configurations  ] [ Data Setup  ] [ Run Spine Loader  ] [ Frequently Occurring Problems  ]
Spine Loader
The spine is a Loader Case Subtype that loads all the spine entities file data into the AOM database tables

Configurations
CaseId SpineLoa
derL-19332 Identifier of the Spine
Loader Case
CaseStatu
sSpineLoa
derCompleted Case Status of the Spine
Loader Case
PauseCas
eSpineLoa
derFALSE This causes the case
(for the specified Case
Type) to pause and sent
to the Notify Support
flow when the Commit
Case State flow is
invoked.
SkipCaseF
inaliseEma
ilSpineLoa
derTRUE Global exclusion at case
subType level to skip the
finalise email regardless
of whether case
outcome was success,
elapsed or aborted
LoaderCh
eckPointsSpine 00:00-23:59 Comma separated list of
check point time ranges
in which the Case will be
allowed to run.
LoaderInc
omingPathSpine /mnt/share/aom/inbound/core/ The path of the incoming
directory where the
Loader will look for the
input files for the
specified type
LoaderLoo
pLimitSpine 10 The CheckTaskStaus
Activity in the Loader
Case is run in a loop to
check if the background ConfigTy
peConfigN
ameConfigValue Comments


4007
task that was initiated
has finished and this
limit is used to control
how many times it
should loop and also to
prevent an infinite loop
condition
LoaderNo
desSpine LoaderNode Designated NoteTypes
for the Loader Case to
run
CaseDepe
ndenciesSpineLoa
derSpineLoader,CCDExtractor,MSLoader,SpineV2Loader,BatchNBA Comma separated list of
depandant cases
Status of any of the
dependant cases is
running then the current
case will be blocked/wait
until that is completed
LoaderEnti
tyListSpine subscription,account,contact,product_holding,product_reference,subs_flex_attribute,su
bs_invoice_charge,address,tps,device
LoaderFile
AttributesSpine {"LoadType":"file", "Compressed":true, "Encrypted":true, "Mandatory":true,
"HasChecksum":true, "HasHeader":false, "Delimiter":"|", "S3TransferMode": "move"}Comma separated list of
entities for the specified
type
FileAttribut
esaccount {"ManifestFilePattern":"account_.*_.*.readme"} File Attributes for the
given Loader Sub Type
which include the file
type configurations
FileAttribut
esaddress {"ManifestFilePattern":"address_.*_.*.readme"} File Attributes for the
given Loader Sub Type
which include the file
type configurations
FileAttribut
escontact {"ManifestFilePattern":"contact_.*_.*.readme"} File Attributes for the
given Loader Sub Type
which include the file
type configurations
FileAttribut


given Loader Sub Type
which include the file
type configurations
FileAttribut
esdevice {"ManifestFilePattern":"device_.*_.*.readme"} File Attributes for the
given Loader Sub Type
which include the file
type configurations
FileAttribut
esproduct_h
olding{"ManifestFilePattern":"product_holding_.*_.*.readme"} File Attributes for the
given Loader Sub Type
which include the file
type configurations
FileAttribut
esproduct_r
eference{"ManifestFilePattern":"product_reference_.*_.*.readme"} File Attributes for the
given Loader Sub Type


4008
Data Setup
Copy all the entities mentioned in ConfigType =LoaderEntityList to be loaded onto path mentioned in the ConfigType
=LoaderIncomingPath
Files will be pushed by the Vodafone team on to S3 path (ConfigType =LoaderIncomingS3Path) on PROD whereas, in all lower
environments, we have to manually sync the files onto LoaderIncomingS3Path before running the loader by using the below AWS CLI
command
The above sync command syncs objects under a specified prefix and bucket to files in a local directory by uploading the local files to
s3.
Option --delete: Any files existing under the specified prefix and bucket but not existing in the local directory will be deleted.
In this example, the user syncs the bucket s3://vf-aom-uk-nonprod-eu-west-1-submissionbucket to the local current directory.
Upload all the files in the local current directory into /dev1/spine/folder on S3 Bucket
Run Spine Loader
Run the CaseIgnitor activity
Set the Parameter CaseSubType to BDC
Verify, if a new case instance is created from the Pega Dev Studio -->App Explorer--> Click on the VFUK-FW-AOMFW-Work-Loader
Class Instances and check the progress of the case
Frequently Occurring Problems
File can’t be found by the process
In most cases, it would be a config issue.
specially in the InputFilePattern/ManifestFilePattern values, all *(stars) should be preceded with .(dot)
Validate the JSON for both FileAttribues and LoaderFileAttributes config Type, In-valid JSON can cause issues
Input file issue, need to check the error and send the error sample to the source system to correct
 which include the file
type configurations
FileAttribut
essubs_flex


which include the file
type configurations
FileAttribut
essubs_flex
_attribute{"ManifestFilePattern":"subs_flex_attribute_.*_.*.readme"} File Attributes for the
given Loader Sub Type
which include the file
type configurations
FileAttribut
essubs_inv
oice_char
ge{"ManifestFilePattern":"subs_invoice_charge_.*_.*.readme"} File Attributes for the
given Loader Sub Type
which include the file
type configurations
FileAttribut
essubscripti
on{"ManifestFilePattern":"subscription_.*_.*.readme"} File Attributes for the
given Loader Sub Type
which include the file
type configurations
FileAttribut
estps {"ManifestFilePattern":"tps_.*_.*.readme"} File Attributes for the
given Loader Sub Type
which include the file
type configurations
1
2$ aws s3 sync <source> <target>
aws s3 sync . s3://vf-aom-uk-nonprod-eu-west-1-submissionbucket/dev1/spine/ --delete


4009
How to run BDC loader and add new BDC model files
[ Description  ] [ Configurations  ] [ Data Setup  ] [ Run BDC Loader  ] [ Frequently Occurring Problems  ]

Description
BDC Models and Features are moved to AOM within the Loader case as a new CaseSubType called BDC.
This data is provided from BDC Production S3 Bucket and written to the Cassandra datasets as a result of the Load model run, to be able
to use for Decisioning.

Configurations
LoaderCheckP
ointsBDC 00:00-23:00 Comma separated list of check point
time ranges in which the Case will be
allowed to run.
LoaderEntityLi
stBDC convergence_model,device_rec,universal_tariff_rec Comma separated list of entities for
the specified type
LoaderFileAttri
butesBDC { "LoadType": "file", "Encrypted": false, "Mandatory": false,
"HasChecksum": false, "HasHeader": false, "S3TransferMode": "move" }File Attributes for the given Loader
Sub Type which include the file type
configuraitons
LoaderIncomin
gPathBDC /mnt/share/aom/inbound/bdc/ The path of the incoming directory
where the Loader will look for the
input files for the specified type
LoaderIncomin
gS3PathBDC s3://vf-aom-uk-nonprod-eu-west-1-submissionbucket/dev1/bdc/ The full S3 path of the incoming
directory where the Loader will look
for the input files for the specified
type.
It must include a trailing / (slash)
LoaderLoopLi
mitBDC 25 The CheckTaskStaus Activity in the


LoaderLoopLi
mitBDC 25 The CheckTaskStaus Activity in the
Loader Case is run in a loop to check
if the background task that was
initiated has finished and this limit is
used to control how many times it
should loop and also to prevent an
infinite loop condition.
LoaderManifes
tArchiveS3Pat
hBDC s3://vf-aom-uk-nonprod-eu-west-1-submissionbucket/dev1/bdc_archive/The directory used by the all case
types to temporarily store archive
files.ConfigType Config
NameConfigValue Descrption


4010

Data Setup
Copy all the entities mentioned in ConfigType =LoaderEntityList to be loaded onto path mentioned in the ConfigType
=LoaderIncomingPath
Files will be pushed by the BDC team on to S3 path (ConfigType =LoaderIncomingS3Path) on PROD whereas in all lower
environments,                                                                                we
have to manually sync the files onto LoaderIncomingS3Path before running the loader by using the below AWS CLI command
The above sync command syncs objects under a specified prefix and bucket to files in a local directory by uploading the local files
to s3.
Option  --delete: Any files existing under the specified prefix and bucket but not existing in the local directory will be deleted.
In this example, the user syncs the bucket s3://vf-aom-uk-nonprod-eu-west-1-submissionbucket to the local current directory.
Upload all the files in the local current directory into /dev1/bdc folder on S3 Bucket
Below are the config updates to add a new BDC Pipeline to push data into the existing dataset
ManifestFilePattern:  Specifies the manifest/readme file pattern/regex
ClassName: Name of the existing Class
Dataset: Name of the existing dataset
Example: Adding new MODEL_XXXCaseDepende
nciesBDC BDCLoader Comma separated list of depandant
cases
Status of any of the dependant cases
is running then the current case will
be blocked/wait until that is
completed
CaseId BDC L-153265 Identifier of the BDC Loader Case
CaseStatus BDCLo
aderCompleted Case Status of the BDC Loader Case
PauseCase BDCLo
aderFALSE This causes the case (for the
specified Case Type) to pause and
sent to the Notify Support flow when


specified Case Type) to pause and
sent to the Notify Support flow when
the Commit Case State flow is
invoked.
SkipCaseFinali
seEmailBDCLo
aderTRUE Global exclusion at case subType
level to skip the finalise email
regardless of whether case outcome
was success, elapsed or aborted
1
2$ aws s3 sync <source> <target>
aws s3 sync . s3://vf-aom-uk-nonprod-eu-west-1-submissionbucket/dev1/bdc/ --delete
LoaderEntityList BDC universal_tariff_rec,ivr_model,device_rec,convergence_model,
<<MODEL_XXX>> Append the new
entity name to the
existing values
FileAttributes <<MODEL_XX
X>> {"ManifestFilePattern": "convergence_.*.readme", "ClassName": "VFUK-FW-
AOMFW-Data-BDCModel-Predictive", "Dataset": "ConvergenceModel"} Add new record for
new entityConfigType ConfigName ConfigValue Notes


4011
Below are the config updates to add a new BDC Pipeline,  by creating a new dataset
ManifestFilePattern:  Specifies the manifest/readme file pattern/regex
ClassName: Name of the Existing Class
Dataset: Name of the New dataset
Example: Adding new model_xxx and new dataset name is MODEL_XXX_DATASET
Run BDC Loader
Run the CaseIgnitor activity on the VFUK-FW-AOMFW-Work Class
Set the Parameter CaseSubType to BDC
Verify, if a new case instance is created from the Pega Dev Studio -->App Explorer--> Click on the VFUK-FW-AOMFW-Work-Loader
Class Instances and check the progress of the case
Frequently Occurring Problems
File can’t be found by the process
In most cases, it would be a config issue.
specially in the InputFilePattern/ManifestFilePattern values, all *(stars) should be preceded with .(dot)
Validate the JSON for both FileAttribues and LoaderFileAttributes config Type, In-valid JSON can cause issues
 LoaderEntityList BDC universal_tariff_rec,ivr_model,device_rec,convergence_model,
<<MODEL_XXX>> Append the new
entity name to the
existing values
FileAttributes <<MODEL_XX
X>> {"ManifestFilePattern": "convergence_.*.readme", "ClassName": "VFUK-FW-
AOMFW-Data-BDCModel-Predictive", "Dataset": "
<<MODEL_XXX_DATASET>>"} Add new record for
new entityConfigType ConfigName ConfigValue Notes


4012
Offers Landing Pages
Overview
Offers pages
Section Templates
Parent Single Action page
Parent with Children page
No Action Information Page
Creating a new template
Offer Hierarchy
Exception Handling Error Page
Troubleshooting
Overview
This page describes the Landing Pages displayed in the Offers Case(Microsite) and how the pages are populated with content. The
attributes used to display the pages are detailed below.
In the event of Landing Pages not displaying as expected, please check the relevant attribute(s) on the page and the value(s) returned in
Decision Data.
Offers pages
The Offers Landing Pages content is populated from attributes that are set in Decision Data - T2TVAttributes and T2TVActions. These are
returned from logic data flows in the Offers Case.
The attributes used to display each screen are detailed below. If any screens do not display as expected, the attribute values should be
checked first.
The value set in T2TVAttributes - TreatmentAttributes.SectionName determines which of the Offers screens to display.
Section Templates
Currently, we have 3 types of templates than can be used to configure an offer.
Parent Single Action page
It is used to display only parents with a single action and the template used for this is SingleActionInformationPage


4013
TreatmentAttributes.SectionName = "SingleActionInformationPage" (set in T2TVAttributes)
The page content is populated from the following name/value properties in TreatmentAttributes set in T2TVAttributes.
Action buttons are populated from T2TVActions Decision Data attributes - ActionTemplateType & ActionTemplateDetail.
There are currently 2 types of Action buttons – The Product Add On button and the Redirect button.
Parent with Children page
This is used if we want to display a single parent and one or more children. The template used for this is ParentWithCardChildren.HeaderSectionRule The header is shown with the Vodafone logo.This should be a valid Section rule name.
The existing Section name with the VF logo
should be H e a d e r A l i g n R i g h t
Header Hello Emma. Here’s a data offer just for you.Text
Body It’s great to see you’ve been making the
most of your data allowance…………..Text
ExtraLargeImageURL The background image is shown -
https://cdn.vodafone.co.uk/en/assets/images/
extralarge/IMG_vodafone_secondline_aom_
v1.jpgURL of the image.
LargeImageURL Background image when the screen size is
reduced to large -
https://cdn.vodafone.co.uk/en/assets/images/
large/IMG_vodafone_secondline_aom_v1.jp
gURL of the image.
MediumImageURL Background image when the screen size is
reduced to medium -
https://cdn.vodafone.co.uk/en/assets/images/
medium/IMG_vodafone_secondline_aom_v1
.jpgURL of the image.
FooterSectionRule Footer showed with ‘Terms & Conditions’ |
‘Privacy policy’ links and @ 2022 Vodafone
text.This should be a valid Section rule name.


text.This should be a valid Section rule name.
The existing Section name should be
F o o t e r D e f a u l t .TreatmentAttributes attribute For example on the screen above Notes
Product Add On ProductAddOn "[{"Name": "ButtonText", "Value":
"<<Set to button label>>"}]"eg. "[{"Name": "ButtonText",
"Value": "Buy Now"}]"
Redirect RedirectURL "[{"Name": "ButtonText", "Value":
"<<Set to button label>>"},
{"Name": "RedirectURL", "Value":
"<<Set to url to redirect to>>"}]"eg. "[{"Name": "ButtonText",
"Value": "Explore My Options"},
{"Name": "RedirectURL", "Value":
"Vodafone – Our Best Ever N
etwork | Now With 5G  "}]"Button type ActionTemplateType ActionTemplateDetail
attributesNotes


4014

TreatmentAttributes.SectionName = "ParentWithCardChildren" (set in T2TVAttributes)
The page content is populated from the following name/value properties in TreatmentAttributes set in T2TVAttributes.
For each Child, the card sections on the page are populated from the following name/value properties in the Child’s TreatmentAttributes :
HeaderSectionRule The header is shown with the Vodafone logo.This should be a valid Section rule name.
The existing Section name with the VF logo
should be H e a d e r A l i g n R i g h t
Header Hello Emma. Here’s a data offer just for you.Text
Body It’s great to see you’ve been making the
most of your data allowance…………..Text
ExtraLargeImageURL The background image is shown -
https://cdn.vodafone.co.uk/en/assets/images/
extralarge/IMG_vodafone_secondline_aom_
v1.jpgURL of the image.
LargeImageURL Background image when the screen size is
reduced to large -
https://cdn.vodafone.co.uk/en/assets/images/
large/IMG_vodafone_secondline_aom_v1.jp
gURL of the image.
MediumImageURL Background image when the screen size is
reduced to medium -
https://cdn.vodafone.co.uk/en/assets/images/
medium/IMG_vodafone_secondline_aom_v1
.jpgURL of the image.
BodyHeader Get your extra Text
FooterSectionRule Footer showed with ‘Terms & Conditions’ |
‘Privacy policy’ links and @ 2022 Vodafone
text.This should be a valid Section rule name.
The existing Section name should be
F o o t e r D e f a u l t .TreatmentAttributes attribute For example on the screen above Notes


4015
For this page, there are no Action buttons for the Parent section. Action buttons can be defined for the Child card sections.
Action buttons are populated from T2TVActions Decision Data attributes - ActionTemplateType & ActionTemplateDetail.
There are currently 2 types of Action buttons – The Product Add On button and the Redirect button.
No Action Information Page
This is used for displaying only offer which has no action and the template used for this is NoActionInformationPage.ImageSashText 50% discount Text
Header 1GB of data for only £XX a month Text
Body Your Data Extra will automatically renew
each month……Text
LargeImageURL Child card image - For 1GB -
https://www.vodafone.co.uk/en/assets/image
s/large/IMG_aom_vodafone_secondline_1gb
.jp . For 2GB -
https://www.vodafone.co.uk/en/assets/image
s/large/IMG_aom_vodafone_secondline_2gb
.jpgURL of the image.
MediumImageURL Child card image for medium screen size -
For 1GB -
https://www.vodafone.co.uk/en/assets/image
s/medium/IMG_aom_vodafone_secondline_
1gb.jpg . For 2GB -
https://www.vodafone.co.uk/en/assets/image
s/medium/IMG_aom_vodafone_secondline_
2gb.jpgURL of the image.
Footer This Data Extra will be added to the mobile
number……………TextTreatmentAttributes attribute For example on the screen above Notes
Product Add On ProductAddOn "[{"Name": "ButtonText", "Value":
"<<Set to button label>>"}]"eg. "[{"Name": "ButtonText",
"Value": "Buy Now"}]"
Redirect RedirectURL "[{"Name": "ButtonText", "Value":


"Value": "Buy Now"}]"
Redirect RedirectURL "[{"Name": "ButtonText", "Value":
"<<Set to button label>>"},
{"Name": "RedirectURL", "Value":
"<<Set to url to redirect to>>"}]"eg. "[{"Name": "ButtonText",
"Value": "Explore My Options"},
{"Name": "RedirectURL", "Value":
"Vodafone – Our Best Ever N
etwork | Now With 5G  "}]"Button type ActionTemplateType ActionTemplateDetail
attributesNotes


4016

TreatmentAttributes.SectionName = "NoActionInformationPage" (set in T2TVAttributes)
The page content is populated from the following name/value properties in TreatmentAttributes set in T2TVAttributes.
There are no Action buttons for this page.
Creating a new template
·         All the new templates need to be created as sections in PegaMKT-Work-Microsite-Offers (Case appliesTo) class. Before creating a
template in AOM, need to get the html required to create a template from the relevant team (UX/UI).
HeaderSectionRule The header is shown with the Vodafone logo.This should be a valid Section rule name.
The existing Section name with the VF logo
should be H e a d e r A l i g n R i g h t
Header Hello Emma. Here’s a data offer just for you.Text
Body It’s great to see you’ve been making the
most of your data allowance…………..Text
ExtraLargeImageURL The background image is shown -
https://cdn.vodafone.co.uk/en/assets/images/
extralarge/IMG_vodafone_secondline_aom_
v1.jpgURL of the image.
LargeImageURL Background image when the screen size is
reduced to large -
https://cdn.vodafone.co.uk/en/assets/images/
large/IMG_vodafone_secondline_aom_v1.jp
gURL of the image.
MediumImageURL Background image when the screen size is
reduced to medium -
https://cdn.vodafone.co.uk/en/assets/images/
medium/IMG_vodafone_secondline_aom_v1
.jpgURL of the image.
FooterSectionRule Footer showed with ‘Terms & Conditions’ |
‘Privacy policy’ links and @ 2022 Vodafone
text.This should be a valid Section rule name.


text.This should be a valid Section rule name.
The existing Section name should be
F o o t e r D e f a u l t .TreatmentAttributes attribute For example on the screen above Notes


4017
·         All the templates will be included in the main section, called Offers, dynamically based on TreatmentAttributes(SectionName) of the
offer returned from dataflow. The name of the Section rule created for a new template needs to match the SectionName in
TreatmentAttributes.
·         Please update the appropriate decision data discussed in the above sections to return the details as part of the data flow.
·         As we have a standard header and footer for all the current templates, we have created common Header and Footer sections that
can be reused.
o    Header - H e a d e r A l i g n R i g h t
o    Footer - F o o t e r D e f a u l t
Please create new rules if any of them is different to existing templates, by referring to the above corresponding header or footer sections.
·         Create a new section that has an HTML body implemented
·         We already have actions (e.g., buttons, links) defined in the SingleActionCard Section class.
o    If we need to add new action please update the section accordingly.
o    The new action needs to come as ActionTemplateType in TreatmentAction which will be returned as part of dataflow.
Offer Hierarchy
Parent and child offers presented on the landing page will follow a parent/child class hierarchy. Please find details below:
Parent offer - VFUK-FW-AOMFW-UI-Microsite-Offer-MainOffer
Child - VFUK-FW-AOMFW-UI-Microsite-Offer
 VFUK-FW-AOMFW-UI-Microsite-Offer Class VFUK-FW-AOMFW-UI-Microsite-Offer
VFUK-FW-AOMFW-UI-Microsite-Offer-
MainOfferClass (Parent) VFUK-FW-AOMFW-UI-Microsite-Offer-
MainOffer


MainOffer
OfferSR Page(VFUK-AOMFW-SR) VFUK-FW-AOMFW-UI-Microsite-Offer
TreatmentAttributes ValueGroup VFUK-FW-AOMFW-UI-Microsite-Offer
TreatmentActions PageList(VFUK-AOMFW-SR) VFUK-FW-AOMFW-UI-Microsite-Offer
Children PageList(VFUK-FW-AOMFW-UI-Microsite-
Offer)VFUK-FW-AOMFW-UI-Microsite-Offer-
MainOfferRule Name Type Class


4018
Exception Handling Error Page
There is only one common exception handling page and displays for all flow exceptions and errors in the Offers Case. The exception page
HTML is configurable and is currently configured in the AOMConfig data type. Please find the details below:

All attributes are set from the following record in AOMConfig (shown here with example ConfigValue):
ConfigType: ExceptionTemplateAttributes
ConfigName: OffersMicrosite
ConfigValue:
{
"PageTitle": "Oops",
"Header": "Sorry, that didn't work",
"Body": "We're sorry, we weren't able to process your request. Please click below to check out your options",
"ExtraLargeImageURL": "Vodafone – Our Best Ever Network | Now With 5G
"LargeImageURL": "Vodafone – Our Best Ever Network | Now With 5G
"MediumImageURL": "Vodafone – Our Best Ever Network | Now With 5G
"ButtonText": "Explore My Options",
"ButtonURL": "Vodafone logo
}
Troubleshooting

Text content not displaying as expected
(Header or Body)Check AOMConfig entry for individual
attributes - Header & Body
Button text not displaying as expected Check AOMConfig entry - ButtonText
attribute
The button does not redirect to the expected
URLCheck AOMConfig entry - ButtonURL
attribute
Background image not displaying as
expectedCheck AOMConfig entries -
ExtraLargeImageURL, LargeImageURL,
MediumImageURLThe different size images are used
depending on the screen size.Problem Check Notes


4019
Simulation
Overview
Running a Simulation
Types
Base Line Data Settings
Execution Modes
BatchNBA
GetNBA
TIL
Output
Overview
We use simulations to simulate the decisioning for customers in batch and realtime customers. To use OOB simulation, we need some
manual steps to get the desired summary output. To overcome this, the Simulation case has been introduced to automate the process. This
document briefs on how to run the simulation case using the portal.
Running a Simulation

To run the simulation, we need to use the simulation portal. Go to 1. Launch portal --> 2. AOMManagement
Next, click 1. Simulation --> 2. Create New
Now configure the Simulation case that you wish to create


4020

Types
Currently, the simulation case supports 3 types of simulation Types
1. Funnel - gives the statistics of an offer in the framework at each funnel. It can drill down and see how different components influence
decision outcomes
2. Distribution - used to inspect the number of actions offered in general, the number of actions across various channels, the average
propensity of the actions, the ranks at which each action is offered, and so on. This is particularly useful when creating or changing an
action and understanding the possible implications of that change.
3. Customer - can track at which funnel the customer is passed/dropped and gives the statistics per an Individual Customer in the
framework
Base Line Data Settings
The simulation case supports the following base line data settings:
1. No base line data
2. Create new Base Line data - a new baseline dataset will be created for the selected Simulation Type after truncating the current dataset
if it existed already
3. Use existing Base Line data - run the simulation on the previously created baseline dataset for the selected Simulation Type
Selecting this option does not require Execution Mode-specific fields outlined in the “Execution Modes” section below
Execution Modes
The simulation supports the following execution modes:
1. BatchNBA: Simulation is executed for the selected customers who are in AOM subscription spine


4021
Segments are used for customer selection
2. GetNBA: Simulation is executed for the selected customers who have interacted via GetNBA API
Customer along with context are stored in the inbound_subscription_context table as part of GetNBA call which will be the source
for GetNBA simulation
3. TIL: Simulation is executed for the selected customers who have interacted via GetBundleEvent API
Customer along with context are stored in the bundle_event_context table as part of TIL call which will be the source for TIL
simulation
BatchNBA
1. Select or type in a Segment from the above dropdown. Only segments that begin with “SIM_” are displayed in the dropdown
2. Optionally, you can choose to refresh the segment during the run
GetNBA
1. Select a Channel which enables the Sub Channel dropdown selection
2. Select a Sub Channel, which enables Primary Context selection. If “N/A” is the only Primary Context (and hence the only Secondary
Context), these values are selected automatically
3. Select a Primary Context, which enables Secondary Context selection. If “N/A” is the only Secondary Context, this value is selected
automatically
4. Select a Secondary Context
Each subsequent dropdown contains a list of values based on the selected previous GetNBA properties i.e. only a combination existing in
inbound_subscription_context can be selected.
5. & 6. After all four of these properties are selected, a date range needs to be chosen. Only customers with request dates in this range will
be processed from inbound_subscription_context
The minimum and maximum date is calculated based on this request data. The date range must be within this minimum/maximum.
In this example, the Primary Context “T radeIn” is the only option
for Channel: Retail, Sub Channel: Basket


4022
TIL
1. Select or type in a value for NTID from the dropdown
2. & 3. After the NTID is selected, a date range needs to be chosen. Only customers with request dates in this range will be processed from
bundle_event_context
The minimum and maximum date is calculated based on this request data. The date range must be within this minimum/maximum.
Output
Based on type and execution mode (for Customer type), the simulation case will output the results to the corresponding table. Below are the
details:

Funnel Any simulation_funnel_summary
Distribution Any simulation_distribution_summary
Customer BatchNBA simulation_funnel_batchnba
GetNBA simulation_funnel_getnba
TIL simulation_funnel_tilType ExecutionMode Output Table


4023
How to Run a Loader Case - Loading files
Step1: Update AOMConfig Data Type
Step2: Load latest Data files on S3 Bucket
Step3: Run Loader Case
Step1: Update AOMConfig Data Type
As per below screenshot, ensure that AOM config has correct values for LoaderEntityList. For example, if a new Loans view has been
added in the database then it should have an entry here. If you’re unsure what values should be included in LoaderEntityList please search
the file name provided by data team as per 2nd screenshot below. As best practice, please ensure to take a backup of AOMConfig
before you make changes and once tested import backup file including your changes and test again.
AOMConfig LoaderEntitiyList:
Search for right ConfigName:
Step2: Load latest Data files on S3 Bucket
First login to realtime/appserver as per below screen shot and create a copy of the files supplied by the data team in your folder. If you don't
currently have a folder best to create one as per below and then copy files.
Open MPutty & Login to bastion by using Authy:


4024
Copy the verification code using the copy button on Authy and do a right click on MPutty to paste it. Once done, leave the bastion session
open and open appserver
Setting permissions to get access
If you are getting the Permission denied error, instead of using root user to open protected directories, change to the correct user first.
Use sudo -i and then sut to change to tomcat user.
Use below commands to get to the right location and create your folder:


4025
cd => change directory command to go to the right directory
ll => show list of items in the folder you’re in
mkdir => create new directory
Once your folder is created, go to the location where the latest files are stored by the data team and copy and paste them into your new
folder ready to be Synced into S3 Bucket location. Location where the data team has placed files will be in their email as per below sample
email:
Sample email from Data Team:
Commands to copy files from above location into your folder:
cp -p  *.zip => Copy and Paste all Zip files form the current directory into destination directory (which should be the folder you’ve
created)
Create our own dummy data:
To check the data in existing file use command:


4026
cat filename
eg. cat device_20200714000000_full_00.dsv.csv
The empty lines represent null values. You can insert dummy data into the database table using SQL and then export the file into csv
format. Remove the column names on top of the csv file and ensure that it is converted to dsv format. You can do manually by replacing
the commas with delimeters e.g.
Import this file into your own folder - /home/name using winscp or you can import using import button in MobaXterm.
Then copy this file from your file into /mnt/share/aom/... using copy command in terminal
Make sure the folder is in tomcat and not root by using the command : chown tomcat:tomcat foldername
For files - chown tomcat:tomcat filename
Once the dsv file is uploaded into the folder, the file needs to be in zipped, encrypted and put into readme format.
To zip file, first check if you have zip installed by running this command zip --version
If the program returns the program version then you can simply zip the file using the command -
zip filename


4027
Otherwise, first install zip - sudo apt install zip unzip, then run the command once installed
Zip command - zip device_202302151149_full_00.dsv.csv.zip device_202302151149_full_00.dsv.csv
To encrypt use the following command
gpg --homedir /mnt/share/aom/.gnupg --yes --batch --output device_202302151149_full_00.dsv.csv.zip.gpg --recipient
aomdomain@internal.vodafone.com --encrypt device_202302151149_full_00.dsv.csv.zip
To decrypt use the following command - useful for decrypting an existing file to make an update to that file
gpg --homedir /mnt/share/aom/.gnupg --yes --batch --passphrase passphrase --output device_202302151149_full_00.dsv.csv.zip --decrypt
device_202302151149_full_00.dsv.csv.zip.gpg
Make sure the file is tomcat and not root!
Make checksum file
cksum device_202302151149_full_00.dsv.csv.zip.gpg > device_202302151149_full_00.dsv.csv.zip.gpg.cksum
Make readme file by creating a new file called device_202302151149_full.readme - this should be in format specified in AOMconfig in
file attributes
Command for new file - touch device_202302151149_full.readme
Then copy device_202302151149_full_00.dsv.csv.zip.gpg file into that file by using command -
echo device_202302151149_full_00.dsv.csv.zip.gpg > device_202302151149_full.readme
This file can then be copied into the core folder and sync process can start as mentioned below.
Adding data to new columns in an existing file using linux :


Adding data to new columns in an existing file using linux :
sed -i 's/$/|1-4SJJBKT/' account_20210113090447_delta_00
Sync all required files from your folder onto the correct S3 Location:
Check the required S3 location in AOMConfig before you sync as per below:
aws s3 sync => Performs sync by taking all files from current folder and loading them onto destination S3 folder with --delete option
which deletes all existing files at destination folders and loads all files from source


4028
Step3: Run Loader Case
Search for CaseIgnitor Activity and open the one is Loader class as per below Screenshot:

Run the activity for Correct CaseSubType, for example use ProductCatalogue to load Catalogue data and Spine for Spine data:
To Monitor Case progress go to below landing page and click on the instance of your run and go to Audit section. If completed successfully
you’ll see a “Resolved-Completed” status if not there will be errors in the Audit to help you understand why case has failed:
You can also find any detail error message in index_status table by searching your case id.


4030
How to create a Renegotiation case with mock data
Step1
Create necessary mock services and update mashup Data transform for renegotiation case
Mashup Name: Mashup_Mock_Renegotiation DataTransform - You can save as and update CaseId and DealId with your previous case,
according to the test scenario.
Validate Basket Mock Service:  You can use your ValidateBasket Graph for VB response, according to the test scenario.
Get Customer Mock Service: You can use your GetCustomer Graph for GC response, according to the test scenario. You can skip it, if
your previous case has the same day.
Step2
Save a recommendation in the previous case.
There are two ways to do that:
1. Click Select button for any of recommendations and close the case.
2. Add Save=True property in the recommendation level in your GR mock service for one of the recommendations.
All setup is done for the previous case.
Step3
Use the corresponding VB mock service and GC mock service(if required) for the test scenario and then launch the VADR with a
renegotiation mashup.
Don't forget to update the recommendation page in your VB response graph while working on your VB mock service.
Because eventually, your recommendation which is saved in the previous case will be replaced with whatever you put in the VB response.


4031
Run Simulation
Overview
Simulation Preprocess
SimulationPreProcess activity
InsertSimulationLookupData
SubscriptionDataForBatchNBA
 Create and Run Simulation
CreateSimulation activity
SetupSimulation DataT ransform
SetupDestinationForFunnel DataT ransform
SetupDestinationForDistribution DataT ransform
RunSimulation activity
CheckSimulationRun activity
Post Processing (TBD)
Overview
This document covers how to run the simulation without using a simulation landing page. This document covers create and run of Funnel
and Distribution simulation types.
Simulation Preprocess
We need to run some preprocessing steps to set up the data for simulation.
SimulationPreProcess activity
 The VFUK-FW-AOMFW-Work.SimulationPreProcess activity will do the following steps to achieve this.
InsertSimulationLookupData
The simulation_lookup table contains proposition data and this is needed when we run queries to view the simulation funnel output.
SubscriptionDataForBatchNBA
SubscriptionDataForBatchNBA is used as an input for both simulations. Before running the simulation we need to make sure the
SubscriptionDataForBatchNBA has the updated customer data with intents.
This activity is used to load the simulation_lookup table with the latest proposition data by calling VFUK-FW-AOMFW-Data-
Subscription.InsertSimulationLookupData activity and load the SubscriptionDataForBatchNBA dataset using PrepareDataForBatchNBA
dataflow
Applies To VFUK-FW-AOMFW-Work
Ruleset TBD
Input
Parameter
sN/ASimulationPreProcess


4032
 Create and Run Simulation
Creating simulation involves creating a page of type Data-Decision-Simulations and updating the required values.
CreateSimulation activity
SetupSimulation DataTransform
SetupDestinationForFunnel DataTransformOutput
Parameter
sN/A
Error
HandlingPrimary Catch-all Error Handler: Catches all the unhandled Exceptions or Errors in the activity
This activity will set data required pages pyOptions, pyDataSource, pyStrategy, and pyDestinations pages of Data-Decision-Simulations for
running a simulation based on SimulationType and  SimulaitonName parameter. Then create and run simulation work-item.
Applies To VFUK-FW-AOMFW-Work
Ruleset TBD
Input
Parameter
sSimulaitonName, SimulationType
Output
Parameter
sN/A
Error
HandlingPrimary Catch-all Error Handler: Catches all the unhandled Exceptions or Errors in the activityCreateSimulation
SetupSimulation DT set data in pyOptions, pyDataSource, pyStrategy, and pyDestinations pages of Data-Decision-Simulations. Sets the
pyDestinations page differently based on SimulationType
Applies ToData-Decision-Simulations
Ruleset TBD
Input
Parameter
sSimulaitonType
Output
Parameter
sN/ASetupSimulation
SetupDestinationForFunnel DT set data in pyDestinations pages of Data-Decision-Simulations for Funnel type simulationSetupDestinationForFunnel


4033
SetupDestinationForDistribution DataTransform
RunSimulation activity
CheckSimulationRun activityApplies ToData-Decision-Simulations
Ruleset TBD
Input
Parameter
sN/A
Output
Parameter
sN/A
SetupDestinationForFunnel DT set data in pyDestinations pages of Data-Decision-Simulations for Distribution type simulation
Applies ToData-Decision-Simulations
Ruleset TBD
Input
Parameter
sN/A
Output
Parameter
sN/ASetupDestinationForFunnel
RunSimulation activity calls the pxSubmitAndRun activity passing SimulaitonID so that the corresponding Simulation gets started.
Applies To VFUK-FW-AOMFW-Work
Ruleset TBD
Input
Parameter
sSimulaitonID
Output
Parameter
sN/A
Error
HandlingPrimary Catch-all Error Handler: Catches all the unhandled Exceptions or Errors in the activityRunSimulation
CheckSimulationRun


4034

Post Processing (TBD)
TBD
 RunSimulation activity calls the pxSimulationLoadProgress activity which loads simulation progress in the Data-Decision-SimulationProgress
page.
Applies To VFUK-FW-AOMFW-Work
Ruleset TBD
Input
Parameter
sSimulaitonID
Output
Parameter
sN/A
Error
HandlingPrimary Catch-all Error Handler: Catches all the unhandled Exceptions or Errors in the activity


4035
Application Versions
Overview
Releases
AOMFW
AOM
Artefacts to deploy to switch any application version to Live
914098: Designing the process to support feature-based releases
Deployment to make an Application Version Live
VF Confluence LinksExpand all   Collapse all


4036
Overview
Application V ersioning
System Architecture
Example Flow
VADR.Administrators ( Trunk Application V ersion/ Live Application V ersion)
VADR.Administrators.Charlie ( PostMVP+ Apple Lovers Application V ersion )
PM Tool

Application Versioning
Application versioning is a way to differentiate current and past application configurations. Rule resolution can look through all the minor and patch versions for the current major ruleset.
Application components include the application ruleset stack — which contains the rules and data types used by the application. To version an application, you must version the application's rulesets.
The below diagram explains the low-level flow of how the application version works with all the rules involved in AOM context

An Operator accessing the pega application in any form like Mashup/API/Dev Studio etc would be mapped to an Access Group which authorizes access to the right rules to get the expected
result/response.
An Access group would be mapped to a specific Application rule version which authorizes a version of the code base to be executed for all the operators mapped to this Access Group
Authentication Profile is used by the Connector rules in Pega to invoke an External API, this rule encapsulates the user credentials for the source system to authenticate the user and respond

System Architecture
The below diagram talks about how the different systems using AOM communicate with the application versioning in the context.
VADR Application can integrate with multiple application versions in parallel from AOM at any given point in time ( but vice-versa is not true) using multiple operators and access-group discussed in
the above section
TIL/Tealium/Microsite can integrate with only one application version from the multiple versions available in AOM at any given point in time, due to technical limitations in the source systems


4037

Example Flow
Below is the example flow of user/operator using different application versions and how the UI changes can be displayed accordingly to the access group
dilek.basaran2 is the operator used in the below example
dilek.basaran mapped to VADR.Administrators which is trunk code base R3.05 application version
dilek.basaran2 mapped to VADR.Administrators.Charline which is R3.05 + PostMVP+ Apple Lovers application version
VADR.Administrators ( Trunk Application Version/ Live Application Version)

1. Below is the screenshot of the dilek.basaran Operator mapped to VADR.Administrators which in turn is mapped to the VADR:01.01.01 application version

2. The same use is logging Upgrade Journey from VADR using Mashup and pega prompts for credentials
       Note: This is not applicable for Call Centre agents as SSO is in place in the PROD environment hence the user will not be prompted for credentials again as they are logged into
Halo( Siebel) already.


4038
3. As displayed below, we can see the Upgrade Case launched and recommendations are displayed.
    VFT together icon highlighted in the screenshot below is displayed, which is applicable to the VADR:01.01.01 application version

VADR.Administrators.Charlie ( PostMVP+ Apple Lovers Application Version )
1. Below is the screenshot of the dilek.basaran2 Operator mapped to VADR.Administrators.Charlie which in turn is mapped to the VADR:01.04.01 application version ( PostMVP+ Apple Lovers
Application Version )


4039
2. The same use is logging Upgrade Journey from VADR using Mashup and pega prompts for credentials
       Note: This is not applicable for Call Centre agents as SSO is in place in the PROD environment hence the user will not be prompted for credentials again as they are logged into
Halo( Siebel) already.

3. As displayed below, we can see the Upgrade Case launched and recommendations are displayed.
      The new VFT together icon highlighted in the screenshot below is displayed, which is applicable to the VADR:01.04.01 application version


4040
PM Tool
Business users log in to their respective application versions to create/update the catalogue version.
PMTool also supports pushing the version into the respective catalogue version into the AOM application version.
The below diagram explains one-to-one mapping between the catalogue version and the AOM application version.


4042
Releases
Releases & App Version Mapping
R3.5
R3.6
R3.7
R4.1 And R4.2
R4.3
R4.4
R4.5
R4.6

Build Package Propagation

The application version build is the same regular build process where the required rules will be packaged and deployed into the target
environment.
Access to the rules on the target is controlled by the access group specific to the application version and is available to a specific user only
In, PROD a feature which is part of the application version is available to the super agent user only.
Once, the business users are happy with the feature then, a new build package needs to be cut from Dev which includes access group
changes, API Operators etc to point to the relevant application version so that all the agents are not moved to this application version in
context


4043
Releases & App Version Mapping
R3.5 R3.5 Core
ReleaseVADR:
01:01:01AOM:
01:03:01
AOMFW:
01:03:01NA(Live
)Once this application version code is deployed, it will be available to all users
which means application code will be Live by default
Apple
Lovers
Renegotiatio
n
Commission
ing VADR:
01:04:01AOM:
01:04:01
AOMFW:
01:04:01Charlie Deployed as Feature release. Needs further deployment once business clears
FUT testing cycle on PROD to make it Live ( available to all users)
R3.6 R3.6 Core
ReleaseVADR:
01:05:01AOM:
01:05:01
AOMFW:
01:05:01NA(Live
)Once this application version code is deployed, it will be available to all users
which means application code will be Live by default
Mobile
Broadband VADR:
01:06:01AOM:
01:06:01
AOMFW:
01:06:01Alpha Deployed as Feature release. Needs further deployment once business clears
FUT testing cycle on PROD to make it Live ( available to all users)
R3.7 R3.7 Core
ReleaseNone AOM:
01:07:01
AOMFW:
01:07:01NA(Live
)Once this application version code is deployed, it will be available to all users
which means application code will be Live by default
No Features based application version requested by Business


which means application code will be Live by default
No Features based application version requested by Business
R4.1 R4.1 Core
ReleaseVADR:
01:08:01AOM:
01:08:01
AOMFW:
01:08:01NA(Live
)Once this application version code is deployed, it will be available to all users
which means application code will be Live by default
5G Ultra VADR:
01:010:0
1None Beta Deployed as Feature release. Needs further deployment once business clears
FUT testing cycle on PROD to make it Live ( available to all users)
R4.2 R4.2 Core
ReleaseVADR:
01:08:01AOM:
01:08:01
AOMFW:
01:08:01NA(Live
)There is no new application for R4.2 and developed in existing version 01:08:01Relea
seFunctionali
tiesVADR
App
VersionAOM App
VersionAccess
GroupComments


4044
 No Features based application version requested by Business
SOHOSOHO VADR:
01:08:01AOM:
01:08:01
AOMFW:
01:08:01NA(Live
)There is no new application for SOHO and developed in existing version
01:08:01
No Features based application version requested by Business
R4.3 R4.3 Core
ReleaseVADR:
01:09:01AOM:
01:09:01
AOMFW:
01:09:01NA(Live
)Once this application version code is deployed, it will be available to all users
which means application code will be Live by default
No Features based application version requested by Business
R4.4 R4.4 Core
ReleaseVADR:
01:11:01AOM:
01:11:01
AOMFW:
01:11:01NA(Live
)Once this application version code is deployed, it will be available to all users
which means application code will be Live by default
FUT
ChangesVADR:
01:012:0
1AOM:
01:12:01
AOMFW:
01:12:01Alpha Deployed as Feature release for Alpha users. Needs further deployment once
business clears FUT testing cycle on PROD to make it Live ( available to all
users)
Retail VADR:
01:015:0
1AOM:
01:15:01
AOMFW:
01:15:01Charlie Deployed as Feature release for Charlie users. Needs further deployment once
business clears FUT testing cycle on PROD to make it Live ( available to all
users)


business clears FUT testing cycle on PROD to make it Live ( available to all
users)
R4.5 R4.5 Core
ReleaseVADR:
01:13:01AOM:
01:13:01
AOMFW:
01:13:01NA(Live
)Once this application version code is deployed, it will be available to all users
which means application code will be Live by default
Retail VADR:
01:015:0
1AOM:
01:15:01
AOMFW:
01:15:01Charlie Deployed as Feature release for Charlie users. Needs further deployment once
business clears FUT testing cycle on PROD to make it Live ( available to all
users)
R4.6 R4.6 Core
ReleaseVADR:
01:16:01AOM:
01:16:01
AOMFW:
01:16:01NA(Live
)Once this application version code is deployed, it will be available to all users
which means application code will be Live by default
No Features based application version requested by Business
Core/Default Release Application VersionLegends


4045
 Feature based application Version


4046
R3.5
List of Application versions as part of R3.5 release
For more details on below access groups, refer to Access Groups page.
01.03.01

01.04.0101.03.01 R3.05
01.04.01 PostMVP, Apple LoversApplication Versions Features/Releases

VADR 01.03.01VADR:AssistedAgents NA Access Group for Call Centre
agents
VADR:Administrators NA Access Group for Application
developers

AOM 01.03.01AOM:API VFUK.VADR
AOM:API VFUK.TIL
AOM:Mailjet api@mailjet.com
AOM:RulesAdmins NA Access Group for Application
developers

AOMFW 01.03.01AOMFW:Tealium VFUK.Tealium
AOMFW:MSUnauthenticated Microsite
AOMFW:AssistedAgents VFUK.Assisted.Agent
AOMFW:Administrators NA Access Group for Application
developers
AOMFW:MarketManager NA Access Group for Logic
developers
AOMFW:PegaMarketManager NA Access Group for Logic
developersApplication Version Access Group Operator Notes
VADR 01.04.01VADR:AssistedAgents.Charlie NA Access Group for Call Centre
agentsApplication Version Access Group Operator Comments


4047
 VADR:Administrators.Charlie NA Access Group for Application
developers

AOM 01.04.01AOM:API.Charlie VFUK.VADR.Charlie
AOM:API.Charlie VFUK.TIL.Charlie
AOM:Mailjet.Charlie api.charlie@mailjet.com
AOM:RulesAdmins.Charlie NA Access Group for Application
developers
AOMFW 01.04.01AOMFW:Tealium.Charlie VFUK.Tealium.Charlie
AOMFW:MSUnauthenticated.Ch
arlieMicrosite
AOMFW:AssistedAgents.CharlieVFUK.Assisted.Agent.Charlie
AOMFW:Administrators.Charlie NA Access Group for Application
developers
AOMFW:MarketManager.CharlieNA Access Group for Logic
developers
AOMFW:PegaMarketManager.C
harlieNA Access Group for Logic
developers


4048
R3.6
List of Application versions as part of R3.6 release

For more details on below access groups, refer to Access Groups page.
01.05.01

01.06.0101.05.01 R3.06
01.06.01 MBBApplication Versions Features/Releases

VADR 01.05.01VADR:AssistedAgents NA Access Group for Call Centre
agents
VADR:Administrators NA Access Group for Application
developers

AOM 01.05.01AOM:API VFUK.VADR
AOM:API VFUK.TIL
AOM:Mailjet api@mailjet.com
AOM:RulesAdmins NA Access Group for Application
developers

AOMFW 01.05.01AOMFW:Tealium VFUK.Tealium
AOMFW:AssistedAgents VFUK.Assisted.Agent
AOMFW:Administrators NA Access Group for Application
developers
AOMFW:MarketManager NA Access Group for Logic
developers
AOMFW:PegaMarketManager NA Access Group for Logic
developersApplication Version Access Group Operator Notes

VADR 01.06.01VADR:AssistedAgents.Alpha NA Access Group for Call Centre
agentsApplication Version Access Group Operator Comments


4049
 VADR:Administrators.Alpha NA Access Group for Application
developers

AOM 01.06.01AOM:API.Alpha VFUK.VADR.Alpha
AOM:API.Alpha VFUK.TIL.Alpha
AOM:Mailjet.Alpha api.alpha@mailjet.com
AOM:RulesAdmins.Alpha NA Access Group for Application
developers

AOMFW 01.06.01AOMFW:Tealium.Alpha VFUK.Tealium.Alpha
AOMFW:AssistedAgents.Alpha VFUK.Assisted.Agent.Alpha
AOMFW:Administrators.Alpha NA Access Group for Application
developers
AOMFW:MarketManager.Alpha NA Access Group for Logic
developers
AOMFW:PegaMarketManager.Al
phaNA Access Group for Logic
developers


4050
R3.7

List of Application versions as part of R3.7 release.

01.07.01
There are no changes in the VADR application so no new application version was created.01.07.01 R3.07Application Versions Features/Releases

AOM 01.07.01AOM:API VFUK.VADR
AOM:API VFUK.TIL
AOM:Mailjet api@mailjet.com
AOM:RulesAdmins NA Access Group for Application
developers

AOMFW 01.07.01AOMFW:Tealium VFUK.Tealium
AOMFW:AssistedAgents VFUK.Assisted.Agent
AOMFW:Administrators NA Access Group for Application
developers
AOMFW:MarketManager NA Access Group for Logic
developers
AOMFW:PegaMarketManager NA Access Group for Logic
developers
AOMFW:MSUnauthenticated NA Access Group for microsite user
PegaNBAM:Agents NA Access Group for OOTB agentsApplication Version Access Group Operator Notes


4051
R4.1 And R4.2

List of Application versions as part of R4.1 and R4.2 release

01.08.01
 01.08.01 R4.01 and R4.02
01.10.01 5G Ultra - Only for VADRApplication Versions Features/Releases

VADR 01.08.01VADR:AssistedAgents NA Access Group for Call Centre
agents
VADR:Administrators NA Access Group for Application
developers

AOM 01.08.01AOM:API VFUK.VADR
AOM:API VFUK.TIL
AOM:Mailjet api@mailjet.com
AOM:RulesAdmins NA Access Group for Application
developers

AOMFW 01.08.01AOMFW:Tealium VFUK.Tealium
AOMFW:AssistedAgents VFUK.Assisted.Agent
AOMFW:Administrators NA Access Group for Application
developers
AOMFW:MarketManager NA Access Group for Logic
developers
AOMFW:PegaMarketManager NA Access Group for Logic
developers
AOMFW:MSUnauthenticated NA Access Group for microsite user
AOMFW:Simulation NA This is for simualtion users to run
simulation on previous code base
PegaNBAM:Agents NA Access Group for OOTB agentsApplication Version Access Group Operator Notes


4052
01.10.01

VADR 01.10.01VADR:AssistedAgents.Beta NA Access Group for Call Centre
agents
VADR:Administrators.Beta NA Access Group for Application
developersApplication Version Access Group Operator Notes


4053
R4.3

List of Application versions as part of the R4.03 release

01.09.01

 01.09.01 R4.03Application Versions Features/Releases

VADR 01.09.01VADR:AssistedAgents NA Access Group for Call Centre
agents
VADR:Administrators NA Access Group for Application
developers

AOM 01.09.01AOM:API VFUK.VADR
AOM:API VFUK.TIL
AOM:Mailjet api@mailjet.com
AOM:RulesAdmins NA Access Group for Application
developers

AOMFW 01.09.01AOMFW:Tealium VFUK.Tealium
AOMFW:AssistedAgents VFUK.Assisted.Agent
AOMFW:Administrators NA Access Group for Application
developers
AOMFW:MarketManager NA Access Group for Logic
developers
AOMFW:PegaMarketManager NA Access Group for Logic
developers
AOMFW:MSUnauthenticated NA Access Group for microsite user
AOMFW:Simulation NA This is for simulation users to run
simulation on previous code base
PegaNBAM:Agents NA Access Group for OOTB agentsApplication Version Access Group Operator Notes


4054
R4.4
List of Application versions as part of R4.4 release

01.11.0101.11.01 (v11) R4.04 Core
01.12.01 (v12) Feature - Upgrades backlog (FUT)
01.15.01 (v15) RetailApplication Versions Features/Releases

VADR 01.11.01VADR:AssistedAgents NA Access Group for Call Centre
agents
VADR:Administrators NA Access Group for Application
developers
VADR:API VADR.PMT Access Group for Pmtool API user

AOM 01.11.01AOM:API VFUK.VADR
AOM:API VFUK.TIL
AOM:Mailjet api@mailjet.com
AOM:RulesAdmins NA Access Group for Application
developers

AOMFW 01.11.01AOMFW:Tealium VFUK.Tealium
AOMFW:AssistedAgents VFUK.Assisted.Agent
AOMFW:Administrators NA Access Group for Application
developers
AOMFW:MarketManager NA Access Group for Logic
developers
AOMFW:PegaMarketManager NA Access Group for Logic
developers
AOMFW:MSUnauthenticated NA Access Group for microsite user
AOMFW:Simulation NA This is for simulation users to run
simulation on previous code
base(V9)
PegaNBAM:Agents NA Access Group for OOTB agentsApplication Version Access Group Operator Notes


4055

01.12.01

01.15.01
VADR 01.12.01VADR:AssistedAgents.Alpha NA Alpha Access Group for Call
Centre agents
VADR:Administrators.Alpha NA Alpha Access Group for
Application developers
VADR:API.Alpha VADR.PMT.Alpha Alpha Access Group for Pmtool
API user

AOM 01.12.01AOM:API.Alpha VFUK.VADR.Alpha
AOM:API.Alpha VFUK.TIL.Alpha
AOM:Mailjet.Alpha api.alpha@mailjet.com
AOM:RulesAdmins.Alpha NA Alpha Access Group for
Application developers

AOMFW 01.12.01AOMFW:Tealium.Alpha VFUK.Tealium.Alpha
AOMFW:AssistedAgents.Alpha VFUK.Assisted.Agent.Alpha
AOMFW:Administrators.Alpha NA Alpha Access Group for
Application developers
AOMFW:MarketManager.Alpha NA Alpha Access Group for Logic
developers
AOMFW:PegaMarketManager.Al
phaNA Alpha Access Group for Logic
developersApplication Version Access Group Operator Notes

VADR 01.15.01VADR:AssistedAgents.Charle NA Charle Access Group for Call
Centre agents
VADR:Administrators.Charle NA Charle Access Group for
Application developers
VADR:API.Charlie VADR.PMT.Charlie Charlie Access Group for Pmtool
API user

AOM 01.15.01AOM:API.Charle VFUK.VADR.Charle
AOM:API.Charle VFUK.TIL.Charle
AOM:Mailjet.Charle api.charlie@mailjet.com  Application Version Access Group Operator Notes


4056
AOM:RulesAdmins.Charle NA Charle Access Group for
Application developers

AOMFW 01.15.01AOMFW:Tealium.Charle VFUK.Tealium.Charle
AOMFW:AssistedAgents.Charle VFUK.Assisted.Agent.Charle
AOMFW:Administrators.Charle NA Charle Access Group for
Application developers
AOMFW:MarketManager.CharleNA Charle Access Group for Logic
developers
AOMFW:PegaMarketManager.C
harleNA Charle Access Group for Logic
developers


4057
R4.5
List of Application versions as part of R4.5 release

01.13.01
 01.13.01 (v13) R4.05 Core
01.15.01 (v15) RetailApplication Versions Features/Releases

VADR 01.13.01VADR:AssistedAgents NA Access Group for Call Centre
agents
VADR:Administrators NA Access Group for Application
developers
VADR:API VADR.PMT Access Group for Pmtool API user

AOM 01.13.01AOM:API VFUK.VADR
AOM:API VFUK.TIL
AOM:Mailjet api@mailjet.com
AOM:RulesAdmins NA Access Group for Application
developers

AOMFW 01.13.01AOMFW:Tealium VFUK.Tealium
AOMFW:AssistedAgents VFUK.Assisted.Agent
AOMFW:Administrators NA Access Group for Application
developers
AOMFW:MarketManager NA Access Group for Logic
developers
AOMFW:PegaMarketManager NA Access Group for Logic
developers
AOMFW:MSUnauthenticated NA Access Group for microsite user
AOMFW:Simulation NA This is for simulation users to run
simulation on previous code
base(V11)
PegaNBAM:Agents NA Access Group for OOTB agentsApplication Version Access Group Operator Notes


4058

01.15.01

VADR 01.15.01VADR:AssistedAgents.Charle NA Charle Access Group for Call
Centre agents
VADR:Administrators.Charle NA Charle Access Group for
Application developers
VADR:API.Charlie VADR.PMT.Charlie Charlie Access Group for Pmtool
API user

AOM 01.15.01AOM:API.Charle VFUK.VADR.Charle
AOM:API.Charle VFUK.TIL.Charle
AOM:Mailjet.Charle api.charlie@mailjet.com
AOM:RulesAdmins.Charle NA Charle Access Group for
Application developers

AOMFW 01.15.01AOMFW:Tealium.Charle VFUK.Tealium.Charle
AOMFW:AssistedAgents.Charle VFUK.Assisted.Agent.Charle
AOMFW:Administrators.Charle NA Charle Access Group for
Application developers
AOMFW:MarketManager.CharleNA Charle Access Group for Logic
developers
AOMFW:PegaMarketManager.C
harleNA Charle Access Group for Logic
developersApplication Version Access Group Operator Notes


4059
R4.6
List of Application versions as part of R4.6 release

01.16.01

 01.16.01 (v16) R4.06 CoreApplication Versions Features/Releases

VADR 01.16.01VADR:AssistedAgents NA Access Group for Call Centre
agents
VADR:Administrators NA Access Group for Application
developers
VADR:API VADR.PMT Access Group for Pmtool API user

AOM 01.16.01AOM:API VFUK.VADR
AOM:API VFUK.TIL
AOM:Mailjet api@mailjet.com
AOM:RulesAdmins NA Access Group for Application
developers

AOMFW 01.16.01AOMFW:Tealium VFUK.Tealium
AOMFW:AssistedAgents VFUK.Assisted.Agent
AOMFW:Administrators NA Access Group for Application
developers
AOMFW:MarketManager NA Access Group for Logic
developers
AOMFW:PegaMarketManager NA Access Group for Logic
developers
AOMFW:MSUnauthenticated NA Access Group for microsite user
AOMFW:Simulation NA This is for simulation users to run
simulation on previous code
base(V13)
PegaNBAM:Agents NA Access Group for OOTB agentsApplication Version Access Group Operator Notes


4060
AOMFW
[ AOMFW : 01-01-01  ] [ AOMFW : 01-02-01  ] [ AOMFW : 01-03-01  ]
 Ruleset Name Ruleset Version
AOMFW-Local 01-01-01
AOMFW-Artifacts 01-01-24
AOMFW 01-01-16
AOMFW-Int 01-01-01
AOMFW-Testing 01-01-01
AOMFW-PM-Artifacts 01-01-01
AOMFW-PM-Campaigns 01-01-02
AOMFW-PM-Catalogue 01-01-01
AOMFW-BuildArtifacts 01-01-01
AOMFW-UI 01-01-06
VFUK 01-01-01
VFUKInt 01-01-01
AOMFW-Database 01-01-01AOMFW : 01-01-01
Ruleset Name Ruleset Version
AOMFW-Local 01-02-01
AOMFW-Artifacts 01-02-56
AOMFW-Database 01-02-09
AOMFW 01-02-19
AOMFW-Int 01-02-10
AOMFW-Analysis 01-02-02
AOMFW-Testing 01-02-01
AOMFW-Test-Cases 01-02-07
AOMFW-PM-Artifacts 01-02-03
AOMFW-PM-Campaigns 01-01-02AOMFW : 01-02-01


4061

 AOMFW-PM-Catalogue 01-01-01
AOMFW-BuildArtifacts 01-01-01
AOMFW-UI 01-02-04
VFUK 01-01-01
VFUKInt 01-01-01
Ruleset Name Ruleset Version
AOMFW-Local 01-03-01
AOMFW-Business-Artifacts 01-03-90
AOMFW-Artifacts 01-03-24
AOMFW-Database 01-03-23
AOMFW 01-03-26
AOMFW-Int 01-03-20
AOMFW-Analysis 01-03-01
AOMFW-Testing 01-03-02
AOMFW-Test-Cases 01-03-13
AOMFW-PM-Artifacts 01-03-01
AOMFW-PM-Campaigns 01-01-02
AOMFW-PM-Catalogue 01-01-01
AOMFW-BuildArtifacts 01-01-01
AOMFW-UI 01-03-09
AOMFW-Simulation 01-01-01
VFUK 01-01-01
VFUKInt 01-01-01AOMFW : 01-03-01


4062
Creating a new AOMFW Application Version
[ Rulesets  ] [ Application  ] [ Custom Access Groups  ] [ OOTB Access Groups  ] [ Unauthenticated access group  ] [ Operators  ] [ Agents  ] [
Job Schedulers  ] [ System Runtime Context  ] [ Requestors  ]

Below are the changes required to be performed when a new application version is created.
Rulesets
Create new ruleset versions for all the applicable rulesets

Application
Update the AOMFW application rule by incrementing the Minor Version as in the screenshot below and save into the applicable ruleset.Ruleset Name Existing Ruleset Version New Ruleset Version
AOMFW-Local 01-03-01 01-04-01
AOMFW-Business-Artifacts 01-03-90 01-04-01
AOMFW-Artifacts 01-03-24 01-04-01
AOMFW-Database 01-03-23 01-04-01
AOMFW 01-03-26 01-04-01
AOMFW-Int 01-03-20 01-04-01
AOMFW-Analysis 01-03-01 01-04-01
AOMFW-Testing 01-03-02 01-04-01
AOMFW-Test-Cases 01-03-13 01-04-01
AOMFW-PM-Artifacts 01-03-01 01-04-01
AOMFW-UI 01-03-09 01-04-01
AOMFW-Simulation 01-01-01
VFUK 01-01-01
VFUKInt 01-01-01


VFUK 01-01-01
VFUKInt 01-01-01
AOMFW-PM-Campaigns 01-01-02
AOMFW-PM-Catalogue 01-01-01
AOMFW-BuildArtifacts 01-01-01  AOMFW : 01-03-01


4063
Custom Access Groups
From the records explorer, Click on the Access Group Under Security  ( Security → Access Group)
On the Access Group Rule, update the application version as shown below and save the application rule


4064

Update all the below access groups to point to the new application version ( AOMFW: 01-04-01)
OOTB Access Groups
Unauthenticated access group
Operators

AOMFW:Administrators AOMFW:MarketAdmins AOMFW:Managers
AOMFW:AssistedAgents AOMFW:MarketAnalysts AOMFW:PegaMarketAdmins
AOMFW:Authors AOMFW:MarketingArchitects AOMFW:PegaMarketManager
AOMFW:CVMManager AOMFW:MarketingDeveloper AOMFW:Simulation
AOMFW:CVMOperations AOMFW:MarketingOperations AOMFW:Tealium
AOMFW:HealthCheck AOMFW:MarketInstall AOMFW:Upgrade
AOMFW:Users AOMFW:MarketManager
AOMFW:MSUnauthenticated AOMFW:Microsites  Access Group Name
PegaNBAM:Agents PegaMKT:Unauthenticated  Access Group Name
AOMFW:MSUnauthenticated  Miscrosite is driven by Microsite operator which is now pointing to
this access group and we cannot have multiple operators for each
application version. We need to update the application version to test
the appropriate application.Access Group Name
VFUK.VADR  This is for VADR application to invoke AOM API’s
VFUK.TIL This is for TIL system to invoke AOM API’s
VFUK.Tealium This is for Tealium eventsOperators


4065
Agents
Please verify, if the Agents created on the below ruleset are mapped to updated access groups. Please check on the security tab of the
Agent and Agent Schedule rule
Job Schedulers
Please verify, if all the job schedulers under AOMFW and AOMFW-Local rulesets are pointing to  updated access groups pointing to the
latest application rule
System Runtime Context
Please verify, if the system runtime is pointing to the latest application rule.
Below is the navigation screenshot to System Runtime Context from the Pega Designer Studio (Configure → System → General →
System Runtime Context)

The application version should be AOMFW:01-04-01 as highlighted below in the System Runtime Context tabPegaMKT-Engine Pega Marketing OOTB Agents
AOMFW-Artifacts ProcessBatchJob OOTB Agent
AOMFW ResumeCaseFlow and  GenerateExtract Custom AgentsRuleset Name Description


4066

Requestors
Below navigation to the System Name from the Pega Designer Studio ((Configure → System → Settings → System Name)


4067
Pickup the Current Name from the screenshot below.
Below is the Navigation to the Requestors Types and their access groups ( (Configure → System → General → Requestors)
Please verify, if the below requestors matching the System Name picked-un in the previous step ( AOM-Dev1) below are mapped to the
updated AOMFW access groups which are mapped to the latest application version rule


4069
AOM
[ AOM : 01-01-01  ] [ AOM : 01-02-01  ] [  AOM : 01-03-01  ]

 Ruleset Name Ruleset Version
AOM-Artifacts 01-01-01
AOM-Rules 01-01-01
AOM-Int 01-01-06
AOM 01-01-01
AOM-Testing 01-01-01AOM : 01-01-01
Ruleset Name Ruleset Version
AOM-Local 01-02-01
AOM 01-02-01
AOM-Int 01-02-06
AOM-Rules 01-02-01
AOM-Artifacts 01-01-01
AOM-Testing 01-02-01
AOM-Test-Cases 01-02-02AOM : 01-02-01
Ruleset Name Ruleset Version
AOM-Local 01-03-01
AOM 01-03-01
AOM-Int 01-03-17
AOM-Rules 01-03-01
AOM-Artifacts 01-01-01
AOM-Testing 01-03-01
AOM-Test-Cases 01-03-06 AOM : 01-03-01


4071
Create a new AOM Application Version
[ Rulesets  ] [ Application  ] [ Custom Access Groups  ] [ Operators  ] [ Agents  ] [ Job Schedulers  ] [ System Runtime Context  ] [ Requestors  ]

Below are the changes required to be performed when a new application version is created.
Rulesets
Create new ruleset versions for all the applicable rulesets

Application
Update the AOM application rule by incrementing the Minor Version as in the screenshot below and save it into the applicable ruleset( AOM
in this case)
 Ruleset Name Existing Ruleset Version New Ruleset Version
AOM-Local 01-03-01 01-04-01
AOM 01-03-01 01-04-01
AOM-Int 01-03-17 01-04-01
AOM-Rules 01-03-01 01-04-01
AOM-Artifacts 01-01-01 01-04-01
AOM-Testing 01-03-01 01-04-01
AOM-Test-Cases 01-03-06 01-04-01AOMFW : 01-03-01


4072
Custom Access Groups
From the records explorer, Click on the Access Group Under Security  ( Security → Access Group)
On the Access Group Rule, update the application version as shown below and save the application rule

Update all the below access groups to point to the new application version ( AOMFW: 01-04-01)
AOM:Unauthenticated AOM:MarketInstall
AOM:RulesAdminsV2 AOM:MarketAnalystsAccess Group Name


4073
Operators
Please verify, if the below API operators are mapped to updated access groups
Agents
Please verify, if the Agents created on the below ruleset are mapped to updated access groups. Please check on the security tab of the
Agent and Agent Schedule rule.
Job Schedulers
Not Applicable
System Runtime Context
Not Applicable
Requestors
Not Applicable

 AOM:RulesAdmins AOM:MarketAdmins
AOM:MarketManagers AOM:Mailjet
AOM:MarketManager AOM:APIv2
 AOM:API
VFUK.VADR VFUK Layer API User
VFUK.TIL VFUK Tibco Integration Layer API User
VFUK.TIL.v2 VFUK Tibco Integration Layer API User ( ***Can be Deleted)
api@mailjet.com Mailjet API UserOperataror Name Description
AOM-Artifacts ProcessBatchJob OOTB AgentRuleset Name Description


4074
Artefacts to deploy to switch any application version to Live
All the below Access Groups points to latest application version. (Need discussion on the following access groups to finalise)
AOMFW Access Groups
AOM Access groups
VADR Access Groups
Access Groups included in the Live Package
Below is the list of Access groups which are included in the package to make a specific version LIVEAOMFW:AssistedAgents AOMFW:MarketAnalysts AOMFW:PegaMarketAdmins
AOMFW:Authors AOMFW:MarketingArchitects AOMFW:PegaMarketManager
AOMFW:CVMManager AOMFW:MarketingDeveloper AOMFW:SimAdmin
AOMFW:CVMOperations AOMFW:MarketingOperations AOMFW:Simulation
AOMFW:HealthCheck AOMFW:MarketInstall AOMFW:Tealium
AOMFW:Users AOMFW:MarketManager AOMFW:Upgrade
AOMFW:Unauthenticated AOMFW:MarketManagers AOMFW:Managers
PegaNBAM:Agents   AOMFW:Administrators AOMFW:MarketAdmins AOMFW:Microsites
AOM:RulesAdmins AOM:MarketAnalysts AOM:MarketManagers
AOM:MarketManager AOM:MarketAdmins AOM:Mailjet
AOM:APIv2 AOM:API  AOM:Unauthenticated AOM:MarketInstall AOM:RulesAdminsV2
VADR:AssistedAgents VADR:Administrators VADR:Operations
AOM:RulesAdmins AOM
AOM:API AOM
AOMFW:Administrators AOMFW
AOMFW:MarketAdmins AOMFW
AOMFW:PegaMarketManager AOMFW
AOMFW:Unauthenticated AOMFW


AOMFW:PegaMarketManager AOMFW
AOMFW:Unauthenticated AOMFW
AOMFW:Tealium AOMFWAccess Group Application


4075

Update Connect-REST rules changed as part of specific application version with live authentication profile.
Datapages changed as part of specific application version need to change with live access groups.
Job schedulers changed as part of specific application version need to change with live access groups.
Note: Revert set of operators who tested specific application to live access group to test Live application.AOM:Mailjet AOMFW
AOMFW:Simulation AOMFW
AOMFW:AssistedAgents AOMFW
PegaNBAM:Agents AOMFW


4076
914098: Designing the process to support feature-based releases
Steps to create a new application version for Charlie
Rules Created for Charlie application version
Charlie(MBB) application
Charlie(MBB) application Test Result
Live application
Live application Test Result
Make Charlie as Live application
Make Charlie as Live application Test Result
Outcome
Limitations
Manual tasks
For Charlie application
For making Charlie as Live application
VADR Journey for Charlie application
VADR Journey after making Charlie as Live application
Steps to create a new application version for Charlie
Create new Application version for AOMFW, AOM and VADR applications. (In this POC, the new application version is for Charlie
release with MBB features)
Create Access Groups for new application versions as shown below
Add new access groups to some of the rules like Job Scheduler, Data page which we change in new release.
Create new minor ruleset versions in all new application versions.
Merge new feature(MBB) branch into new minor ruleset version created as part of new application versions.01.03.01 01.03.01 01.01.01 Live For App:
AOMFW:Adminis
trators
For Logic:
AOMFW:Market
Manager
AOMFW:PegaMa
rketManagerAOM:RulesAdmi
nsVADR:AssistedA
gents
01.04.01 01.04.01 01.04.01 Charlie For App:
AOMFW:Adminis
trators.Charlie
For Logic:
AOMFW:Market
Manager.Charlie
AOMFW:PegaMa
rketManager.Cha
rlieAOM:RulesAdmi
ns.CharlieVADR:AssistedA
gents.CharlieAOMFW
Application
versionAOM
Application
versionVADR
Application


Application
versionAOM
Application
versionVADR
Application
versionRelease AOMFW Access
GroupsAOM Access
GroupsVADR Access
Groups