Data permission security can be administered trough tree-based or role-based security. Both methods involve assigning data access to user permission lists.
Tuesday, July 13. 2010
Peoplsoft Modifications: Bolt-ons or delivered objects
Customizations to delivered objects present an on-going maintenance issue.
So, if you customize a delivered piece of code or a page or a component, when you upgrade (or even just apply a bundle that updates that object), it is going to overwrite the object with the newly delivered version, then you are going to have to go back in and reapply your customization.
Bolt-on objects are just brought forward in an upgrade. So for example, the custom page you have in release 8.9 will come through the upgrade looking exactly like it did in the upgraded 9.1 database. So from the perspective of not having to continually reapply your modifications to delivered objects once they get updated in a fix or upgrade, bolt-on objects are easier to maintain.
However -- the catch is that the bolt-on object still has to be tested and may or may not require re-development. It may point to or relate to delivered objects that have changed or disappeared, so from this perspective, there may be effort to redevelop your bolt-on objects too.
To my mind, though, there is less effort involved with custom-added (bolt-ons) because you may or may not have to do anything to your bolt-ons depending on what you find in testing, but with modification you are always advised to take the newest delivered version of a PeopleSoft object, then reapply your modification to it.
So, if you customize a delivered piece of code or a page or a component, when you upgrade (or even just apply a bundle that updates that object), it is going to overwrite the object with the newly delivered version, then you are going to have to go back in and reapply your customization.
Bolt-on objects are just brought forward in an upgrade. So for example, the custom page you have in release 8.9 will come through the upgrade looking exactly like it did in the upgraded 9.1 database. So from the perspective of not having to continually reapply your modifications to delivered objects once they get updated in a fix or upgrade, bolt-on objects are easier to maintain.
However -- the catch is that the bolt-on object still has to be tested and may or may not require re-development. It may point to or relate to delivered objects that have changed or disappeared, so from this perspective, there may be effort to redevelop your bolt-on objects too.
To my mind, though, there is less effort involved with custom-added (bolt-ons) because you may or may not have to do anything to your bolt-ons depending on what you find in testing, but with modification you are always advised to take the newest delivered version of a PeopleSoft object, then reapply your modification to it.
Saturday, July 3. 2010
Didi Mau
Didi Mau is a Vietnamese expression mean "go, go quickly". Didi Mau is pronounced Diddy Mow.
I came across this expression in James Wesley Rawles's (JWR) book "Patriot".
JWR is also the founder and editor of a great blog, The Survival Blog. Check it out here.
I came across this expression in James Wesley Rawles's (JWR) book "Patriot".
JWR is also the founder and editor of a great blog, The Survival Blog. Check it out here.
Thursday, July 1. 2010
Set Trace on PeopleSoft 9.1 Login pages
From the login page type trace=y at the end of the url.
https://diverseyhr.oracleoutsourcing.com/psp/PJDI2J/?cmd=login&languageCd=ENG&trace=y
https://diverseyhr.oracleoutsourcing.com/psp/PJDI2J/?cmd=login&languageCd=ENG&trace=y
Set up CI security for Userid
Open up the userid that you are using to run the Excel to CI.
People Tools > Security > User Profiles
Go to the Roles tab.
Click the View Definition link next to any role.
Click on the Permission Lists tab.
Click on View Definition next to any permission list.
Click on the Component Interfaces tab.
Enter CI_JOB_DATA and click save.
Click edit.
Set each method to full access.
Click edit.
Set each method to full access.
People Tools > Security > User Profiles
Go to the Roles tab.
Click the View Definition link next to any role.
Click on the Permission Lists tab.
Click on View Definition next to any permission list.
Click on the Component Interfaces tab.
Enter CI_JOB_DATA and click save.
Click edit.
Set each method to full access.
Click edit.
Set each method to full access.
(Page 1 of 1, totaling 5 entries)
