How date format works on Activity based email notification

Below are the sequence of steps the activity checks for date format.

1. Initially this looks for user defined date format in Regional Settings.
2. If above setting is not defined then this looks for the date format set for the browser language option settings.
3. if above 1 and 2 settings are blanks, then this takes the date format from system level defined settings.

Details of each step with screenshots.

1. User can define date format in My personalizations.

2. Local default settings for browser language options.

“M stands for MM/DD/YYYY” and “D stands for DD/MM/YYYY”.

Browser language option looks like below.

3. System level default settings.

Analytic Engine and Analytic Grid with simple Example

This example is to understand how to create and use Analytic Grid and Analytic Engine which is available in PeopleTools.

This is a simple example to create Read Only Analytic Grid without any PeopleCode used.

This can be more complex if Analytic Grid is used as Read/Write. (I will not cover Read/Write Analytic Grid in this example).

Example: To Create Analytic Grid for Location based Department based Head Count from Job record.

Preview:

 

Below Steps are used to create Analytic Grid for above example:

Note: Analytic Grid can be based on Physical Record or View. However if view is used then the Analytic Grid will be read-only. For read-write analytic grid physical record is required with the version record. As this example is to demonstrate only read-only I am using view for this example.

Step 1: Create a view over Job record or Job effective date view with LOCATION, DEPTID, PM_COUNT fields. This is used for Analytic Grid Data Cube Collection

a) Create a view and insert the fields to the record LOCATION, DEPTID, PM_COUNT. PM_COUNT is a number field and LOCATION and DEPTID as Primary Key.

b) Save the view as “PM_HEADCOUNT_VW”

c) Provide the below SQL in the view.

SELECT LOCATION , DEPTID , COUNT(*) AS PM_COUNT   FROM PS_PM_JOB_VW   GROUP BY LOCATION   ,DEPTID

Step 2: Create a work record which is used for Analytic Grid Presentation Cube Collection.

a) Create a work record with LOCATION, DEPTID, PM_COUNT fields.

b) Save the work record as “PM_HDCOUNT_WRK”

Step 3: Creating Analytic Model.

a) Create New Analytic Model from Application designer.

b) Right click on the “Dimension” and create two dimensions as LOCATION and DEPTID as shown in the image.

c) Save the Analytic Model as “PM_HEADCOUNT_AM”

d) Right Click on the Cubes and Create “HEADCOUNT” cube and attach “LOCATION” and “DEPTID” dimensions to the cube as shown below.

e) Right Click on the Cube collection and create “DATACUBECOLLECTION” cube collection and associate “HEADCOUNT” cube to the Cube Collection and assign the created view “PM_HEADCOUNT_VW” in “Main Record” section of General Tab as shown below.

 

f) Map the appropriate fields in “Field Map” Tab as shown.

g) Right Click on the Cube collection and create “PRESENTATIONCUBECOLLECTION” cube collection as above and associate “HEADCOUNT” cube to the Cube Collection and assign the created work record “PM_HDCOUNT_WRK” in “Main Record” section of General Tab as done for “DATACUBECOLLECTION”. Map the appropriate fields in the “Field Map” Tab.

h) Create “Explicit Dimension Set” to filter value based on Location or Department. To Create “Explicit Dimension Set” Click on “Explicit Dimension Set” shown in above example and right click to add “Add Dimension Set”. Add the dimension set as shown in the below Image.

i) Save the Analytic Model.

Step 4: Creating Analytic Type.

a) Create new Analytic Type from application designer and associate the Analytic Model (PM_HEADCOUNT_AM) to this Analytic Type. To add Analytic Model click on “Model Tab” of Analytic Type and from Menu bar under Inset menu select “Analytic Model..”. Select the PM_HEADCOUNT_AM Analytic model and this will add into Analytic Type.

b) Save the Analytic Type as “PM_HEADCOUNT_AT”.

Step 5: Creating Analytic Instance.

a) Navigate to the Main Menu > PeopleTools > Utilities > Administration > Analytic Inst. Create/Del/Copy in the PIA.

b) Select the Analytic Type (PM_HEADCOUNT_AT) and Provide the Analytic Instance name (PM_HEADCOUNT_IN). Click on “Create Analytic Instance” button.

c) This will create the Analytic Instance “PM_HEADCOUNT_IN”.

Step 6: Load Analytic Instance.

a) Navigate to the Main Menu > PeopleTools > Utilities > Administration > Analytic Instance Load/Unload in the PIA.

b) Search for “PM_HEADCOUNT_IN” (i.e. Appropriate instance name according to you)

