PeopleTools Wish List
From TekiWiki
This whole wiki has now moved to http://www.springboardsolutions.com/wiki
Go to this page PeopleTools Wish List
(→PeopleSoft - The Module) |
(→Cost of Ownership Improvements) |
||
| Line 8: | Line 8: | ||
This would decrease the perceived risk of adopting Fusion for PeopleSoft customers and therefore increase the take up of Fusion, making it a strong powerful product with key differentiators from the competition. In turn, PeopleSoft customers have a reduced resistance to other Fusion modules such as Taleo/Recruit. | This would decrease the perceived risk of adopting Fusion for PeopleSoft customers and therefore increase the take up of Fusion, making it a strong powerful product with key differentiators from the competition. In turn, PeopleSoft customers have a reduced resistance to other Fusion modules such as Taleo/Recruit. | ||
| - | ==Cost of Ownership | + | ==Improve Cost of Ownership== |
| - | One criticism that | + | PeopleSoft's key strength is that the application is easy to customise and enhance. Translation: PeopleSoft can support your business processes, now and in the future. In areas where processes and procedures need to adapt to best practices, legal requirements and the business changes happening in that sector. |
| + | |||
| + | One criticism that this amazing feature 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. | 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. | ||
