Editing and Approving Procedures
Auto-captured procedures must be reviewed, edited if necessary, and approved before they become active. The Skill Library provides a structured approval workflow with side-by-side comparison of the auto-captured procedure against the originating conversation.
Approval Workflow
Candidate Captured
Agent completes a successful multi-step task. ProcedureCaptureService creates a candidate with IsApproved = false.
Admin Notified
Platform sends a notification (email or WorkDesk task) to designated procedure reviewers.
Review in Skill Library
Admin opens the candidate in the Approval Queue. They see: the originating conversation, the extracted procedure steps, and any parameter templates.
Edit if Needed
Admin edits step instructions, fixes parameter templates, adjusts the trigger pattern, or adds/removes steps.
Approve or Reject
Click "Approve" → IsApproved = true, procedure becomes active. Click "Reject" → candidate is archived with a rejection reason.
Approval API
// Approve a pending procedure
PATCH /api/octopus/procedures/{id}/approve
Authorization: Bearer {adminToken}
Content-Type: application/json
{
"reviewNote": "Reviewed and confirmed correct tool call sequence"
}
// Reject a pending procedure
PATCH /api/octopus/procedures/{id}/reject
{
"rejectionReason": "Parameter generalization incorrect — contract ref not captured"
}Common Editing Tasks
| Issue Found | Edit Action |
|---|---|
| Trigger pattern too broad — matches wrong requests | Narrow the regex: add anchors, more specific keywords |
| Specific value hardcoded instead of placeholder | Replace with {{parameter_name}} |
| Tool argument JSON invalid | Fix JSON syntax in step editor |
| Step order wrong | Drag-and-drop steps to reorder |
| Missing confirmation step | Add a final step: "Confirm completion to the user" |