c) Click on “Load Analytic Instance” button from the below Screen to load the Analytic Instance.

Step 7: Verify Analytic Model using Analytic Model Viewer.

a) Navigate to the Main Menu > PeopleTools > Utilities > Administration > Analytic Model Viewer.

b) Search the Analytic Instance “PM_HEADCOUNT_IN” and click on the instance link.

c) Select the “PRESENTATIONCUBECOLLECTION” to view the Analytic Model functioning.

Step 8: Create a Page with Analytic Grid to associate the Analytic Model to Analytic Grid.

a) Create a Page and Place an Analytic Grid control to the Page.

b) Add the work record(PM_HDCOUNT_WRK) fields in the Analytic Grid which is as main record in “PRESENTATIONCUBECOLLETION” cube collection.

 

c) Set the properties of the Analytic grid as follows.

d) Analytics Instance in the Grid Properties shown above is the page field placed in the page and this field has the value of Analytic Instance which is created through online (PM_HEADCOUNT_IN). This value(Analytic Instance) is assigned in prebuild event of component. (Create a separate work record with a field to assign analytic instance on this. Analytic instance can be assigned as <Recod>.<Field>.Value = “<ANALYTIC_INSTANCE>” for this example PM_HEADCOUNT_WRK1.DESCR.Value = “PM_HEADCOUNT_IN”).

e) Save Page and Component. (INSTALLATION record can be used as search record to bypass search page).

f) Register the component and View the page online and see the Analytic Grid Functioning.

 

Note: Make sure “Analytic Server” is UP and running in “Application Server”.

PS Mobile/Tablet Solutions

Delivered:

• Mobile Company Directory - Doc ID 1494986.1 and 1494952.1
• Mobile Approvals - Doc ID 1505021.1
• Mobile Expense - Doc ID 1505021.1
• Mobile eProcurement

Planned Solutions(In Future Releases):

• Time and Labor
• Absence Management
• Cash Position Management
• HR Self-Service
• Dash Boards

Some more details documented on document id: 1504427.1
For video features: Document ID: 1362821.1

One Stop Shop for all useful Queries

I have created an Excel Tool to collect the Useful Queries in one place, i.e. One Stop Shop for all useful Queries.
Use of this Tool:
1. This can be used for One Stop Shop for all the queries used in Development And Support.
2. This can be used for One Stop Shop for all your personal Queries.. (As local Copy)
Download Link: Excel Tool To store all Useful Queries

PeopleTools 8.53 Improvements

Some important improvements got introduced in how customers deploy, scale, and update peoplesoft applications with features like virtualization and the PeopleSoft Update Manager (PUM).

Here are some of the major improvements in PeopleTools 8.53 release:

• Oracle’s Secure Enterprise Search – Provides secure, free-text search within PeopleSoft applications across multiple objects and multiple applications for a more streamlined search-driven navigation approach.
• Related Actions – Enables end users to take relevant actions on objects within the context of transactions rather than using lengthy traditional menu paths.
• Activity Guides – Provides for the deployment of guided business processes, which facilitate a variety of activities from self-service to administration.
• Pivot Grids – Offers self-service, real-time, multi-dimensional analytics embedded into PeopleSoft applications providing end users with the actionable information needed to make decisions.
• WorkCenters – Consolidates user tasks, exceptions, alerts, links, reports, and queries into a single, secure, role based “command center” that can be personalized and configured by end users for increased productivity.
• Cascading Style Sheets (CSS) – Improves use and support of CSS and enables customers to easily configure their PeopleSoft system to reflect organizational branding (e.g. color, graphics, etc.).
• Oracle Private Cloud Deployments of PeopleSoft – Enables multiple PeopleSoft application instances to be consolidated on Oracle Exalogic, providing high capacity and performance, dynamic scaling and provisioning using Oracle Virtualization.  This also dramatically improves system management, patching, and maintenance.  All of this reduces total cost of ownership.
• Secure by Default - As part of Oracle Secure by Default initiative, PeopleTools 8.53 will request passwords for delivered accounts necessary for system initialization and disabling other sample accounts. We will also be delivering a salted SHA-1 hash for PeopleSoft passwords. The salted SHA-1 hash enhancement will not affect upgrades.

Minimum RDMS Privileges of the PSADMIN Role

 

