PeopleTools Wish List
From TekiWiki
This whole wiki has now moved to http://www.springboardsolutions.com/wiki
Go to this page PeopleTools Wish List
(→3: Reducing Clashes Between Vanilla and Custom Code) |
(→3: Reducing Clashes Between Vanilla and Custom Code) |
||
| Line 36: | Line 36: | ||
Although it would not prevent all possible clashes, if there was a custom event after (or before or both) each vanilla event, many clashes in the code could be avoided, saving a lot of time. | Although it would not prevent all possible clashes, if there was a custom event after (or before or both) each vanilla event, many clashes in the code could be avoided, saving a lot of time. | ||
| - | Also, if each vanilla class could have a shadow custom class that could extend it without changing its name, this also would allow enormous flexibility without the upgrade penalty. | + | Also, if each vanilla class could have a shadow custom class that could extend it without changing its name, this also would allow enormous flexibility without the upgrade penalty. Private functions and properties would also need to be available to the shadow class. |
| + | As more PeopleSoft functionality is based on classes, this would enable more places for the system to be extended. | ||
==Other PeopleSoft Enhancements== | ==Other PeopleSoft Enhancements== | ||
