Appreciate if anyone has any thoughts before I attempt it. Over the years, I have noticed that CP Modules tend to get corrupted more than most (or the CP System develops problems). Some metrics on the CP modules showed thousands of objects and 100,000's of change history records have built up over time. The obvious thing is to baseline the Proposal Modules. Will the CP system survive baselining is the question? Thanks ADent - Wed Jun 14 01:38:35 EDT 2017 |
Re: Baselining A CP Module We always baseline CP modules with their parent module at release times within a baseline set - this will preserve links to the proper version of the main objects. Additionally we have a script to "cleanup" the CP modules that we run after the baseline, it deletes and purges ONLY APPLIED baselined CP objects - Note: do not delete the "CP author" heading objects or this will cause issues. With this method, CPs will remain in their current baseline preserving all change history. Additionally we have the benefit of easily seeing what changes applied to each release. This keeps all the information that you need and makes the CP module much more useable over time. We have been doing this nearly 20 years without issue. I strongly recommend verbosely commenting the baseline description so users understand what they are loading in the future. Sara |