|--------------------+------------------------------------+------------| 
|                    |                                    |            | 
| Privilege          | Comments                           | Removable? | 
|                    |                                    |            | 
|--------------------+------------------------------------+------------| 
|                    |                                    |            | 
| ALTER SESSION      | This is done during some SQR       | No         | 
|                    | processes and is also necessary to |            | 
|                    | enable SQL tracing during          |            | 
|                    | performance tuning                 |            | 
|                    |                                    |            | 
|--------------------+------------------------------------+------------| 
|                    |                                    |            | 
| ALTER TABLESPACE   | PeopleSoft does not alter the      | Yes        | 
|                    | tablespace itself, this is a job   |            | 
|                    | for the DBA instead.               |            | 
|                    |                                    |            | 
|--------------------+------------------------------------+------------| 
|                    |                                    |            | 
| ALTER ROLLBACK     | The rollback segments should be    | Yes        | 
| SEGMENT            | completely maintained by the DBA.  |            | 
|                    |                                    |            | 
|--------------------+------------------------------------+------------| 
|                    |                                    |            | 
| CREATE CLUSTER     | PeopleTools cannot do this         | Yes        | 
|                    | directly and is therefore not a    |            | 
|                    | function of PeopleSoft, but could  |            | 
|                    | be an option for performance       |            | 
|                    | tuning that the DBA may wish to    |            | 
|                    | take                               |            | 
|                    |                                    |            | 
|--------------------+------------------------------------+------------| 
|                    |                                    |            | 
| CREATE DATABASE    | Private database links are used    | Yes        | 
| LINK               | during the upgrade compare         |            | 
|                    | process.  Although, perhaps only   |            | 
|                    | the DBA should be creating         |            | 
|                    | database links.                    |            | 
|                    |                                    |            | 
|--------------------+------------------------------------+------------| 
|                    |                                    |            | 
| CREATE PUBLIC      | Public database links are not used | Yes        | 
| DATABASE LINK      | by PeopleSoft                      |            | 
|                    |                                    |            | 
|--------------------+------------------------------------+------------| 
|                    |                                    |            | 
| CREATE PUBLIC      | Public synonyms are created during | No         | 
| SYNONYM            | the upgrade compare process        |            | 
|                    |                                    |            | 
|--------------------+------------------------------------+------------| 
|                    |                                    |            | 
| CREATE SEQUENCE    | Sequences are not used by          | Yes        | 
|                    | PeopleSoft                         |            | 
|                    |                                    |            | 
|--------------------+------------------------------------+------------| 
|                    |                                    |            | 
| CREATE SNAPSHOT    | PeopleSoft does not use snapshots  | Yes        | 
|                    | by default, but they can be used   |            | 
|                    | to maintain generated tables.      |            | 
|                    |                                    |            | 
|--------------------+------------------------------------+------------| 
|                    |                                    |            | 
| CREATE SESSION     | This allows connection to the      | No         | 
|                    | database and is essential          |            | 
|                    |                                    |            | 
|--------------------+------------------------------------+------------| 
|                    |                                    |            | 
| CREATE SYNONYM     | Private synonyms are created for   | No         | 
|                    | PSOPRDEFN and PSLOCK for each user |            | 
|                    |                                    |            | 
|--------------------+------------------------------------+------------| 
|                    |                                    |            | 
| CREATE TABLE       | Data Designer created tables       | No         | 
|                    |                                    |            | 
|--------------------+------------------------------------+------------| 
|                    |                                    |            | 
| CREATE VIEW        | Data Designer creates views        | No         | 
|                    |                                    |            | 
|--------------------+------------------------------------+------------| 
|                    |                                    |            | 
| CREATE PROCEDURE   | Not used directly by PeopleSoft.   | Yes        | 
|                    | Useful in conjunction with         |            | 
|                    | triggers. Before Oracle 7.3 would  |            | 
|                    | be needed in conjunction with      |            | 
|                    | triggers as triggers are not       |            | 
|                    | compiled, whereas packaged         |            | 
|                    | procedures are.                    |            | 
|                    |                                    |            | 
|--------------------+------------------------------------+------------| 
|                    |                                    |            | 
| CREATE TRIGGER     | PeopleSoft does not use triggers   | Yes        | 
|                    | by default.  However this is an    |            | 
|                    | option for additional auditing.    |            | 
|                    | In which case CREATE PROCEDURE     |            | 
|                    | would be an advantage too.         |            | 
|                    |                                    |            | 
|--------------------+------------------------------------+------------| 
|                    |                                    |            | 
| CREATE TABLESPACE  | PeopleSoft does not alter the      | Yes        | 
|                    | tablespace itself, this is a job   |            | 
|                    | for the DBA instead.               |            | 
|                    |                                    |            | 
|--------------------+------------------------------------+------------| 
|                    |                                    |            | 
| CREATE USER        | A new database user is created     | No         | 
|                    | when a new PeopleSoft user is      |            | 
|                    | created                            |            | 
|                    |                                    |            | 
|--------------------+------------------------------------+------------| 
|                    |                                    |            | 
| CREATE ROLLBACK    | The rollback segments should be    | Yes        | 
| SEGMENT            | completely maintained by the DBA.  |            | 
|                    |                                    |            | 
|--------------------+------------------------------------+------------| 
|                    |                                    |            | 
| DROP PUBLIC        | Public database links are not used | Yes        | 
| DATABASE LINK      | by PeopleSoft                      |            | 
|                    |                                    |            | 
|--------------------+------------------------------------+------------| 
|                    |                                    |            | 
| DROP PUBLIC        | Public synonyms may be dropped     | No         | 
| SYNONYM            | during the upgrade compare process |            | 
|                    |                                    |            | 
|--------------------+------------------------------------+------------| 
|                    |                                    |            | 
| DROP ROLLBACK      | The rollback segments should be    | Yes        | 
| SEGMENT            | completely maintained by the DBA.  |            | 
|                    |                                    |            | 
|--------------------+------------------------------------+------------| 
|                    |                                    |            | 
| DROP TABLESPACE    | PeopleSoft does not alter the      | Yes        | 
|                    | tablespace itself, this is a job   |            | 
|                    | for the DBA instead.               |            | 
|                    |                                    |            | 
|--------------------+------------------------------------+------------| 
|                    |                                    |            | 
| DROP USER          | A database user is dropped when a  | No         | 
|                    | new PeopleSoft user is removed     |            | 
|                    |                                    |            | 
|--------------------+------------------------------------+------------| 
|                    |                                    |            | 
| MANAGE TABLESPACE  | This allows tablespaces to be      | Yes        | 
|                    | taken on and off line during a     |            | 
|                    | backup.  This is a job for the DBA |            | 
|                    | instead                            |            | 
|                    |                                    |            | 
|--------------------+------------------------------------+------------| 
|                    |                                    |            | 
| RESOURCE           | This is equivalent to CREATE       | Yes        | 
|                    | CLUSTER, CREATE PROCEDURE,         |            | 
|                    | CREATE_SEQUENCE, CREATE TABLE, and |            | 
|                    | CREATE TRIGGER that are all dealt  |            | 
|                    | with explicitly elsewhere.  It is  |            | 
|                    | used for compatibility with        |            | 
|                    | previous versions of Oracle7.      |            | 
|                    | Thus is privilege is not required  |            | 
|                    |                                    |            | 
|--------------------+------------------------------------+------------| 
|                    |                                    |            | 
| EXP_FULL_DATABASE  | Full exports could be performed by | Yes        | 
|                    | the DBA rather than the PeopleSoft |            | 
|                    | system administrator.  This also   |            | 
|                    | implies SELECT ANY TABLE.          |            | 
|                    |                                    |            | 
|--------------------+------------------------------------+------------| 
|                    |                                    |            | 
| IMP_FULL_DATABASE  | Full imports could be performed by | Yes        | 
|                    | the DBA rather than the PeopleSoft |            | 
|                    | system administrator  This also    |            | 
|                    | implies BECOME USER.               |            | 
|                    |                                    |            | 
|--------------------+------------------------------------+------------| 
|                    |                                    |            | 
| GRANT ANY ROLE     | This privilege is required in      | Yes        | 
|                    | order to grant the PSUSER role to  |            | 
|                    | the new database user when         |            | 
|                    | creating a PeopleSoft user in      |            | 
|                    | Operator Security.  However, if    |            | 
|                    | the PSUSER role is granted to      |            | 
|                    | SYSADM with the ADMIN OPTION then  |            | 
|                    | SYSADM can still grant PSUSER and  |            | 
|                    | GRANT ANY ROLE is no longer        |            | 
|                    | required.                          |            | 
|                    |                                    |            | 
|--------------------+------------------------------------+------------| 
|                    |                                    |            | 
| ALTER USER         | This allows the user, amongst      | No         | 
|                    | other things, to change passwords. |            | 
|                    | It is therefore required           |            | 
|                    |                                    |            | 
|--------------------+------------------------------------+------------| 
|                    |                                    |            | 
| BECOME USER        | This is required by and implicit   | Yes        | 
|                    | in IMP_FULL_USER, but is not       |            | 
|                    | otherwise required by PeopleTools  |            | 
|                    |                                    |            | 
|--------------------+------------------------------------+------------| 

