1. In the navigation pane of App Studio, click SettingsApplication Settings.
2. On the Features tab, select the Artificial intelligence insights - opportunity insights, lead ranking, and sales coach check box to see all of the AI capabilities.
3. Enable any of the listed AI capabilities by selecting the individual check box.
4. Click Save.
5. Switch to Dev Studio.
6. In the navigation pane of Dev Studio, click RecordsSysAdminAgent Schedule.
7. Search for an open the SA-Artifacts agent schedule.
8. On the Edit Agent Schedule page, select the Enable this agent check box.
9. Click Save.

1. In the header of Dev Studio, click ConfigureDecisioningInfrastructureServices.
2. Verify that each of the following services on the list contains a node with a status of Normal:
   • Decision Data Store
   • Adaptive Decision Manager
   • Data Flow
   • Visual Business Director

1. In the header of Dev Studio, click ConfigureApplicationDistributionImport.
2. Click Choose File, browse for and select the HistoricalData file from your distribution media, and then follow the wizard instructions.

   Pega-provided historical data consists of a snapshot of data from a production environment for various models.

1. In the navigation pane of Dev Studio, click RecordsData ModelData Set.
2. Search for and open the pxDecisionResults data set of the Data-Decision-Results class.
3. Click ActionsRun.
4. In the Operation field, select Truncate.
5. Click Run.
6. Repeat steps 2 to 5 for the PreviousStages data set of the SA-SR class.

1. In the header of Dev Studio, cllick ConfigureDecisioningModel Management.
2. Select all of the models listed below:
   • PredictWin
   • PredictMoveNextStage
   • PredictCloseDate
   • BaseWinModel
   • LeadRanking
   • PredictEffectiveness
3. Click Delete Models.

Note: Before performing the steps below, make sure that you have the EnableOpportunityInsights dynamic system setting set to true.

1. In the navigation pane of Dev Studio, click RecordsData ModelData Flow.
2. Search for and open the StoreOpportunitySnapshots data flow.
3. Click ActionsRun.
4. After you see the confirmation message with a successful result, repeat steps 2 and 3 for the TrainFromHistory data flow.

Note: Before performing the steps below, make sure that you have the EnableSalesCoach dynamic system setting set to true.

1. In the navigation pane of Dev Studio, click RecordsData ModelData Flow.
2. Search for and open the StoreSalesRepSnapshots data flow.
3. Click ActionsRun.
4. After you see the confirmation message with a successful result, repeat steps 2 and 3 for the CaptureEffectivenessOutcomes data flow.

1. In the navigation pane of Dev Studio, click RecordsData ModelData Flow.
2. Search for and open the StoreLeadSnapshots data flow.
3. Click ActionsRun.
4. Repeat steps 2 and 3 for the CaptureLeadOutcomes data flow.
5. Optional: To set up predictors and calculate lead score for already existing leads and store them in the lead predictor table, run the InitialiseLeadPredictorTable activity.

1. In the navigation pane of Dev Studio, click RecordsData ModelData Flow.
2. Search for and open the StoreIndividualLeadSnapshots data flow.
3. Click ActionsRun.
4. Repeat steps 2 and 3 for the CaptureIndividualLeadOutcomes data flow.
5. Optional: To set up predictors and calculate lead score for already existing leads and store them in the lead predictor table, run the InitialiseLeadPredictorTable activity.

1. In the navigation pane of Dev Studio, click RecordsSysAdminDynamic System Settings.
2. Search for and open the usePreloadedNBA dynamic system setting.
3. In the Value field, set the value true.
4. In the navigation pane of Dev Studio, click RecordsSysAdminJob Scheduler.
5. Search for and open the GenerateNBA job scheduler.
6. Turn on the Enable Job Scheduler switch.
   Tip: To see the job scheduler changes instantly, run the LoadNBAForAllOpps data flow.
7. Optional: If your implementation layer has additional next best actions, add them by overriding the LoadNBAForAllOpps_Ext data flow. Then, create declare triggers to track work item updates.