Overview
As PeopleSoft consultant, many a
times we design and build Manager Self Service (MSS) components. MSS is
that part of the PeopleSoft HCM application, where a manager (someone who has
direct reports) can go and perform transactions for their Direct Reports. So in
all of our custom MSS components we need to have a solution in place to display
a list of direct reports of the manager. Upon selection of one/multiple Direct
Reports the manager is usually taken to the custom transaction component where they can perform the tasks for the selected Direct Report(s).
For the first part of the requirement
which is common across all MSS components, PeopleSoft delivers the
DirectReportsUI application class that encapsulates the Direct Reports
"Select Employees" User Interface pages into an easy to use class
that can be plugged into any new custom MSS component. Unfortunately instead of
using the DirectReportsUI application class many a times we end up
reinventing the wheel and design our own solution for displaying the list of
direct reports. Ease of use, standard look and feel, comprehensive configuration
options and integration with text catalog are some of the compelling reasons to
use the DirectReportsUI application class.
In part 2 of this blog we will
understand the steps involved in using the DirectReportsUI application
class for our custom MSS components. For this illustration we have kept the
requirement of the transaction component, where the manager will be transferred
on selecting a Direct Reports as very simple. In this case the
transaction component consists of only one page which displays current job data of
the Direct Report selected by the manager. The search record of the component
is PS_INSTALLATION as the component buffer will be populated using PeopleCode
written in the Component PostBuild event. We want to highlight how simple it is
to use the DirectReportsUI application class.
Contributed by Debasish