Source: Oracle Doc ID: 1140413.1

Org Chart Viewer and Mobile Company Directory

Org chart viewer and mobile company directory from Pawan Mundhra

PeopleSoft Interaction Hub

Steps to Implement Data Archive Manager

Step1: Create Archive Object

Archive Record: Record from data need to archive.

Base Record: The record is selected is the base record of this archive object. This is a check box and only one can be base record.

History Record: History Record to which transaction data is needed to archive.

History Record Structure (Example):

1. Save as HR_ACCTG_LINE record to HRACTLN_HST and don’t copy any peoplecode associated with record HR_ACCTG_LINE.

2. Insert Subrecord PSARCHIVE_SBR at top in the record as shown in below image.

3. Build the table.

Step2: Create Archive Query

Archive Query contain Archive record name and all field selected.

Criteria: This is required to add criteria which filter the data for archiving.

Step3: Archive Template

Step4: Running Archive Process

Process Type:

1. Selection: Copy data from Archiving Record to History Record.

2. Delete: Deleting data from Archiving Record.

3. Remove from History: Deleting data from History Record.

4. Rollback: Copy data from History Record to Archiving record.

Note: Select the process type and run the process.

Absence Management White Papers to Assist with Implementations by Oracle

Oracle has recently provided Absence Management White Papers. Below are the documents can be find at Oracle support. You need login for these documents.

