Oracle PeopleTools 8.63: Key Features, AI, and Security Updates

Listen to article

Oracle PeopleTools 8.63 introduces new capabilities across AI, security, search, and administration. Understanding what changed and how each enhancement aligns with your organization's priorities can help you plan your next steps with confidence.

Key Takeaways

• Oracle made PeopleTools 8.63 generally available on Oracle Cloud Infrastructure on July 29, 2026, with on-premises availability to follow.
• The release's biggest theme is AI readiness: Natural Language Search, Model Context Protocol (MCP) server support, and an AI Assistant inside Application Designer.
• New SAML 2.0 single sign-on and TOTP-based two-factor authentication give organizations more ways to align PeopleSoft with their existing identity strategy.
• Semantic Search and Typo Tolerance improve everyday usability for business users without requiring new training.
• Treat 8.63 as a planning exercise, not just a technical upgrade: map each capability to a real business need before committing resources.

What PeopleTools 8.63 Is, and Why It's Worth Your Attention

PeopleTools is the technology foundation underneath every PeopleSoft application, from HCM to FSCM to Campus Solutions. Oracle released PeopleTools 8.63 on OCI on July 29, 2026, via PeopleSoft Cloud Manager Image 22, with on-premises availability expected to follow.

The release touches eight areas: AI enablement, search, security, user experience, lifecycle management, operations, integration, and deployment. Most organizations won't adopt everything on day one, nor should they. What matters is understanding what changed, who it affects, and where it fits into your roadmap.

Cloud Manager 22 - New Look and Feel

Cloud Manager Automation was used to Upgrade People Tools from 8.62 to 8.63

AI Enablement Is the Headline, but Adoption Is Your Choice

The clearest theme in 8.63 is preparing PeopleSoft for AI-powered work without forcing a single AI vendor or approach.

• Natural Language Search Service interprets natural-language questions and returns secured PeopleSoft Search results through a REST API, so users can ask questions in plain language instead of guessing at search terms.
• Model Context Protocol (MCP) server support gives AI agents a standards-based way to interact with PeopleSoft through delivered and customer-defined APIs. It connects PeopleSoft to the AI platform your organization chooses while preserving PeopleSoft security and user context.
• Application Designer AI Assist adds an LLM-powered chat window inside Application Designer that can explain PeopleCode, suggest improvements, troubleshoot issues, or draft documentation using project metadata and uploaded files as context. It's pluggable, so you choose the LLM that fits your governance, cost, and security requirements.

For CTOs and IT managers: AI Assist can help your existing team work more efficiently, not replace it, orienting new developers or freeing senior developers from documentation work. But you still need to decide which LLM to use and how it aligns with your data governance policies first.

Search Gets Easier for Everyone Else

Everyday business users will feel two changes:

• Semantic Search returns results based on meaning and context, not just exact keyword matches.
• Typo Tolerance forgives minor misspellings instead of returning nothing.

Neither requires end-user training, and both reduce the small daily frustrations that add up to support requests and lost time. This is a practical, low-risk starting point for evaluating 8.63.

Stronger, More Flexible Sign-On

Security teams get two additions that solve different problems.

SAML 2.0 support gives PeopleSoft native single sign-on with identity providers that support the standard, covering both IdP-initiated and SP-initiated sign-on flows, so users can start from an identity portal or a direct PeopleSoft link and still land where they intended. This reduces custom integration work for organizations centralizing identity management.

Two-factor authentication (2FA) via TOTP adds a verification step after primary sign-on using a registered authenticator app. Users manage devices through the My Two-Factor Verifications page; administrators enable it via security policy and web profile configuration. An API also lets you invoke 2FA for specific transactions (e.g., updating direct deposit), so you add friction only where risk justifies it.

Neither feature is mandatory on day one. Both offer more flexibility to align PeopleSoft with your existing identity model.

Less Customization, More Configuration

Two changes matter for anyone managing technical debt: the continued expansion of Page and Field Configurator, and Event Mapping, which introduces logic changes without touching delivered code. Used well, both shrink the customization footprint that complicates future upgrades. Oracle also improved the Kibana and OpenSearch analytics dashboards, with faster-loading visualizations and more responsive filters.

Operations and Lifecycle Management

PeopleTools 8.63 also includes operational upgrades that matter more to your technical team than end users: PeopleSoft Log Analyzer, Customization Groups, webhook support, Middleware DPK Builder, and PeopleTools container images. None will make headlines individually, but together they continue Oracle's effort to make PeopleSoft environments easier to deploy, monitor, and maintain, particularly on OCI.

FAQs

1. Is PeopleTools 8.63 available for on-premises PeopleSoft environments?

At general availability, it's available on OCI through PeopleSoft Cloud Manager Image 22. Oracle has indicated on-premises availability will follow.

2. Do we need to enable AI Assist or Natural Language Search right away?

No. These are optional and can be adopted on your own timeline. Establish your LLM selection and data governance approach before enabling AI Assist or exposing PeopleSoft data through MCP server access.

3. Does SAML 2.0 support replace our existing single sign-on setup?

Not automatically. 8.63 adds the native SAML 2.0 framework and configuration pages, but you still need to integrate it with your specific identity provider.

4. What is Model Context Protocol (MCP) server support, in plain terms?

A standards-based way for AI agents and AI-powered applications to interact with PeopleSoft through delivered and customer-defined APIs, reducing the need to build custom integrations for every AI tool you connect.

5. Where should we start when planning a PeopleTools 8.63 upgrade?

Start with an honest assessment of your current PeopleTools release, customizations, and integrations. Then prioritize the features that address your most important business needs, such as security, search usability, or AI readiness, rather than adopting everything at once.

Conclusion

PeopleTools 8.63 isn't a single decision. It's a collection of independent capabilities, and the right adoption sequence depends on your environment, risk tolerance, and business needs this year. Start with three questions: Where is security exposure highest, and would SAML 2.0 or TOTP address a meaningful gap? Where is search friction costing business users time? And what governance should be in place before any AI capability, including AI Assist or MCP server access, touches production data?

Answering those questions before touching a test environment leads to a more deliberate upgrade plan. We work alongside PeopleSoft teams on exactly this kind of assessment, reviewing your current release, customizations, and integrations, then prioritizing adoption based on business needs rather than the full feature list. If you're evaluating PeopleTools 8.63, contact us to start the conversation.