If you update from an earlier version, and your application uses the out-of-the-box access roles, your operators acquire the required privilege after the update.

1. Review your access groups to determine whether you use any of the access roles that have been updated to include the new privilege:

   Access role	Privilege
   PegaCRM:User4	crmCanSAUserRunActivity, crmCanCRMUserRunActivity
   PegaCRM-SFA:SysAdmin	crmCanSAUserRunActivity, crmCanCRMUserRunActivity
   PegaSFA-EmailServices	crmCanSAUserRunActivity, crmCanCRMUserRunActivity
   PegaCRMBase:Guest	crmCanGuestUserRunActivity

2. If an access group does not include an access role with the required privileges, ensure that your operators can access the rules that are required to run your application:

   • If you use out-of-the-box access roles, add the access role to the access group.

     For information, see Adding a role to an access group.

   • If you use custom access roles, modify the custom access role to include the privilege.

     For information, see Granting privileges to an access role.

1. Log in to Dev Studio as an administrator for your implementation layer.
2. In the navigation pane of Dev Studio, click Records TechnicalActivities.
3. Search for and open the CreateFieldValuesFromDataTable activity.
4. Edit this activity by entering the following values:
   1. In the FieldName field, enter TaskType.
   2. In the FVAppliesToClass field, enter PegaCRM-Work-Task.
   3. In the DataTableDP field, enter D_TaskCategories.
   4. In the PropertyToCompare field, enter Name.
5. Click Save.
6. Run the activity by clicking Actions Run.
7. Search for and open the CreateFieldValuesFromDataTable activity.
8. Edit this activity by entering the following values:
   1. In the FieldName field, enter LossReason.
   2. In the FVAppliesToClass field, enter PegaCRM-.
   3. In the DataTableDP field, enter D_ManageLossReasons.
   4. In the PropertyToCompare field, enter Name.
9. Click Save.
10. Run the activity by clicking Actions Run.

1. Update access groups and application instances to reference the SalesAutomationForInsurance 08.40 application.
2. User defined functions (UDFs) are no longer supported for Cloud deployments. Existing objects and instances referencing UDFs in the 8.4 application will generate missing value errors for unexposed columns. If your customized application rules used properties that relied on UDFs, you must optimize the affected properties after the update by running the column population job to repopulate these properties. To obtain the list of the properties you must optimize after the update, review the DDL SQL file to find the altered database tables.
3. Unique ID prefixes might be altered during the update. Review the Unique ID prefixes to ensure that they are still appropriate for the environment.

   Unique ID prefix	Class reference
   BT	PegaCRM-Data-BusinessTerritory
   DF-	Pega-DM-DDF-Work
   HH-	PegaCRM-Entity-RelationshipGroup-Household PegaInsCRM-Work-RelationshipGroup-Household
   PR	PegaCRM-Data-Product
   RT-	PegaCRM-Data-RelationShipTypes
   TP-	PegaCRM-Data-TimePeriod

1. If you will use Attribute Based Access Control (ABAC) security, complete the following tasks:
   1. Run the PopulateTerritoryForQuotes Quote activity to update all quotes with the appropriate territory.
      ABAC security requires control attributes to be maintained and exposed on each object in order to provide acceptable performance. Quotes require the appropriate TerritoryID assigned to each instance.
   2. Run the PopulateTerritoryAccInsNameForPolicies activity to apply the appropriate territory for each policy.
      ABAC security requires control attributes to be maintained and exposed on each object to provide acceptable performance. Internal and external policies require the appropriate TerritoryID assigned to each instance.
