Reviewing PeopleTools Functionality

PeopleSoft Online Help provides details about the current PeopleSoft PeopleTools functionality. There are many new features delivered in the new release that you may want to use. You should now review the PeopleSoft Online Help and the PeopleTools Deployment Packages Installation guide for your new release to configure your environment properly. This may include, but is not limited to, configuring and starting a process scheduler and a report server, and reviewing portal settings.

See PeopleTools on the Oracle Help Center, https://docs.oracle.com/en/applications/peoplesoft/peopletools/index.html

See the PeopleTools Deployment Packages Installation guide for your new release.

To review the PeopleSoft PeopleTools New Feature Overview, go to My Oracle Support and search for the PeopleSoft PeopleTools New Feature Overview for your new release.

You should review the following considerations:

  • If you applied a PeopleSoft PeopleTools patch as part of the upgrade, review the patch's README file, especially anything documented in the Patch Notes or Additional Considerations sections. All of the steps included in the PeopleTools Patch Change Package were covered as part of applying the PeopleTools Upgrade Change Package. The scripts run in the patch deliver data in an incremental fashion versus the composite scripts used in the upgrade, but any database changes delivered in the patch were also included in the upgrade.

  • Oracle has updated the themes that define the look of the user interface.

    Various user interface options were delivered with your current PeopleSoft release.

    The following table lists the theme or style available for each PeopleSoft release:

    Theme Name Release

    Classic (deprecated as of PeopleTools 8.50)

    PeopleSoft 8.4 applications and pre-8.50 PeopleTools system databases

    Light blue (deprecated as of PeopleTools 8.50)

    NA

    Dark blue

    PeopleSoft 8.8, 8.9, and 9.0 applications and 8.51 or later PeopleTools system databases

    SWAN

    PeopleSoft 9.1 applications

    Tangerine, Tangerine_ALT, and Fluid

    PeopleSoft 9.2 applications

    Your style settings were retained during the upgrade, but your theme may have been updated.

    See the product documentation for PeopleTools: Portal Technology for your new release for more information about using PeopleTools branding features.

  • Review your PeopleSoft Portal settings, as the values may have changed during the upgrade.

    See the product documentation for PeopleTools: Portal Technology for your new release for more information about understanding changes in portal configuration settings.

  • As of PeopleTools 8.54, partitioning is supported on Oracle platforms. The upgrade process preserved partitioning on existing tables and indexes. Table partitioning information is stored in PTTBLPARTDDL and index partitioning information is stored in PTIDXPARTDDL. You can query these records to find the Oracle-delivered partitioning recommendations, if any. Review the delivered application partitioning recommendations, make any necessary changes for your specific environment, and then apply the changes to your environment.

    See the product documentation for PeopleTools: Data Management, Maintaining Partition Definitions for more information about partitioning on Oracle platforms.

  • As of PeopleTools 8.55, if you are an Oracle database customer, the set of privileges given to the access ID has been refined even further. If you are upgrading from PeopleSoft PeopleTools 8.54 or earlier, restrict the access ID privileges after completing the final pass of the upgrade.

    See the PeopleSoft 9.2 Application Installation guide for your new release, appendix “Synchronizing the ACCESSID User.”

  • As of PeopleTools 8.55, SAP Crystal Reports and Business Objects Enterprise (BOE) are no longer supported. Crystal Reports and BOE will not work on any environments that are running on PeopleSoft PeopleTools 8.55. Review Tech Update: Oracle Retires Support for Crystal Reports (Article ID KB418566) for more information.

  • As of PeopleTools 8.55, the Namespace Alias feature is enhanced and can be used for mapping environment information when cloning or changing middle tier components. If you used this functionality with Elasticsearch or SES, you can continue to use Namespace Alias with OpenSearch in all OpenSearch supported releases. You will need to delete any old Namespace Alias settings for SES and then build initial indexes for OpenSearch. Already indexed data with Elasticsearch 7.10 can be directly used with OpenSearch. If you did not use Namespace Alias in an earlier PeopleTools version, then no action is required for upgrade.

    See the product documentation for PeopleTools: Search Technology, Administering Search Framework for more information about setting Namespace Aliases.

  • As of PeopleTools 8.61, OpenSearch is the only supported search engine; Elasticsearch can no longer be used. For more information on how this affects your specific environment and your upgrade plans, please review Tech Update: Oracle PeopleSoft Transitions to OpenSearch (Article ID KB401747). Additionally, review the PeopleSoft Search and Insights Home Page (Article ID KA592) for complete instructions for implementing or upgrading to the correct version of OpenSearch for your new PeopleTools release.

  • Password security has been enhanced as of PeopleSoft PeopleTools 8.57. In order to take advantage of the AES algorithm, reset the following passwords using PeopleTools 8.57 or later: CONNECT ID password, domain password, Access ID password. This is not applicable to user passwords.

  • If you compared PeopleTools objects during the upgrade, evaluate the compare reports to help identify whether the delivered objects conflict with any of your customizations. The compare report will also show any changes that are delivered in the new PeopleTools release. If you need to re-implement your customizations after the upgrade, you should avoid changing delivered PeopleTools objects because they may be updated in both PeopleTools patches as well as future PeopleTools releases.

  • Beginning with PeopleTools 8.60.13 patch and PeopleTools 8.61 release, PKCS12 files require the use of the AES-256-CBC algorithm, including REN server p12 keystore files, whereas previous releases required PKCS12 files to use the RC2-40-CBC algorithm. If you are using an SSL-enabled REN server, you need to regenerate the REN server p12 keystore file.

    For more details, please refer to E-REN: REN Server With SSL Not Working (Article ID KB392008).

    If you are using certificates from the database for your REN server, please follow these steps:

    1. Shut down your REN server.

    2. Back up and remove the REN server p12 keystore file specified on your REN server definition page.

    3. Start up your REN server, a new keystore file should be generated for you.

    If you are using an external keystore for your REN server, please follow these steps:

    1. Shut down your REN server.

    2. Back up and remove the REN server p12 keystore file specified on your REN server definition page.

    3. Regenerate the REN server keystore file to use the new algorithm.

    4. Start up your REN server.

Properties

Database Orientation Pass Type Products Platforms Languages

Target

All

All

All

All