We have an application in PRPC 6.3 SP 1 which we are planning to upgrade to PRPC 7.1.9,ie a full system release. The work table of the application is huge with almost 300000 records and a large number of open work items. If we are going in for a Out Of Place upgrade with split schema, the Pega DATA should contain all the migrated work objects, am I correct? What are the precautions that should be taken so that there is NO impact on existing cases.
Also is it better to use the Upgrade Assistant tool or going in by a manual approach? The Upgrade reference materials say both are equally effiicient. I have a personal preference of going in by the tool, is there a reason as to why the manual apprach might be preferred?
**Moderation Team has archived post**
This post has been archived for educational purposes. Contents and links will no longer be updated. If you have the same/similar question, please write a new post.
Upgrade process neither migrates nor manipulates any work related tables/data. There is no impact on existing cases hence you can safely utilitze the out-of-place split schema approach.
Reg command line vs IUA, for out-of-place split schema, migrating rules and data-only upgrade is possible only via command line. Command line utility also provides more options for skipping some optional steps
migratesystem.bat/sh must be used for the rules migration process. Please go through the upgrade guide and ensure you understand the entire sequence of steps and pre-requisites before triggering the upgrade