Posts Tagged ‘peopletools’
PeopleTools 8.52, starting to look like Fusion Applications
The Release Value Proposition for PeopleTools 8.52 has been posted on metalink.
This realese of PeopleTools introduces and extends current PeopleTools technology that look and behave more and more like Fusion Applications. With this version the transition or fusion of PeopleSoft customers to Fusion Applications will be more streamlined.
In this post I will highlight some of the new features of PeopleTools 8.52
Setting up predelivered Related Content services
With the release of PeopleTools 8.50, Related Content was introduced. Related Content Framework enables you to contextually link PeopleSoft pages to other PeopleSoft pages and non-PeopleSoft pages and view all related pages within one frame, without leaving the primary page.
- Related Discussion
- Related Links
- Related Tags
See following datasheet from Oracle describing the license use.
This post describes the steps that need to be taken to enables Portal Related Content Services in PeopleSoft Applications.
Release PeopleSoft 9.1 and PeopleTools 8.50: Effort to implement the Wow
As stated in an earlier blog post the new PeopleTools 8.50 really gives you a WOW.
And there are a lot of WOW’s. But do they come of the box or do you have to put a lot effort to get them available to the user when you are upgrading from an earlier version?
Here I’ll give an overview about what Oracle says about some of these, so you can get an idea.
Release Value Proposition for PeopleTools 8.51
After the long-awaited and quite revolutionarily PeopleTools 8.50, Oracle announced PeopleTools 8.51. With this release Oracle will enhance PeopleTools and add some new features that will be a great markup for PeopleSoft in general.
Here are some snippets from the RVP, which I think will have a great added value to the PeopleSoft application.

The advantages of the use of Application Package PeopleCode
Recently we had to make quite some customizations in Vanilla PeopleCode in the ePerformance module of HCM. In this case we decided to use an Application Package. We decided to put all our code for the modifications in a class. This worked out quite elegant.
We created a component object in the PostBuild PeopleCode of the Component.
Example:
import KP_EP_FUNCTIONS:BonusSheetCalc;
&oBonusSheetCalc = create KP_EP_FUNCTIONS:BonusSheetCalc(&sBonusStat);
In the private section we could put all the variables, which we would put normally as component variables. Example:
private
instance boolean &bBnsMtxChg;
instance boolean &bEditStat;
instance Rowset &rsBnsShtTgtDpt;
Then at every piece of PeopleCode where we need to use one of the methods, we only needed to put the declaration of the component object and all the defined methods and variables are then available:
Component object &oBonusSheetCalc;
&oBonusSheetCalc.SavePreChange(EP_APPR.PERIOD_BEGIN_DT, &PushButton);
There is a disadvantage though. If you are working in a project with several people, then only person can work on the Application Package at a time.