SQR output and Fonts

There is limited support for True Type fonts in PeopleSoft.

Below is the extract from the PS delivered file. We may try with any font which is not listed below and in case if that font is not supported, PS converts it to the default font, which is Courier.

List of defined fonts in PeopleSoft:

Number --------------- Name
3 ----------------------- Courier

300 -------------------- Courier-Bold

4 ----------------------- Helvetica

400 -------------------- Helvetica-Bold

5 ----------------------- Times-Roman

500 -------------------- Times-Bold

6 ----------------------- AvantGarde-Book

8 ----------------------- Palatino-Roman

800 -------------------- Palatino-Bold

11 ---------------------- Symbol

12 ---------------------- ZapfDingbats

17 ---------------------- ZapfChancery-MediumItalic

18 ---------------------- Bookman-Light

23 ---------------------- NewCenturySchlbk-Roman

2300 ------------------- NewCenturySchlbk-Bold

30 ---------------------- Courier-Oblique

3000 ------------------- Courier-BoldOblique

31 ---------------------- Helvetica-Oblique

3100 ------------------- Helvetica-BoldOblique

32 ---------------------- Times-Italic

3200 ------------------- Times-BoldItalic

33 ---------------------- AvantGarde-Demi

34 ---------------------- AvantGarde-BookOblique

35 ---------------------- AvantGarde-DemiOblique

36 ---------------------- Palatino-Italic

3600 ------------------- Palatino-BoldItalic

37 ---------------------- NewCenturySchlbk-Italic

3700 ------------------- NewCenturySchlbk-BoldItalic

38 ---------------------- Helvetica-Narrow

3800 ------------------- Helvetica-Narrow-Bold

39 ---------------------- Helvetica-Narrow-Oblique

3900 ------------------- Helvetica-Narrow-BoldOblique

40 ---------------------- Bookman-Demi

41 ---------------------- Bookman-LightItalic

42 ---------------------- Bookman-DemiItalic


We can get this list of delivered SQR fonts in postscri.str file .

RVP for HCM and FSCM 9.2

The roadmap is clear, for HCM and FSCM 9.2. Yesterday, Release Value Propositions for HCM and FSCM 9.2 has been released by Oracle. Items like iPad certification (with Safari as browser) and Pivot Grids are great, however, more or less related to PeopleTools 8.52. So PT 8.52 has been a pre-requisite to use the same features/technology for HCM and FSCM 9.2.
Moreover, a new term has been introduced, PeopleSoft Interaction Hub for PeopleSoft Applications Portal. Unlike the old days, this product now comes with an HCM or FSCM license. This will be a great change for the customers who are using the most used features, Dynamic Unified Navigation and Site-wide branding. Earlier, for these features too, customers had to purchase the entire license.

HCM

Smart HR – extension on Template Based Hire
Headcount Pivot Grids
Profile Management Enhancements – based on Secure Enterprise Search
Open compensation cycle job changes
Compensation Pivot Grids
Compensation history
ePerformance Workcenter
ePerformance Outlook integration
E-learning homepage / self service
Recruitment Gateway – with various 360 screens like in CRM (Job Opening, Applicant)
Recruiting Pivot Grids
Benefits
Absence with Outlook integration
Approval via HTML e-mail
HR Helpdesk – self service homepage, FAQ enhancements, discussion forums


 FSCM
Extending Global Reach
Financial Control & Reporting Business Process Overview
Plan to Retire Business Process Overview
Program and Portfolio Management Business Process Overview
Order to Cash Business Process Overview
Plan to Produce Business Process Overview
Source to Settle Business Process Overview

Industry Enhancements – General Ledger, Healthcare, Higher Education / Research

PeopleSoft Cumulative Feature & Fit/gap analysis

In any PeopleSoft application or PeopleTools upgrade process, you will need to perform a fit gap between your current version of PeopleSoft in order to find the differences. This is a daunting task to do when it comes to delivered functionality. For example, many people want to know what are the major differences between my version and the new one.

Oracle provides a cumulative feature overview tool for PeopleSoft to start your fit gap analysis.This tool is basically an Excel spreadsheet, that enables you to quickly understand major changes that have occurred across multiple releases for any give product. For example, if you are on PeopleSoft FSCM 9.0 and are looking for the changes that have occurred between 9.0 and 9.1, this new tool allows you to enter your current version and will provide you with a list of these changes for all releases since your version with detailed descriptions. The same is applicable to any source and target PeopleTools release.

https://support.oracle.com/epmos/faces/DocContentDisplay?_afrLoop=1023358752541899&id=1117033.1&_afrWindowMode=0&_adf.ctrl-state=rturvgxol_4

SchedulerTransfer servlet - posting issue

Issue: Distribution agent failed to post the files to report repository.



Error message: The XML file returned by the web server is invalid. XML document object creation failed.

Solution: This is an issue with SchedulerTransfer servlet which requires authentication. When a report needs to get transfer to report repository, distribution agant use SchedulerTransfer servlet for this purpose. SchedulerTransfer servlet checks for the default local node and if there is no authentication there, it will get fail. The Default Local Node must have the Authentication Option set to 'Password'. Application server needs a restart post this change.


Navigation :  Peopletools > Integration Broker > Integration Setup > Nodes > Default Local Node
Must have Password Authentication.

PeopleTools->Portal- > Node Definitions

Portal Security Syncronization

PeopleSoft Internet Architecture (PIA) portal can be defined as the collection of folders and content refrences with the navigational structure. The portal registry is a tree structure where one need to register the content and further it can be organized. The portal registry consists of the following primary parts:

Folders

Content references

Nodes

The main table which consists of all the portal definitions is PSPRSMDEFN. Security mechanism is used for folders, content references, content reference links, tab definitions, pagelets, and user homepages. The hierarchical relationships and dependencies between objects in the portal registry determine what security settings each object must have. The portal won't work correctly if these security relationships aren't maintained.

A folder that is not public or hidden must have at least the level of access that its immediate child objects (folders, content references, and content reference links) have.

A content reference link must have exactly the same level of access as the object (content reference or content reference link) to which it links.

A content reference that represents a PeopleSoft component or iScript must have exactly the same level of access as the object that it represents.

Portal object security settings can become unsynchronized when you move portal objects from one database to another using the Project Copy feature in PeopleSoft Application Designer. When you merge projects this way, if the projects contain any portal objects with identical names, the security settings of the portal objects in the last project copied overwrite the security settings of portal objects copied earlier. Also, when a copied portal object doesn't overwrite an existing object, it changes the structure of the resulting portal registry hierarchy.

Use the Portal Security Synchronization page to reinstate the correct security relationships between objects in the portal registry after you copy a project that contains portal objects. The portal objects are synchronized as follows:

-- The security settings of each content reference are compared to the component or iScript that it represents, and updated to match.

-- The security settings of each content reference link are compared to the content reference or content reference link to which it connects, and updated to match.

-- The security settings of each content reference and content reference link are propagated to its parent folder, in addition to the parent folder's existing settings.

-- None of the parent folder's existing security access is reduced.

-- The security settings of each folder are propagated to its parent folder, in addition to the parent folder's existing settings.

Delete Invalid Security Option


When we move portal objects from one database to another, roles and permission lists assigned to folders and content references on the source database may not exist on the target database and therefore become invalid. Select the Delete Invalid Security check box on the Portal Security Sychronization page to remove non-existing roles and permission lists from folders and content references.


Main section >> calls INIT section >> and then CREFPERM

INIT

STEP01 -- Do Select -- Selects the OPRID and RUN_CNTL_ID from PS_AERUNCONTROL table (run control table for AE).


STEP02 -- Do Select -- Selects the PORTAL_NAME (EMPLOYEE, SUPPLIER etc...) and PORTAL_FLDRP_FLAG (This flag is to select if we wish to delete invalid security, we may skip this too and it will set to 'N') from PS_PORTAL_CSS_RUN.
CREFPERM
STEP01 -- PeopleCode -- Main step to do the processing for syncronization, invalid security etc...

Below are the tasks in brief what exactly PORTAL_CSS is all about .

1. Check for invalid permission lists.

This step figures out the Permission which is/are invalid and further it get deleted by the program for object in concerned portal.


2. Check for invalid roles.

This step figures out the Role which is/are invalid and further it get deleted by the program for object in concerned portal.


3. Check Parent folder permissions and roles.
Check for missing permission list on cref or differences in permission counts.



4. Compare permissions and permission count against PSAUTHITEM

5. Check for missing permission list on cref's parent folder.

6. Check for PeopleSoft iScript
7. Worklist URL

8. Some other type of CRef (UEXT, UGEN)

9. CRef Link Synchronization
Compare the link to it's parent folder. Also, it compares the permissions of the cref link against the object it's linked to

10. Folder Synchronization
Here, it will only select the nonpublic folders.



Navigation of PORTAL_CSS program: Main Menu > PeopleTools > Portal > Portal Security Sync

Bind Variables on PeopleSoft Home Page

Prior to PT 8.48 release, there was a record WEBLIB_MENU, using which we were able to pass the dynamic variables to show the same on PeopleSoft Home Page. Below is the


resolution (Resolution # 1, copied from Oracle PeopleSoft Metalink site)



From PT 8.48 and above, one will not be able to find out the record WEBLIB_MENU. The design has been changed. Below is another resolution (Resolution # 2) how to pass the bind

variables like User ID, Instance name etc on the home page.



Resolution # 1 (Prior to PT 8.48, Oracle PeopleSoft Metalink, resolution ID # 623430.1)



E-PIA : How do you add/modify bind variables to change the look and feel. [ID 623430.1]



Resolution # 2 (PT 8.48 and above)



1. Open up App Package PT_BRANDING > Class BrandingBase in application designer. Search for the string ‘add &addjs’. Add the below code above the comment which contains the string ‘add &addjs’:



&greeting = "User: " %UserId " in Database: " %DbName;





The overall code will be like:



/* Added to show the bind variables on the home page */

&greeting = "User: " %UserId " on Database: " %DbName;

/* add &addjs to PT_IFRAME_HDR_SWAN (bind 22) and PT_IFRAME_HDR(bind 23) */



If this looks fine in presentation, its okay, however, the style/font of this variable "&greeting" can be taken care by PSHOMEPAGE Style Sheet



2. Open the PSHOMEPAGE Style Sheet in application designer, locate the "greeting" style class and replace this piece of code with the below code:



/*.greeting {

color: #FFFFFF;

font-family: Arial, Helvetica, sans-serif;

font-size: 12pt;

font-weight: bold;

}*/



/* Customized for the home page bind variables looks*/



.greeting {

color: #FFFFFF;

font-family: Arial, Helvetica, sans-serif;

font-size: 10pt;

font-weight: bold;

}



The above delivered code is commented and below is the customized one. You can use more alterations according to your choice.