Oracle Fusion AI Agent Studio Foundations

Get to know where agents are designed. You tour the studio’s Fusion-native design and built-in features, and learn how its parts relate to the applications around it.

• Why the studio is Fusion-native
• The main components and where to find them
• Built-in features an agent can use
• How a request moves through the studio
• Where the studio sits among Fusion applications

You build An annotated map of the studio’s components and what each is for.

An agent needs to know the business it works in. You learn how business objects hold the data, how roles decide access, how workflows move work along, and how enterprise structures shape what each person may see.

• Business objects and the data they hold
• Roles and what they allow
• Workflows in Fusion applications
• Enterprise structures and their effect on access
• Why an agent must respect all four

You build A table that links one Fusion process to its objects, roles, workflow and structure.

Every agent combines a few parts. You look at topics, prompts, tools and workflow steps, and at how together they turn a request into a result.

• Topics and what they route
• Prompts and instructions
• Tools and what they do
• Workflow steps and their order
• Following one request through an agent

You build A diagram of one agent showing how its parts handle a sample request.

Tools decide what an agent can do. You learn the five tool types, which are document, business object, external REST, deep link and email, and match each to the kind of job it handles best.

• Document tools for reading and searching content
• Business object tools for Fusion data
• External REST tools for other systems
• Deep links that open the right page
• Email tools for notifying people
• Choosing one tool for a given task

You build A tool choice, with reasons, for five common requests.

Some actions need a person to say yes. You learn which actions should wait for approval, where in a flow to place a checkpoint, and how to make the request clear enough to approve quickly.

• Actions that need a person’s confirmation
• Placing an approval checkpoint in a flow
• Writing a clear approval request
• What happens when a request is declined
• Balancing speed and control

You build An approval checkpoint design for an agent that changes data.

An agent is only useful if it works well. You use the studio’s built-in testing tools to run sample requests, judge the quality of the answers and read what the results tell you.

• Writing test requests from real needs
• Running tests with the built-in tools
• Judging answer quality
• Reading results and spotting weak areas
• Improving the agent and testing again

You build A test plan and results summary for one agent.

See how the same ideas apply across Fusion. Through worked examples in HCM, ERP, SCM and CX, you learn to recognize the patterns of question, data, tool and approval that repeat from one area to the next.

• A worked example in HCM
• A worked example in ERP
• A worked example in SCM
• A worked example in CX
• Patterns shared across all four areas

You build A comparison of four examples that shows what each has in common.

Take one business need and design an agent for it. You choose the objects, tools and approvals, set the roles, and plan how to test it, explaining each choice.

• Choosing a business need
• Selecting objects, tools and approvals
• Setting roles and access
• Planning tests and success measures
• Explaining the design to a colleague

You build A complete design for one agent, from request to approval to test plan.