Some good questions and answers on PS

user13421260

PS Dinosaur

While the answers to the questions are great in the perfect world, and probably the most appropriate and correct solutions, they are not always what takes place in the real world.

An example of this would be this one:

A customer wants to apply only a critical fix to resolve an application error that is halting production. The company is three months behind in applying all the posted patches and fixes and there are numerous prerequisites to applying each fix. How can you guarantee that a prerequisite will NOT be missed?
a) Apply the patches only for modules that the client uses
b) Apply the latest PeopleSoft patch only
c) Upgrade or install to the most current PeopleTools release
d) Apply the patches for licensed modules only
e) Apply all applicable PeopleSoft service packs

Typically when there is a critical fix and the solution is available in one of the posted patches, the client does not have the time or bandwith to be able to apply all patches and test all of them.  Instead we locate the particular fix that will solve our current issue and then we one-off it, testing only that fix and then applying it to production.  Then, when we have scheduled maintenance we can properly schedule time and resources to apply all patches/fixes. 

GordonB-Oracle

While the answers to the questions are great in the perfect world, and probably the most appropriate and correct solutions, they are not always what takes place in the real world.

An example of this would be this one:

A customer wants to apply only a critical fix to resolve an application error that is halting production. The company is three months behind in applying all the posted patches and fixes and there are numerous prerequisites to applying each fix. How can you guarantee that a prerequisite will NOT be missed?
a) Apply the patches only for modules that the client uses
b) Apply the latest PeopleSoft patch only
c) Upgrade or install to the most current PeopleTools release
d) Apply the patches for licensed modules only
e) Apply all applicable PeopleSoft service packs

Typically when there is a critical fix and the solution is available in one of the posted patches, the client does not have the time or bandwith to be able to apply all patches and test all of them.  Instead we locate the particular fix that will solve our current issue and then we one-off it, testing only that fix and then applying it to production.  Then, when we have scheduled maintenance we can properly schedule time and resources to apply all patches/fixes. 

There is a change in recommendations for PT 8.53 and 9.2 applications using PeopleSoft Update Manager (PUM):
According to PeopleSoft recommendations, you apply a newly acquired Application Designer Project from an update or a fix into which database?
a) Application update
b) Development
c) Demo
d) Production

PUM is designed to first apply to a development database.  This is because the initial pass includes compares against customizations.  If you use initial pass for demo, you won't get any differences due to customizations and will not be able to incorporate them into a newly generated change package for the next environment.  This saves a step in the apply process in order to reduce total time to apply maintenance.

Regards,

GordonB - Oracle

Vinod Varma Kakarlapudi

Thank you for the document and some more just for information. 

1. To Group Radio buttons they must be adjacent fields on the Order tab
of the page

2.A Long Character field cannot be a Key field in a Record

3.Peoplesoft recommends using prompts in place of drop-down list boxes
in grids for better performance.

4.We cannot insert Radio Button into Grid.

5. We cannot use selected function for a rowset in secondary page grid even though we have row selection indicator in prperties.