1. Absence Management Entitlement and Take Setup:

Document ID 1493866.1: This document (Document ID 1493866.1) provides an overview of how to set up the main components of Absence Management, such as Absence Entitlement and Take elements, as well as other supporting elements relevant to your Absence Management implementation.

2. Absence Management System Elements:

Document ID 1493879.1: This document (Document ID 1493879.1) provides an overview of the system elements related to Absence Management. System elements are building blocks used during the design and construction of your Absence Rules. Knowing how they work and when to use them should help you expedite the implementation of your Absence Policy rules in your company

3. Absence Management Self Service Setup :

Document ID 1493867.1: This document (Document ID 1493867.1) provides an overview and guidance on some of the important areas when setting up Absence Self Service. Throughout this document we are providing examples of different configurations supported in Self Service. 

Source: Oracle Support centre.

External People(non–employee / Applicant) Access for PeopleSoft Pages

Below steps helps to give access to components for external people.

This is required for many scenarios. Some Examples are:

1. Forgot password – Helps employee to retrieve login password.

2. External Candidate – Helps to apply  job for the company.

3. External candidate to register course – Helps external candidates to apply course. etc..

Steps to to give access for external people:

Step 1: Create a user id as EXTERNAL and set a password(PS) for it.Assign "External Applicant" & "Recruitment User"(optional) roles to this user-id. Save it.

Important : Do not attach any other Role to this user id.

Screens of roles

Step2: go to PeopleTools --> Webprofile --> Webprofile Configuration.

Then choose the profile (E.g. DEV)

Navigate to the "Security" tab and check "allow public access" and give the userid "EXTERNAL" and password "PS" and save it.

Step3: To access page use the below format.

"http://Your IP:Port/psc/ps/EMPLOYEE/HRMS/c/ComponentName.Market"

In Scroll Area, Clicking from "View All" to "View 1" Creates Empty Space

Problem Description:

In some scroll areas, when clicking from "View All" to "View 1" link, the page doesn't remove the extra space that was used from "View All" mode.

Solution:

For PeopleTools 8.50: This bug has been fixed on Patch 8.50.03 and higher.

For PeopleTools 8.52: This bug has been fixed on Patch 8.52.10 and higher. In normal case, we have tested for this issue on patch 10 and its working good for View all and View 1 action but some scenarios this is broken.

 

Reference document from oracle support: [Doc ID 1062053.1]

Release Value Proposition: PeopleTools 8.53 feature analysis

Oracle has planned to enhance/add below features in PeopleTools 8.53.

1. User Interface
2. PeopleSoft Search Framework
3. Lifecycle Management
4. Server Administration and Infrastructure
5. Security Administration
6. Integration Technology
7. Reporting and Analysis Tools
8. Development Tools

1. User Interface

a) Dramatic New Look and Feel: New style sheet for good look and feel. These changes also lay the groundwork for future user interface changes.

b) Related Actions/Related Content: PeopleTools 8.53 brings Related Actions to Pivot Grids, allowing users to take actions directly on data displayed in a pivot grid.

                                                         A new Related Actions widget can be used to display the Related Actions menu. This feature eliminates the need for a developer to write code for displaying the optional menu and for defining HTML areas on pages to display Related Actions.

                                                         Related Services can be configured in groups, which make it simpler to configure the same services that appear in multiple places.

