PeopleTools 8.50 Upgrade Issues To Avoid

Posted by: Brent Martin in PeopleTools

Tagged in: Untagged 

Brent Martin


In my recent podcast I interview Karen from Chesapeake Energy about Chesapeake's PeopleTools 8.50 Upgrade. She was generous enough to share their issue list, and so I wanted to pass it along. I hope you find it helpful!

The new auto-complete functionality does not allow you to select using the mouse. You must use your up and down arrows and the ‘Enter’ key.

* Oracle supposedly has this fixed in 8.50.05.

External URLs – No longer work the same way they did before. Previously, URLs on content references that contained escape sequences would function correctly, but now PS replaces the “%” in the escape sequence with another escape sequence, “%” which breaks the URL. To work around, it was necessary to replace the escape sequence with the value it replaced (e.g. replacing with an actual space character).

ViewURL and ViewContentURL Functions – Similar (and likely related) to issue 1, the PeopleCode functions used for transferring a user to a specific URL no longer work as they previously did. The issue does not seem to be related to escape sequences in the URLs, but rather with how PS is transferring the user. To work around, we instead transfer the user to an iScript which uses the Response class method RedirectURL to do the transferring, which behaves as expected.

Old-style Outer-joins in PS Query – Because PS query has been modified to utilize ANSI standard inner joins for row-level security (and perhaps some “standard” joins as well), any queries against records for which row-level security was implemented that also used old-style outer-joins (with the “(+)” indicator) failed because any select statement cannot contain both styles at the same level of the query. To work around, we have been fixing queries with the problem on a case-by-case basis. In some cases, the query can simply be re-written using an ANSI standard outer-join, but in others (such as queries with multiple outer-joins), this either cannot be done or is impractical to do because of the fact that PS Query only allows outer-joins against the last record in the query. In these cases, views have been created that handle the outer-joining themselves.

* Oracle targeting tools 8.51 for fix on this issue

PS Query Prompts – Prompts with prompt table edits do not function correctly when ran by clicking one of the direct links (“HTML”, “Excel”, etc.) in the Query Manager or Query Viewer search results. When the magnifying glass for the prompt is clicked and the user enters Advanced search mode or chooses an alternate search key for their search, the search results table in the modal prompt window gets garbled and is unreadable. To work around, users have been prompted to use Query Manager, click “Edit” on the query and go to the “Run” table instead. The prompts function correctly using this method. For users who previously only had Query Viewer access, the same workaround is possible by giving them Query Manager access, but only granting access to the Search and Run pages in that component.

* Oracle targeting tools 8.50.08 for fix on this issue

XMLDoc-based XML Publisher Reports – On a small percentage of existing XMLDoc-based XML Publisher reports, the Report Definition became inaccessible after the Tools upgrade (user would receive a hard error trying to open it). Case was opened with Oracle and they provided a workaround that involves creating a schema for the Data Source associated with the Report Definition. They utilized Visual Studio to create the schema based on the sample XML. I tried creating a schema myself, and although it was valid for the sample XML, that did not fix the problem, so apparently reports that have this problem are “finicky” about the schema they need. They have been unable to give me a reason as to why this is a problem on some reports but not others, or why my hand-made, valid schema did not work.

Recurrences – Processes that were scheduled to run on a recurrence prior to the upgrade began having problems after the upgrade. In most cases, none of them had any “PS_CDM%” table entries created when they ran and no temporary directories were created for content to be written to while the process ran (prior to posting to report repository). Many processes look to PS_CDM_LIST specifically to obtain this temporary directory location stored in the PRCSOUTPUTDIR field, and thus failed when trying to write files to a non-existent, undefined location. Even those that didn’t would get stuck in a “Posting” status after running to success because the content to be posted did not exist. Cancelling current recurrences and rescheduling seemed to remedy the issue.

DeleteAttachment Function No Longer Idiot-Proof – We have 2 applications (employment agreements and severance agreements) that allow users to attach documentation that is subsequently stored in a database table. The user has the option to delete this documentation, and to do so we use the DeleteAttachement function. Prior to the upgrade, we had unknowingly appended an “S” to the end of the record name passed to this function (e.g. “CK_EA_EE_UPLOADS” when the record is actually “CK_EA_EE_UPLOAD”). Prior to the upgrade, the function truncated the record name to the maximum number of characters, which allowed it to work correctly even with our invalid record name. After the upgrade, this was no longer the case so the code had to be fixed.

Deserialization error – Data Integrity Error – This has been occurring on one of our HR application servers almost every time we do a migration. It looks like the object versioning gets mixed up and caching does not refresh correctly at the application server level.

Sometimes the XML commands are displaying instead of the page. Oracle is looking into this but so far has not been able to provide a solution.


Comments (0)Add Comment

Write comment

security code
Write the displayed characters