FEATURE SPEC

Questions or comments?

Post them as a comment on the tracking issue -- requires a GitHub account with access to this repo.

Approval Hub Integration (Novaworks-Initiated Approvals)

Parent Feature Set: ../concept.md.

Note

Following information is reverse engineered for [AI-DLC]. Review and remove this note before proceeding.

Important

To follow the AI-DLC process, fill this spec with PM assistance first.

GitHub Issue Description (verbatim)

Issue #391, titled "[Feature] Approval Hub Integration (Novaworks-Initiated Approvals)":

Summary

--

Acceptance Criteria

--

Expected Business Value

--

Additional Context

No response

All fields are placeholder — the GitHub issue itself carries no content beyond its title.

Matching PRD Content

Reproduced verbatim from ../reference/sn-integration-v1.md, F-04a.

Priority: High — Mid-Market HCM Direction: Novaworks → EC Approval Hub Deployment Target: Mid-Market (Ateko)

Why we're building it (company): Novaworks agents initiate HR workflows (onboarding, transfers, offboarding) that require human approval. Routing those approvals through EC Approval Hub means Novaworks fits natively into the manager and HR workflow experience customers already use — rather than creating a parallel approval channel.

Why it matters (customer): Managers receive and action Novaworks-initiated approvals directly in their existing Employee Center experience. No separate Novaworks portal login required.

What it does: - Novaworks creates approval requests routed to EC Approval Hub via ServiceNow API - Approval request payload includes Novaworks context (agent, workflow, policy citation) - Approval decision (approved/rejected) returned to Novaworks via callback or polling - Novaworks agent resumes or halts workflow based on approval outcome

Sources

• GitHub issue #391
• ../reference/sn-integration-v1.md, F-04a