c) WorkCentres and Dashboards: Application developers and designers can deploy dashboard-like pagelets within WorkCenters to provide better decision support for WorkCenter transactions. This capability combines some of the features and benefits of Dashboards with WorkCenters.

                                                    Applications can now consume remote pagelets in WorkCenters, Homepages, and Dashboards.

d) Activity Guide: In 8.53, the Activity Guide enables application developers to define a list of action items tied to transactional, collaborative, or manual tasks. The action item represents a task that can be tracked for assignment and completion, and is secured by roles and user lists. Activity Guides also enable a hierarchical list of action items.

                            A new Activity Guide WorkCenter template is available for use with building and configuring Activity Guides. This template provides a frame with the navigation controls used to traverse an Activity Guide. The WorkCenter template also provides the following features:

• A status bar to indicate the progress of the Activity Guide, and the Active Action item is highlighted.
• Ability to do pre-processing and post-processing for an action item.
• Ability to assign an action item to a role or a user.
• Ability to create dependency rules for action items.

2. PeopleSoft Search Framework

PeopleSoft Application Search framework features include:

• A search experience that functions similarly to the internet, providing a look and feel that users will find both familiar and intuitive.
• An Application Search that is available at any point in an application and can be configured to span multiple PeopleSoft applications. It enables users to initiate transactions or navigate to key information without using the PeopleSoft application menu or returning to the homepage to do so.
• The ability to use filters and facets to narrow result sets, further enabling users to identify and navigate to specific application content.
• Search results that display in prioritized order by relevance based on the provided search terms.
• Related Action menus that are embedded directly in the search results, allowing users to navigate straight to specific related transactions, which are prepopulated with the selected search results data.
• A Component Search function that enables users to search by keyword, thereby extending the versatility of virtually all existing search pages.

Key PeopleSoft Search Framework Enhancements:

• Performance
• New source types
• Oracle SES instance sharing
• Multiple FTP credential support
• Monitoring and diagnostics
• Duplicate search results
• Increased operator support

3. Lifecycle Management

a) PeopleSoft Update Manager

b) Configuration Management with the Data Migration Workbench(A brand new tool): The Data Migration Workbench is a new tool that helps users manage the process of moving configuration data from one system to another.

c) PeopleSoft Test Framework: Enhanced to support a number of new PeopleTools features and capabilities.

d) Three-Way Merge Support

4.  Server Administration and Infrastructure

a) Platform Components

b) Extending 64-bit Support to the Windows Server Platform: The application server uses 64-bit binaries on the Windows Server platform. The 32-bit Windows code for the application server will no longer be available.

c) A New Home for Customizations - PS_CUST_HOME : This change is optional; customers may continue to use a traditional PS_HOME if desired.

d) PeopleSoft Application Management Pack for Oracle Enterprise Manager 12c

e) Offload PS/nVision Workloads with Active Data Guard and Golden Gate

f) Support for Firefox Extended Support Releases: Firefox 17 is the anticipated minimum ESR to be certified with PeopleTools 8.53.

5. Security Administration

a) Secure by Default Initiative:

• Deliver all UserIDs with a password that must be set during Installation.
• Salt-enabled user Passwords.

6. Integration Technology

a) JavaScript Object Notation (JSON) from Documents

b) REST Web Services

c) Integration Network Enhancements

• Automated Network Status and Real-Time Notification of Errors
• Improved Life Cycle Utilities
• Bulk Update of Permission for Service Operations

7. Reporting and Analysis Tools

a) Reporting Console Enhancements:

• Drag-and-drop of folders and Process Bookmark as a sibling.
• Drag-and-drop of folders and Process Bookmark as a child of an existing folder.
• Rename of folders.
• Import folders and Process Bookmark of existing user.
• Dynamic Context Menu option on folder and Process Bookmark row for add, edit, rename, delete options.

b) New My Reports Pagelet:

• Display list of different systems/databases containing the reports and providing functionality for filtering reports based on a particular database.
• Opening of the actual report directly instead of a page to display a list of files.
• Grouping of multiple instances of the same report.

c) Chart Enhancements: PeopleTools 8.53 introduces a number of Chart Enhancements, including making use HTML, CSS3, and JavaScript instead of the server-based chart engine. The new charts incorporate improvements in scrolling and display and more closely match the overall PeopleTools look and feel.

d) Pivot Grid Enhancements:

• Multi Select Filters that provide the ability to filter data on multiple values instead of a single value.
• Progressive Filtering that shows only valid values for the current filter selection when a filter value is modified.
• Dynamic passing of prompt values into the Pivot Grid being displayed in a Related Content frame or in Related Actions.
• Chart-only view allows users to change layout using grid.
• Enabling of Pivot Grid pagelets to interact with each other and with transaction pages. Prompt and filter value changes can be published and subscribed to in real-time.
• Enhancements to the user interface.
• Pivot Grid Administration Component provides module to clone and delete Pivot Grid Models and personalization.
• Enhancements to the Pivot Grid Wizard.

8. Development Tools

PeopleTools 8.53 introduces a new feature in Application Designer that allows developers to define the field label alignment for new or modified pages. A configuration property can be set that defines whether new field labels should be right or left aligned. This feature greatly streamlines the otherwise manual process of field label alignment. Once a field is placed on a page, the developer retains the ability to change the label alignment where necessary.

 

Key PeopleTools 8.53 features Executive Summary:

PeopleSoft Styles and User Interaction Model

• New styles for a contemporary appearance.
• More flexibility in WorkCenters and Dashboards.
• Improvements to the Related Content Framework, Related Actions, and Activity Guides.

PeopleSoft Data Migration Workbench

PeopleSoft Update Manager (NEW)

• The customer does not have to be current on maintenance.

• The customer can select a single fix and find out if requisite fixes are available that must be applied with it.

• Dependencies are calculated by area of system affected rather than time, so fewer dependencies are required.

PeopleSoft Secure by Default Initiative

• Safeguards for ensuring that passwords for default user accounts are set during installation.

• Additional mitigation for brute force and denial-of-service attempts.

• Additional security for file attachments and the Report Repository.

Round Pie Chart Slice Labels

Slice the labels of pie chart to required(example 1) decimal place.

<SliceLabel>

<ViewFormat decimalDigit="1" decimalSeparator="." decimalDigitUsed="true" decimalSeparatorUsed="true" />

</SliceLabel>

Related content link in Dropdown

As shown in Image to create related content link in Dropdown we need to follow below steps.

Assumption: Component is created and Related content setup is done.

Below steps need to be done to use Related content in drop down.

Step1: Adding HTML Area to page.

Place a HTML area in the page to the created component.

Here “N_RELATED_ACTNS” is a custom Long char field.

In General Tab provide “RELATEDACTIONS” as page field name as shown in the image

Step 2: Hiding the Related Action Page field and making it modified by JavaScript.

Here People ID is the Related action Field defied in Related action setup page.

Make this field is hidden and set the page field property as below Image.

Note: Modified by JavaScript should be enabled.

Step 3: Code to set Related action to HTML area.

/*****************Start - Related Actions*************************/
For &i = 1 To &rs_var.ActiveRowCount
   &sActionShortLabel = &rs_var(&i).N_HR_EE_DB_WRK.N_RELATED_ACTNS.GetShortLabel("RELATED_ACTION");
   &sPopUpMenuJavaScript = GetHTMLText(HTML.N_GET_POPUPMENU);
   &rs_var(&i).N_HR_EE_DB_WRK.N_RELATED_ACTNS.Value = &sPopUpMenuJavaScript | GetHTMLText(HTML.N_REL_ACTIONS, String(&i - 1), "N_PEOPLE_ID_DR", "%Image(PT_BTN_ARROW)", &rs_var(&i).N_MSSACTION_EMP.N_PEOPLE_ID.Value, &rs_var(&i).N_MSSACTION_EMP.N_PEOPLE_ID.Value);
   
End-For;
/*****************End - Related Actions*************************/

Note: “ String(&i - 1)” is required if this is used in grid/scroll else this can be eliminated.

Custom HTML object Definitions used in above code:

1. N_GET_POPUPMENU  - (Object Type is HTML)

<script language="JavaScript">
function ShowPopUpMenu(sFieldName,nRow, sActionFieldName)
{
       CreateContextMenu(sFieldName,nRow, 3,"", 0, 0,"","%FormName",sActionFieldName);
       return ;
}
</script>

2. N_GET_POPUPMENU - (Object Type is HTML)

<a id="relatedActionsRow$%BIND(:1)"  class="PSHYPERLINKNOUL" href="javascript:ShowPopUpMenu('%BIND(:2)','%BIND(:1)','relatedActionsRow$%BIND(:1)');" title="%BIND(:5)" ac="1"  class="PTSESRSLTRLTDINFO">

<img border="0" src="%BIND(:3)" style="width: 12px; height: 8px; cursor: pointer; vertical-align:middle: text-bottom;" ac="1" noc="1">%BIND(:4)</a>

Analysing “PSQRYCRITERIA” Table

 

CONDTYPE and EXPRTYPE stores below code in PSQRYCRITERIA Table.

