PeopleSoft Overview

PeopleSoft Overview
Program Agenda
• Technology Overview
• Navigating PeopleSoft Application
• Explaining PeopleSoft Architecture
• Understanding Effective Dating
• Validating Data
Technology Overview

Four Phases of Application Development
– PeopleSoft Application development is a four-phase process
Technology Overview

– PeopleSoft Application development is a four-phase process
• Planning Phase - In Planning phase we design the application
• Data Design Phase – In the data design phase we
– Create Fields
– Create Records
– Build Tables
• User Interface Phase – In the user interface phase we
– Create Pages
– Create Components
– Register Components
• Testing Phase – In the test phase we enter sample data and test navigation
and security
Technology Overview

– Planning Phase - Elements of the Planning Phase includes
• Fit-gap analysis
– When performing a fit-gap analysis determine the current capabilities
and compare them to the performance that you want. This is typically
done by functional users/consultants
• Design analysis
– In a design analysis you examine functional business requirements
and convert them into technical requirements
• Cost analysis
– When performing a cost analysis consider hardware, software, and
human capital cost
Technology Overview

– Planning Phase - Elements of the Planning Phase includes
• Resource Analysis
– In a resource analysis you determine the availability and number of resources
that are required
• Contingency Analysis
– Consists of planning for events that may cause your project to be extended
– Data Design Phase – In data design phase you
• Create field definitions
• Aggregate field definitions to create record definitions
• Build SQL tables
Technology Overview

– User Interface Phase – In this phase we begin building the user-facing
elements of the application
• Create Page Definitions
• Create Component Definitions
• Set Up User Navigation
• Set Up User Security
Technology Overview

– Testing Phase – In this phase we verify the data structures and and user
interface. In this phase we
• Verify Navigation
• Verify Security
• Enter and Verify data
Technology Overview

Describing PeopleSoft Application Designer
– In PeopleSoft we use Application Designer to complete most
development tasks
Technology Overview

Describing PeopleSoft Application Designer
– Development tasks that we do not perform in Application Designer
include :
• Creating Structured Query Report (SQR) programs
• Modifying COBOL programs
• Running PeopleSoft Data Mover Scripts
– How to find information about application designer in PeopleBooks
• Use the Enterprise PeopleTools 8.50 PeopleBook : Application Designer
Developer's Guide to find development information, including :
– Information for planning application development
– Information for creating data structures
– User Interface design and implementation
– Appendixes
Program Agenda
• Validating Data
Navigating PeopleSoft Application

Signing in to PeopleSoft Applications
– To sign in to a PeopleSoft Application we need three things
• A URL
• A Valid User Id
• A correct password for the User Id

Signing in to PeopleSoft Applications
– PeopleSoft Sign In Page

Homepage
– After user signs in, the homepage appears in the browser
– The Homepage contains three major areas
• The drop-down menu which displays a hierarchy of folders and content
references
• The header which contains quick access to navigational aids
• The target area, which displays content

PeopleSoft Navigation Elements
– PeopleSoft Applications are made up of a navigational structure,
components (groups of pages) and pages
– Two elements make up PeopleSoft Navigation
• Content References – is a link in the menu hierarchy that accesses a
component, which consists of one or more transaction pages
• Folders - Folders define the hierarchy of the navigation. Triangular icons
identify folders. Folders can contain other folders and content references.
Click the triangular icon or the folder name to expand the folder

PeopleSoft Navigation Options
– Drop-Down Navigation
• Intuitive way of updating or viewing data in your database. Drop-down navigation
consists of a hierarchy of cascading folders and content references

– Drop-Down Navigation
• When using drop-down navigation, you begin by clicking Main Menu. When you
click Main Menu, this causes the list of general areas to which you have access to
appear. Hover your mouse over any folder and you will see a cascading menu
open. You can continue to hover your mouse through each cascading menu until
you find the content reference that you want
• AJAX – PeopleSoft applications use Asynchronous Javascript and XML (AJAX).
Because of AJAX, as you hover over folders in the main menu, the system retrieves
only the appropriate hierarchy for the selected link or folder, instead of refreshing
the entire menu. When you hover over the folder image next to the folder name,
only specific folder contents are retrieved. When you click the folder link itself, then
the entire hierarchy of the root portal registry contents and the folder contents
themselves are retrieved and displayed.

– Navigation Page
• Navigation pages serve as alternatives to the menu.
• You click a folder to access the navigation page
• Elements embedded in the folder, including content references and other folders,
are arranged in a graphical format on the navigation page

