Oracle Fusion AI Agent :: Publishing a Document Tool in AI Agent Studio (Post 26B)

  Document Lifecycle

The standard document lifecycle is:

Draft → Ready to Publish → Process Agent Documents → Published


⚙️ Behavior Change After 26B

 Before 26B

· Upload a file

· Set status to Ready to Publish

· Manually run ESS Job: Process Agent Documents

· Status updates to Published


 After 26B (New Flow – Automatic Publishing)

The ESS job is no longer required. Publishing is now handled automatically.

  Step-by-Step Process

1. Upload File

2. Click Save as Draft

3. Close the Tool

4. Re-open the tool

5. Change status to Ready to Publish

6. Close the Tool again

7. Wait a few minutes

8. Re-open the tool →  Status will be Published


⚙️ What Happens Behind the Scenes

Once marked as Ready to Publish, the platform automatically:

· Uploads documents

· Parses and chunks the content

· Generates vector embeddings

· Stores embeddings in the Fusion tenant vector database

· Makes the document searchable by the AI agent at runtime


  Required RAG Permissions (For Custom Roles)

To fully manage the RAG document lifecycle, ensure the custom role has the following permissions:

Operation

Permission Group

Read RAG resource

oraCommonFusionAISecurityAuthorization_read_Rag_OraResource

Create RAG resource

oraCommonFusionAISecurityAuthorization_create_Rag_OraResource

Update RAG resource

oraCommonFusionAISecurityAuthorization_update_Rag_OraResource

Delete RAG resource

oraCommonFusionAISecurityAuthorization_delete_Rag_OraResource


 

Comments

Popular posts from this blog

Oracle Fusion HCM - Enhancements to Summary of Changes and History Sections in Redwood Workforce Structures Pages

Query to get Salary Change details in Fusion HCM

πŸ€– Benefits Analyst: Oracle’s AI Assistant for Employee Benefits Clarity