Field: Condition Type (CONDTYPE)
Code	Description	Return Code
2	equal to	EQU
3	not equal to	EQU-
4	greater than	GRE
5	not greater than	GRE-
6	less than	LES
7	not less than	LES-
8	in list	LIS
9	not in list	LIS-
10	Between	BET
11	not between	BET-
12	Exists	EXI
13	does not exist	EXI-
14	Like	LIK
15	not like	LIK-
16	is null	NUL
17	is not null	NUL-
18	in tree	TRE
19	not in tree	TRE-
20	eff dt <=	EDLE
21	eff dt >=	EDGE
22	eff dt <	EDLT
23	eff dt >	EDGT
24	first eff dt	EDFS
25	last eff dt	EDLS

 

Field: Expression Type (EXPRTYPE)
Code	Description	Return Code
0	effective sequence	ES
1	constant	CN
2	field	FD
3	Expression	EX
4	Subquery	SQ
5	list	LS
6	current date	CD
7	tree	TR
8	Prompt	PR
9	between const-const	CC
10	between const-field	CF
11	between const-expr	CE
12	between field-const	FC
13	between field-field	FF
14	between field-expr	FE
15	between expr-const	EC
16	between expr-field	EF
17	between expr-expr	EE
18	Tree prompt	TP

Detailed Information:

Record Field Name: QRYFUNCTIONS - QRYTRANSFUNCS

PeopleTools iPad Certification

Error on Javascript in PeopleTools 8.52: "hAction_win0 is not defined"

Below code may not work from PeopleTools 8.52. But this will work on below version of tools release (i.e. 8.50, 8.51).

hAction_win0(document.win0,pageFldName,0,0,inlabel,false,true); 

Reason:

"hAction_win0" is no longer used in PeopleTools 8.52.

Solution:

"hAction_win0" can be replaced with "submitAction_win0" for 8.52 PeopleTools.

Sample code:

submitAction_win0(document.%FormName,pageFldName,0,0,inlabel,false,true); 

Rowset FILL Method with JOIN / UNION Keyword

FILL method helps to fill stand alone rowset from database directly.

But sometimes it is required to fill rowset Using JOIN / UNION Keyword.

1. Using JOIN Keyword.

Local Rowset &rs = Createrowset(Record.TL_RPTD_TIME);

&rs.Fill("INNER JOIN PS_TL_RPTD_TIME TM ON TM.EMPLID = FILL.EMPLID WHERE FILL.PUNCH_TYPE = '0' AND FILL.EMPLID = :1", &emplid);

2. Using UNION Keyword.

Local Rowset &rs = Createrowset(Record.PERSON);

&rs.Fill("WHERE 1=0 UNION SELECT EMPLID, %DateOut(BIRTHDATE),BIRTHPLACE,BIRTHCOUNTRY,BIRTHSTATE,%DateOut(DT_OF_DEATH),%DateTimeOut(LAST_CHILD_UPDDTM) FROM PS_PERSON WHERE EMPLID = :1", &emplid);

Configuring Report Manager

 

Steps to configure and get Reports in Report manager.

1. Enable getting Reports in Report Manager.

2. Add New Folders.

3. Get new files to Process Monitor.

4. Assign/Create required Permission Lists/Roles to Users.

5. Configure the process.

6. Create a new run control id.

7. Run it.

8. Verify it.

 

For any reports to be visible to other people in Report Manager we need to do the following:

1. Activate the following Service Operations

• · Check Active (in Default Service Operation Version)

2. To Add New Folders, add them here. This is just to group by folders and has no security tied to it.

•   Verify they come up

3.  To get new files to Process Monitor

· Add PRL in System Settings –> Distribution File Options –> Add PRL & Description

• Bounce the Process Scheduler
• After running the report verify that the file is pulled up

4.  Create new permission list

• Add Report Manager access and Report Viewer access.

• ·Click Select All to give the Report Viewer Page access.

• Add other Reports access. This gives the option to run the reports. If the users don’t want/need to run the reports this may be skipped.

5.  Add new Role

• Add this role to users

• Verify required users got the Role

6.  Change the Process Destination, set the Destination Source, Folder Name and Distribute To.

7.   Run the process

• Create a new run control id

• Chose the process

• To ensure everything is correct, Click on the Job (Description)

• Click on Distribution of required Process, we must be able to see the given Folder Name and the Role.

8.  Verify the distribution by going to Report Manager –> List

 

Thanks a lot to my friend Ranjan Patro (http://in.linkedin.com/in/ranjanpatro) for creating this document.