PeopleTools Wish List
From TekiWiki
This whole wiki has now moved to http://www.springboardsolutions.com/wiki
Go to this page PeopleTools Wish List
| Line 9: | Line 9: | ||
One criticism that PeopleSoft gets is the cost of an upgrade. Oracle have made in roads into reducing this with the PUM image releases. Now it is trivial to download and review the latest PeopleSoft code base. | One criticism that PeopleSoft gets is the cost of an upgrade. Oracle have made in roads into reducing this with the PUM image releases. Now it is trivial to download and review the latest PeopleSoft code base. | ||
| + | Decreasing the cost of keeping current means decreasing the impact of customisations. There is a body of development standards and techniques created by partners and customers to try to make customisations easy to spot and separate from the PeopleSoft vanilla code. Many of my ideas here are to embed these good practices into PeopleTools and almost make them mandatory. | ||
| + | 1: Naming conventions | ||
| + | Virtually every site I have been to utilises a naming convention of prefixes or suffixes to denote custom code. Often this is a 1-3 letter code (usually derived from the company name) followed by an underscore. Each customer has picked a different prefix and a mildly different way to get around the "awkward cases" where a prefix would cause an issue with functionality. | ||
| + | |||
| + | ==Other PeopleSoft Enhancements== | ||
Here is a list of fairly minor enhancements I would like to see in [[PeopleTools]] : | Here is a list of fairly minor enhancements I would like to see in [[PeopleTools]] : | ||