– Bread Crumbs
• When you access a navigation page or a content reference, a set of bread crumbs
appear. The bread crumbs reveal the full navigation to the page
• Each folder within the bread crumbs is an active sub-menu. If you click the element
in the bed crumbs, the sub-menu appears
• As a result you do not have to navigate back to the main menu to access a sub-
menu or page that is included in the bread crumbs

– Menu Pagelet
• Pagelets are blocks of content on the homepage
• Pagelets display information within a small rectangular area on the page
• Click the Personalize Content Link to select which Pagelets appear on the home
page
• Pagelets are available in groups called portal packs for most applications
• Menu 2.0 pagelet gives users an alternative to drop-down menu navigation
• The menu consists of a hierarchy of cascading folders and content references

– Favorites
• The Favorites drop-down menu gives access to recently used links as well as to the
links that you add to your favorites list
• Setting up PeopleSoft favorites
– Navigate to a page or a type of content
– Click the Add to Favorites link in the header
– Enter the label of the favorite
– Click the Add to Favorite button
• Using PeopleSoft favorites
– Click the Favorites folder in the navigation header
– Select the content reference to access

– Favorites
• PeopleSoft Favorites Basics
– The default name for the favorite is the label used in the navigation
– The sequence determines the order of appearance
– All favorites appear as content references in the Favorites folder at the top of
the navigation
– Content references in the Favorites folder are navigational shortcuts
– Favorites are associated with user ID and are available on any browser upon
sign-in

– Favorites
• PeopleSoft favorites are different from browser favorites as described in the
following table

– Search
• Another method of navigation is through the search feature on the homepage. To
use the search feature:
– Type a word to search
– Click the Search button
– Click a link

Activity 1 : Using Basic Navigation Tools
– Sign in to the PeopleSoft Pure Internet Architecture
– Use Content References to load components
– Create PeopleSoft favorites
– Navigate with searches

Using Search Pages
– Search Pages have these properties
• They are an interim step between a content reference and its component
• They are dynamically built based on several definition properties
– Search pages enable users to
• Find data
• Select from a list of data rows
– Type of Search Pages
• Depending on how we configure a component, we may see
– A basic search page
– An advanced search page

Using Search Pages
– Basic Search – Key Points
• You can select advanced or basic search from a link on the search page
• You can click the Search button with no search parameters and the search returns
all data rows to a maximum of 300
• You can identify the maximum number of rows that you want returned from the
search, upto the system default
• You can configure the system default for the maximum numbers of rows to return
on the PeopleTools Options page
• It may be case-sensitive
• You can use wildcard characters
• You enter search parameters in one search field
• You cannot change the comparison operator (in this example, text fields always use
begins with.)

Using Search Pages
– Advanced Search
• You can select advanced or basic search from a link on the Search page
• Clicking the Search button with no search parameters returns all data rows to a
maximum of 300
• You can identify the maximum number of rows that you want returned from the
search, upto the system default
• Search Criteria may be case-sensitive
• You can enter multiple search parameters simultaneously to narrow the results
below the 300-row limit
• You can select from multiple comparison operators, such as starts with, and so on.

Using Search Pages
– Search Keys – The search fields that appear on the page are determined in
the record definition. They are called
• Search Keys
• Alternate Search Keys

Identifying definitions
– Below diagram shows the relationship of definitions that make up the
PeopleSoft User Interface

– PeopleSoft definitions are independent and reusable. You combine fields to
create records. You use pages to create components that interface with
records. You secure components through PeopleTools security and create
navigation through the portal registry
– The component definition is central to the user interface
– Component definitions determine:
• The search page
• The toolbar buttons at the bottom of the screen.
• The mode of the component: update/display, history, or correction
• The pages that we access
• Page tabs or links

– The component definition is central to the user interface

– The page definition is what the user sees
• Each component can hold multiple pages
• Tabs at the top of the screen enable access to each page
• Pages contain fields
• Levels segment pages
• All pages include a level zero, and many have other levels as well
• Level zero contains the highest-level key values that make a row of data
unique
• Level zero key values are entered once, when a new row is created
• A scroll area or a grid, if one exists, binds other levels

– The Field definition is the basic elements in PeopleSoft
• Fields are the basic elements
• Fields on a page hold data that we save to tables in the database
• Fields support many data types
• Fields can be interactive or display-only
• PeopleSoft applications support ten basic field data types: character, long
character, number, signed number, date, time, datetime, image, image
reference, and attachment

– Pages can contain different field types represented by different controls,
including:
• Edit boxes
• Drop-down list boxes
• Check boxes
• Radio buttons
• Images

