1 of 6

Policy Agent: UiPath Agentic Automation

TO-BE Architecture for Policy Document Management

2 of 6

Overview of the Agent

  • This Agent handles:
  • - Policy Template Editor via UiPath Apps
  • - Policy Document Generator via UiPath Autopilot
  • - Interacts with SQL DB for data lookup
  • - Stores templates in UiPath Storage Buckets
  • - Sends output via Email

3 of 6

Core Components

  • 1. UiPath Autopilot – Interprets user prompts
  • 2. UiPath Apps – UI for editing templates
  • 3. Policy Agent – Routes logic and invokes processes
  • 4. SQL Database – Source for document fill data
  • 5. UiPath Studio Workflows – Executes core automation logic
  • 6. UiPath Orchestrator – Orchestrates job scheduling and queueing
  • 7. Storage Bucket – Stores and retrieves templates
  • 8. Email Integration – Sends generated documents

4 of 6

Template Editing Process

  • 1. User requests 'edit policy templates'
  • 2. Autopilot sends UiPath App link
  • 3. User searches/selects template
  • 4. Opens and edits file in App
  • 5. Uploads updated file
  • 6. File is stored in the Storage Bucket

5 of 6

Document Generation Process

  • 1. User requests 'generate policy document'
  • 2. Autopilot agent triggers backend logic
  • 3. Agent fetches data from SQL DB
  • 4. Agent retrieves latest template from Storage Bucket
  • 5. Data filled into placeholders using workflow
  • 6. Generated document converted to Word/PDF
  • 7. Document emailed to requester

6 of 6

Optional Enhancements

  • - Version control and rollback for templates
  • - Audit trails for edits and document actions
  • - Support for collaborative editing (e.g., Office 365)
  • - Scheduling document generation (cron-style)