PeopleSoft Technical Issues and Resolutions
General PeopleSoft Issues
1) Running Query Statistics: Is there any issue is setting the parameter "Run Query Statistics" on for our current PeopleTools version? I think that this was a setting which was earlier set but has been provided as a configurable option since PeopleTools 8.4.x. Is there any harm in enabling this parameter? Will it cause any locking/performance issues?
Response from PeopleSoft
PeopleSoft recommends that you only use the query statistics feature for the purposes of analysis. Do not leave the query statistics feature enabled on an ongoing basis. When this feature is enabled, you may compromise the performance and the system may have an increased possibility of query timeouts or may return query results with zero values. PeopleSoft also offers this recommendation to users of queries in reports.
Note. By default, the query statistics feature is disabled.
Upgrade Related Issues
Issue: Knowing that all current security related objects permission lists, roles & user profiles will be picked up in the Initial Pass, in this scenario
a) What are the security considerations we should have?
b) What happens to any new user profiles who are added into the system in the interim?(between now & next MTP)
c) What about new/modified roles & permission lists which are migrated/setup in Production? Will they get picked up in the next MTP? or do they have to be retrofit as part of customizations?
Responses were as follows:
a) All the security related issues always go in the INIT pass, as you probably know. In this pass we set all security that later will be added to your new PeopleTools release. That's why we recommend our customers to freeze production.
b) They won't be added, since they do not belong to the new DEMO of your application (which contains all both data and security related after your initial pass). However, we have a solution document for preserving security through the upgrade passes (this can be used as a workaround).
c) Any new or modified roles and permissions should be duplicated in the source of the upgrade pass for them to be carried on into the target. Remember that in your upgrade there will be new permissions list and roles to take into account the new menus and pages in the new version. The roles and permissions list that you add into production may not be applicable in the upgrade.
I had also enquired about the differentiation which had been established in the succeeding passes from the Initial Pass due to which security doesn't get picked up and only gets picked up from the Initial pass. Their response
"In the initial pass, there is a Full Tools Upgrade. In the Test Move Passes, the tools is not upgraded.
All the tools tables are exported via datamover from the final target of the initial upgrade pass , then on each test move pass that export file is imported into the target database on the test move pass. We do this to save time so the tools upgrade does not need to be done again."
With this response, we have couple of options knowing that security (user profiles, roles & permission lists) may change over the several months till Go Live.
1) Setup Security manually
A) This can be done provided the number of user profiles added since the CoP was taken is minimal - less than 10, no security modifications are being made to existing user profiles & we have not been adding roles & permission lists
B) This manual step would add to the Production cutover time lines
C) There is a possibility that by doing it manually, we may miss security changes
D) Manual tracking process for all security changes should be in place for this to work.
2) Conversion Scripts
A) Scripts can be written to pull in the latest security from Prod. These can be tested during all MTPs to ensure that all security did get correctly converted
B) This script would be a quickie during Production cutover & can be included on the Upgrade Assistant template as a custom script
C) Will ensure that all security changes are captured (e.g. accounts for changes in roles pertaining to users)