– From any component in the application, use CTRL + J to see an
information page that includes the names of the component definitions
that make up the interface
– URL Information
• The URL also give you information about
the current component.
• The last two elements in the URL are
<MenuName>.<ComponentName>.<Market>

Entering and Modifying Data
– Components include these buttons at the bottom of the screen:
• Save
• Return to Search
• Next/Previous in List
• Add
• Update/Display
• Show History
• Correct History

– When we add new rows of data for an entire component, we start by
entering a new high-level (level zero) key value.
– We add a new level zero value from either:
• The search page
• The component – if you are already looking at a row of data in a component,

you can use the Add button to create a new row

– To update existing information or insert new rows at level one:
• Use the insert row button in a scroll area
• Use the insert row button in a grid
Program Agenda
• Validating Data
Explaining PeopleSoft Architecture

Describing PeopleSoft Databases
– Tables in PeopleSoft databases fall into three general areas

– System catalog tables contain database metadata
– These tables:
• Track all objects in the entire database
• Are analogous to a table of contents
• Vary based on platform

– PeopleTools tables contain metadata about the PeopleSoft application
installed on the database
– PeopleTools tables:
• Are structured consistently between applications
• Vary in content between applications
• Can be modified by PeopleTools such as PeopleSoft Application Designer
• Are converted to HTML and delivered to a browser
• Use the naming convention PS*; for example, PSPNLDEFN
– Definitions are the elements that make up the application user interface. They
are stored in PeopleTools tables

– The following table describes PeopleTools tables:

– Application data tables hold the data that users enter into the database
– Specific tables are determined by the application
– Developers can create more of these tables
– Content is modified through the user interface
– Tables use the naming convention PS_*; for example,
PS_CUSTOMER_TBL.

Explaining Data Transfer in PeopleSoft Internet Architecture (PIA)
– The architecture of PeopleSoft Internet Architecture takes raw data
from the application database and delivers it in the form of an
interactive user interface on a standard web browser
– In PIA, there are no PeopleSoft executable on the client
– The client can be an internet device that uses standard internet
technologies to communicate with PeopleSoft applications
– Components of PeopleSoft Internet Architecture are

Explaining Data Transfer in PeopleSoft Internet Architecture
– With PeopleSoft Internet Architecture, users do their work with a
browser; no code is required on the client
– Advantages to delivering the user interface on a browser include:
• Easy access
• Platform independence
• Low bandwidth access
• Simple application maintenance and deployment

– Web Server
• When a client connects to the server, the system displays a sign-in window that
the Web Server sends to the browser in HTML
• Web services software manages communication with the browser
• Web services software displays HTML, but the HTML has to exist first
• The database server has definitions, not HTML (usually), stored in tables
• You must have one more piece to complete PeopleSoft Pure Internet
Architecture

– Application Server
• When a user navigates through a PeopleSoft application using a browser, a number
of things happen.
• A request for a page of data about an employee, Sachin, goes through these
architecture elements to the browser:
• PeopleTools tables
– All the raw data required to assemble the employee data component is
contained in PeopleTools tables. This includes definitions of the component,
page, fields, navigation, and other elements. This raw data goes to the
application server for assembly as HTML

• Application data tables
– After the request is made, the information about Sachin is retrieved
and sent to the application server
• PeopleSoft services
– There are dozens of individual processes running. One (PSAPPSRV)
takes the PeopleTools data and application data about Sachin and
assembles it into HTML for display
• Oracle Tuxedo and Oracle Jolt
– Oracle Tuxedo manages the multiple connections to the database.
Oracle Jolt is a Java-based communication protocol. Jolt and Tuxedo
send the assembled HTML to the web server

• Java servlets
– Individual programs manage the state of each user session, including a
buffer that allows the use of the browser Back button. Servlets pass the
HTML to web services for display
• As seen in this diagram, the application server completes the connection,
managing communication with the database and delivering HTML to the web
server fro display

– Server Characteristics
• As a rule, you want the application server to be the fastest system possible, as
its job is processor-intensive
• The web server requires the most memory, as it might store thousands of
HTML pages. Requirements vary depending on user population and other
factors
– Server Cache
• Storing certain data on the application server and web server enhances
performance, reducing trips to the database for commonly accessed
information
• The application server caches definition data such as fields, pages, and
components
• The web server caches images, style sheets, and JavaScript

