v7.x Upgrade Documention needs to be changed
Pega version 7.x upgrade documentation is the wrong place to be discussing the benefits of split schemas. All upgrade documentation should simply read, If you have single schema follow path A, If you have dual schema follow path B.
Moving to split schema should be a separate enhancement and has nothing to do with the update/migration you are trying to preform. In fact it just adds in a confusion factor . Pega own docs contradicted itself.
Planning your upgrade
The Pega 7 Platform supports several configuration options that can affect the choices that you make during the upgrade. Before beginning, read this section thoroughly.
l Do not change your environment during an upgrade. For example, if you are making changes to your application server, or database server, do so before you upgrade the Pega 7 Platform.
lChoose a configuration type: single-schema or split-schema system. Pegasystems recommends a split-schema system. See Split-schema and single-schema systems.
Regards,
John Maruscak
John,
Thank you for your post reporting the Deployment (Upgrade) Guides usability issue.
For the benefit of all community participants, here is how to submit product documentation bugs and feedback:
(For your current issue, simply link to this community post.)
Your Feedback submission is tracked in the Pega-internal Agile Studio application.
The product documentation owner or other Pega SME will close the loop with you (and post reply here, we expect).
Reference:https://pdn.pega.com/community/product-support/question/how-report-pdn-issues and its Comment thread
Find this reference document on the Product Support Community home page under Important PSC Information.
-Mary