SA-22306

Summary

Upgrade from PRPC 6.2 SP1 to Pega 7.2 fails if 'Requestor Types' for 'prpc' is altered.

Error Messages

 [java] 2 related to applies-to class 'Pega-Landing-System-Upgrade', but were defined in rulesets which are not in your rulesetlist: {Pega-LP-SystemSettings:07-10-15, Pega-LP-SystemSettings:07-10-17}.
     [java] 
     [java] 
     [java] Current RulesetList:
     [...]<list of customer rulesets>[...]

Steps to Reproduce

Run PRPC_Setup.jar against an existing PRPC 6.2 SP1 system to upgrade to Pega 7.2.
Note: the issue only occurs if the 'Requestor Types' (DATA-ADMIN-REQUESTOR instances) ACCESS GROUPs have been modified for the System Name 'prpc'.

Root Cause

The 'Requestor Types' for the system name 'prpc' must be unaltered to avoid issues. 


A defect in Pegasystems’ code or rules : the upgrade process does not check the validity of these DATA-ADMIN-REQUESTOR instances before the Upgrade Process starts.

Resolution

Perform the following local-change: 

From an Out-of-the-box 6.2 SP1 system, export the 4 DATA-ADMIN-REQUESTOR instances for the system name 'prpc': and import them into the system which is to be upgraded.

It is necessary to perform this task using the export or import process to avoid the system vetoing any changes made from the Designer Studio.

Also see: Process Commander V6 help "About Requestor Type data instances" and "When and how to change a system name" for more background information about 
Requestor Types.