– Development Consideration
• When developing for PeopleSoft Pure Internet Architecture interfaces, consider
these issues :
– No Code runs on the client
– All codes run on the application server
– Running code requires a server trip and a browser refresh
• Disadvantages of having no local code
– Any time that a user does something that requires processing, application
generates new HTML and then passes it to the web server for display
– PeopleCode is attached to fields that run on simple actions such as
changing focus from one field to the next. This requires server processing.
If the application server has to reassemble pages every time a user
presses Tab, performance can slow drastically

• Deferred processing is one solution to limit server trips. With deferred processing,
user actions are processed as a single batch. Processing normally takes place
when user saves work. You can delay some actions that are processed on the
server
• User experience is a large factor in the success of deferred processing
• When you enable deferred processing, trips to run logic on the server are limited.
These trips are deferred when the user:
– Enters data
– Uses a prompt table
– Passes a related field
• Events that do trigger server trips include:
– Selecting a new page tab
– Inserting or deleting a row in a grid or scroll area
– Clicking any button or icon (for example, Refresh)

• Multi-row insert is another development option to limit server trips. Multi-row
processing:
– Is used when entering multiple rows of data
– Enables the user to enter the number of data rows to insert
– Holds data in the component buffer until you save the component

Identifying Requirements for the Development Environment
– The development environment primarily consists of PeopleSoft Application
Designer
– This application is installed on the Microsoft Windows client with the
installation of PeopleTools
– PeopleSoft Application Designer:
• Manipulates data in the PeopleTools tables on the database
• Connects to the database directly or by means of an application server

– Two-Tier Client Workstations
• As a developer, you manipulate data directly in the database
• As you create definitions in PeopleSoft Application Designer, the result is rows of
data in PeopleTools tables
• The two-tier client connects directly to the database. This connection offers the
most functionality, but it can be slow unless connected to the database over a fast
local area network (LAN)
– System Requirements include:
• Microsoft Windows
• PeopleSoft client software (Application Designer, Data Mover, and so on)
• Database client software to manage the communication with the relational database
management server (RDBMS). Connectivity software varies depending on the
database platform being used

– Reasons to use two-tier client workstations include:
• They’re easy to set up
• They’re fast if the workstation is local to the database and on a fast network
• They’re required for certain tasks:
– Using Data Mover for loading data directly to the database tables
– Upgrading your database in Application Designer
– Reasons not to use two-tier client workstations include:
• They may provide hackers with too much access to the database
• They’re hard on database performance, because the database has to manage all
the connections
• They slow performance on wide area networks (WANs).

– Three-Tier Client Workstations
• The three-tier client uses BEA Tuxedo and an application server to manage the
database connection
• This speeds performance over WAN connections and makes for a thinner client,
because no database client software is required
• This system requires Microsoft Windows and the PeopleSoft client software. The
connection to the application server requires the TCP/IP protocol
– System requirements are:
• Microsoft Windows
• PeopleSoft client software (PeopleTools)
• TCP/IP communication protocol (already installed in most Windows systems)

– Security and Three-Tier Client Workstations
• Because the application server makes the database connection, users on a three-
tier client do not have the direct access to the database that can invite hacking
attempts
– Reasons to use three-tier client workstations include:
• They are the fastest in most situations (multiple users or a WAN)
– BEA Tuxedo is a much more efficient communication method than SQL,
especially if bandwidth is limited
• Multiple connections are managed by the application server, so the database is not
slowed by this job
– They are more secure, because there is no direct database access

– This diagram illustrates how the two types of development workstations might
fit into the architecture:

– Two-Tier Vs Three-Tier Connections
Program Agenda
• Validating Data
Understanding Effective Dating

Effective Date Fields
– Tables containing an effective date (EFFDT) field as a key are called
effective-dated tables
– To be effective dated, a table must include the field EFFDT as a
descending order key
– Many effective-dated tables also include the field EFF_STATUS. This
field reports whether the row of data is active (A) or inactive (I)
– Effective dating:
• Retains historical data
• Stores data for future use
– Effective-dated tables include three types of rows:
• Future
• Current
• History

– When entering rows into effective-dated tables, you have four action
choices:
• Add
• Update/Display
• Include History
• Correct History
– Effective dating validates data by ensuring that:
• Users have access to current, active information
• Historical data is stored
• Users can enter future changes at any time, and that these changes
become available only when the effective date arrives

– Summary of the Action Modes

– Entering data into effective-dated pages is unique. Even though all the
data resides on a single table, the page contains two levels
– The current effective date for a given high level key is displayed
– This design enables you to enter multiple effective dates for each high-
level key
– All effective-dated pages follow these rules:
• All rows are categorized as history, current, or future
• When you insert a new row, data for all fields is copied from the current row
• When prompting to tables that are effective dated, only current, active
values are available
Program Agenda
• Validating Data
Validating Data