2. If your application used a custom version of an activity that was deprecated in version 7.4, refactor the activity.

   The following table describes deprecated activities, and the refactoring information for each.

   pyclassname	Activity Rulename	Update	Alternate Rule Name
   Code-Pega-List	BusinessPolicyByProductOrProductGroup	D_ShowPoliciesByProduct DataPage Activity replaced by Report Definition and Data Transform rules	Report Definition: PolicyByAccountAndProducts Data Transform: ShowPoliciesByProduct
   Code-Pega-List	IndvPolicyByProductOrProductGroup	D_ShowPoliciesByProduct DataPage Activity replaced by Report Definition and Data Transform rules	Report Definition: PolicyByContactAndProducts Data Transform: ShowPoliciesByProduct
   Code-Pega-List	GetClaimsDetailsByID	D_PolicyClaims DataPage Activity replaced by Report Definition and Data Transform rules	Data Transform: GetClaims
   Code-Pega-List	LoadAllPolicies	This activity in D_ShowPolicies DataPage replaced by Report Definition	Report Definition: FetchPolicies
   Data-	GetCase	D_OperatorLookup Datapage and related activity, GetCase withdrawn due to non-use.
   PegaCRM-Data-Product	FetchProductByID	D_ProductByProductId Datapage updated to use Lookup method, so activity withdrawn	Lookup for Product Class - same parameter used for activity is used to do the lookup.
   PegaCRM-Data-Product	FetchProductByName	D_ProductByProductName DataPage updated to use Data Transform rule and activity withdrawn	Data Transform: FetchProductByName
   PegaCRM-Portal	GetSearchResults	Activity withdrawn due to non-use
   PegaInsCRM-Data-CustSearch	GetObjCount	The FlowAction activity was replaced with Data Transform GetObjCount.	Data Transform: GetObjCount Data Page: D_GetQuotesByContactID Rpt Definition: GetQuotesByContactId Leverages crmRelatedTasksForContact / crmRelatedTasksForContact
   PegaInsCRM-Data-ManageLossReasons	GetLossReasons	Activity withdrawn due to non-use
   PegaInsCRM-Data-ManageTaskCategories	GetTaskCategories	The Section SFAPortal_Tools_Content has a Task categories Button that ran GetTaskCategories activity for the Harness action. The secion rule has been updated and no longer run an activity. The section, ManageTaskCategories, which had a grid layout with pxResults has been updated with D_ManageTaskCategories DataPage as a source.	Section Updated: ManageTaskCategories DataPage: D_ManageTaskCategories
   PegaInsCRM-Work-	DetermineSourceSystem	Activity ran Decision Table, DetermineSourceSystem. Activities that referenced this activity were udpated to reference DT directly.	Activities updated to use DT instead of calling activity: PegaInsCRM-Work-Policy crmBulkPostMerge (withdrawn) PegaInsCRM-Work-SFA-Quote crmBulkPostMerge (withdrawn) If these activities have been customized, they may need to be refactored to call DT: PegaInsCRM-Work-Policy crmPreProcessRecord PegaInsCRM-Work-SFA-Quote crmPreProcessRecord
   PegaInsCRM-Work-	PercentageOfTop5SalesPriorities	Was used in DataPage, D_PercentageOfTop5SalesPriorities	Data Page D_PercentageOfTop5SalesPriorities updated to use Data Transform PercentageOfTop5SalesPriorities
   PegaInsCRM-Work-Policy	DetermineProductId	Activity ran Decision Table DetermineProductId. Activity GetPolicyDetailsByID was udpated to apply Data Transform DetermineProductId	Data Transform: DetermineProductId
   PegaInsCRM-Work-SFA-Opportunity	AddFeedbacktoPulse	This wrapper activity was withdrawn. FlowAction GetFeedback was updated to call pxPostMessage activity directly.	N/A
   PegaInsCRM-Work-SFA-Quote	DetermineProductId	Updated "GetQuoteDetails" activity to call decision table	Data Transform: DetermineProductId
   PegaInsCRM-Work-Task	GetWorkObjectsRelatedToTask	Updated Datapage D_WorkObjectsRelatedToTask to use Report Definitions.	Activity withdrawn and GetWorkObjectsRelatedToTask RD's created in account, contact, org, lead, opportunity classes

3. If your application used a custom version of a quote section that was deprecated in version 7.4, convert to a new section.

   Two quote sections are deprecated and two new sections are added. The new sections conform to the Sales Automation for Insurance naming conventions. The sections are invoked when adding, reviewing, and editing an internal or external quote. Deprecated sections will be removed in a future release.

   The following tables shows the quote section changes from version 7.31 to version 7.4. An asterisk (*) denotes a value that is circumstanced for Internal/External quotes.

   Structure - Harness New

   UI Form	7.31	7.4
   Harness	New	New
   Section	pyNewWorkSummary	pyNewWorkSummary
   Section	WorkSummary*	CaptureWorkPrimaryDetails*
   Section	AddInternalQuote / AddExternalQuote
   Section	AddInternalQuote_ToWrap / AddExternalQuote_ToWrap

   Structure - Harness: Perform

   UI Form	7.31	7.4
   FlowAction	crmEdit	crmEdit
   Section	pyNewWorkSummary	pyNewWorkSummary
   Section	WorkSummary*	CaptureWorkPrimaryDetails*
   Section	AddInternalQuote / AddExternalQuote
   Section	AddInternalQuote_ToWrap / AddExternalQuote_ToWrap

   Structure - Harness: Review

   UI Form	7.31	7.4
   Harness	Review	New
   Section	pyCaseMain
   Section	pyWorkBody
   Section	pyWorkBodyLeft
   Section	pyWorkDetails	pyWorkDetails
   Section	WorkSummary*	workPrimaryDetails*
   Section	AddInternalQuote
   Section	AddInternalQuote_ToWrap