PeopleTools Wish List
From TekiWiki
This whole wiki has now moved to http://www.springboardsolutions.com/wiki
Go to this page PeopleTools Wish List
(→Cost of Ownership Improvements) |
|||
| Line 18: | Line 18: | ||
2: Holding a Copy of Vanilla within the Database | 2: Holding a Copy of Vanilla within the Database | ||
| + | Vanilla PeopleSoft code held separately from any customisations. The vanilla code would remain untouched and custom code would be held separately, so an upgrade could confidently switch the old vanilla code with the new code, leaving the customisations in place. If all three (old vanilla, new vanilla and customisations) exist in the database at once, compares could be much faster and so less costly than at present. | ||
| + | Additionally, reverting to vanilla code would be very easy (if custom code could be switched on or off). | ||
| + | How could this be achieved? Add a key field to each PeopleTools table stating the release of that code. PeopleSoft releases would always have a set label format, allowing PeopleSoft to ensure the latest code is always in use. Customisations would be given a label that would override the vanilla code. There would also be a status field that allows custom code to be switched off. | ||
| + | This scheme could require a lot of changes to the PeopleTools code, so another option would be to hold the versions in copy tables of vanilla, and for Application Designer (and the PIA where applicable) maintains the copying to the resultant PeopleTools tables. | ||
==Other PeopleSoft Enhancements== | ==Other PeopleSoft Enhancements== | ||