Describing Prompt Tables
– Prompt Table Edits
• In a prompt table edit, field values can be filled or edited only from a list of values in
the prompt table
• This diagram shows the prompt table PSU_INSTR_TBL providing a list of values for
the Instructor field in the PSU_CRS_SESSN table
Validating Data

– Prompt Process Flow
• Structurally, a prompt table is no different from any other application data table. It
stores values that other tables can validate against
• This diagram illustrates the process flow of the prompt button
Validating Data

– Lookup Page
• When you click the prompt button, a lookup page displays. You may notice that this
page, although called a lookup page, is almost identical to the search pages that
you see when you select a content reference. The mechanism that creates the
lookup is the same for creating a search page
– How to Identify Prompts on the Screen
• Fields that validate against prompt tables typically display a magnifying glass icon
to the right of the field
– How to Use Prompt Buttons
• Click the prompt icon to the right of the field. A lookup page will appear from which
you can search for a valid value. You may also enter a valid value into the field
bypassing the lookup page.
Validating Data

Comparing Validation Types
– In addition to prompt tables, there are other types of validation:
• The translate table (PSXLATITEM) edit
• The Yes/No edit
• The 1/0 edit
– Fields that have translate values must:
• Be a Character data type
• Have a length less than or equal to 4
• Have fewer than 30 valid values
• Be static data
• Need only a long and short description
Validating Data

– Translate Table Edit
• The translate table is a universal prompt table that many fields in an application
share
• The translate table is similar to a prompt table, but there are significant differences
as well
– The translate table is a specialized effective-dated prompt table that is keyed
to specific field names. It has a fixed structure that you cannot customize
– You use the translate table to quickly enter a list of values for the prompt on a
specific field
» Using the translate table is great if you need only a value and a short or
long description
» If you need other descriptive information, you should create a prompt
table
Validating Data

– Translate Table Edit
• Prompt tables can be built to any specification.
• The default page control for a field with translate values is a drop-down list box
• The translate table is cached on the application server
– Structure of the Translate Table
Validating Data

– Yes/No Edits
• The translate table stores a special set of values for binary switches, which you set
by using the Yes/No table edit:
– Yes/No
– On/Off
– Selected/Clear
• The Yes/No table is a subset of translate table values, but it is set up differently
during development
• The field name is PSYESNO, and values are either Y or N
• The default is a Y as the value when selected and an N for the value when cleared.
The developer, as required, can reverse the behavior
• The default page control of a Yes/No prompt on the browser is a check box
• The advantage of this type of edit is that you have a way of having two valid values
for many fields without having to have two translate values for each field.
Validating Data

– 1/0 Edits
• If you validate a number field, the Yes/No edit will appear as a 1/0 edit. Being able
to multiply by 1 or 0 makes this option more versatile if used in SQL, SQR, or
PeopleCode
– Summary of Prompt and Translate Table Characteristics
Validating Data

– Translate Table Considerations
• This table shows considerations for when to use a prompt table edit and when to
use the translate table edit
Validating Data

Explaining Tableset Sharing
– Use tableset sharing to filter prompt table choices based on business rules
– In PeopleSoft applications, a large percentage of the tables are keyed with one
of two fields:
• Business Unit - Business Unit is the key field for transaction tables
• SetID - SetID is the key field for control tables
Validating Data

Explaining Tableset Sharing
– Many PeopleSoft applications include prebuilt tableset sharing that filters
results by product line, department, reporting structure, region, and other
organizational lines
– This diagram shows prompt values that have been limited by location

PeopleSoft Overview

Hochgeladen von

Dokumentinformationen

Originalbeschreibung:

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

PeopleSoft Overview

Hochgeladen von

Copyright:

Verfügbare Formate

PeopleSoft Overview

• Navigating PeopleSoft Application

• Explaining PeopleSoft Architecture

• Understanding Effective Dating

• Navigating PeopleSoft Application

• Explaining PeopleSoft Architecture

• Understanding Effective Dating

• The component – if you are already looking at a row of data in a component,

• Navigating PeopleSoft Application

• Explaining PeopleSoft Architecture

• Understanding Effective Dating

• Navigating PeopleSoft Application

• Explaining PeopleSoft Architecture

• Understanding Effective Dating

• Navigating PeopleSoft Application

• Explaining PeopleSoft Architecture

• Understanding Effective Dating

Das könnte Ihnen auch gefallen