PeopleSoft Assistant

PeopleSoft Assistant is a conversational chat UI built into PeopleSoft Fluid. Instead of hunting through navigation and search pages, users ask in plain language. The Assistant answers with live PeopleSoft data, takes them straight to the right page, or walks them through the task.

Every request runs with the signed-in user’s own PeopleSoft security, so the Assistant can never show more than that user could see on their own.

Who it’s for

• Employees checking balances, pay, benefits, and personal details.
• Managers working through approvals and team information.
• Occasional users who don’t use PeopleSoft often enough to remember where things are.
• Help desks that want fewer “how do I…?” tickets.

What users can ask

• “How many vacation hours do I have left?”
• “Where do I update my direct deposit?”
• “Which of my team’s timesheets are still waiting for approval?”
• “What’s the status of requisition 0000012345?”
• “Show me the open purchase orders for Acme Corporation.”

Two ways in

Chat page

A Fluid page that users open from a tile on their homepage or the NavBar, for open-ended questions, help finding pages, and guided tasks.

Magic Button

An Ask the Assistant action on the fields you choose. It opens the Assistant already knowing the page, the field, and its value, so users can ask “What does this mean?” or “What should I enter here?”

Magic Buttons are field-level related actions, set up under PeopleTools > Portal > Related Content Service, so delivered page definitions stay unchanged. Magic Buttons shows how.

How it works

1. The user asks on the chat page or through a Magic Button. The question goes to the Assistant service, with the user’s access token and any page and field context.

2. The LLM plans the answer. It works out what information it needs, and which of the Assistant’s tools can provide it.

3. PeopleSoft APIs do the work. Each tool calls a REST API built with the Application Services Framework (ASF), with a token for the signed-in user. PeopleSoft checks the user’s permission lists, and the API applies row-level security.

4. The user gets an answer grounded in live data, with links to the relevant PeopleSoft pages. When they want to change something, the Assistant links to the page and says what to enter; the user makes the change there.

Built-in guardrails

• The user’s security, not a super-user’s. The Assistant has no database access and no privileged service account, only the APIs the user is already authorized to use.
• People make every change. The Assistant’s tools only read. Changes are made and saved on PeopleSoft pages, by the user.
• Your choice of LLM. Use a hosted model or one that runs in your own environment.
• Auditable conversations. Every question and API call is logged under the user’s identity.

What you need

• PeopleTools 8.59 or later, for the Application Services Framework.
• An identity provider that PeopleSoft trusts for OAuth 2.0 access tokens, and that supports token exchange.
• An LLM that supports tool calling and streaming, hosted or in your own environment.
• A place to run the Assistant service, close to PeopleSoft.

Set up the Assistant takes you through each step.

Oracle also offers chatbots for PeopleSoft, built on Oracle Digital Assistant with the PeopleSoft Chatbot Integration Framework. The Assistant described here takes a different path: it works with any LLM that supports tool calling, and its tools are your own application services.

Go deeper

How the Assistant worksIts parts, one turn step by step, the tool loop, streaming, and what each part keeps.

PeopleSoft APIs as toolsHow application services and their OpenAPI descriptions become the Assistant's tools.

Acting as the userSign-in, token exchange, PeopleSoft's OAuth 2.0 setup, and what PeopleSoft checks.

Magic ButtonsAdd Ask the Assistant to fields with the Related Content Framework.

Prompts and conversationsThe system prompt, turn context, prompt caching, long conversations, and costs.