Skip to content

FEATURE SPEC

Questions or comments?

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

Automated Policy-Based Approvals (EC Integration)

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 #392, titled "[Feature] Automated Policy-Based Approvals (EC Integration)":

Summary

Explore the servicenow auto-approval based on policy feature

Acceptance Criteria

--

Expected Business Value

--

Additional Context

No response

Matching PRD Content

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

Priority: Medium — Policy-as-Code Differentiation Direction: Novaworks Policy Engine → EC Approval Hub Deployment Target: Mid-Market (initial); Enterprise (follow-on)

Why we're building it (company): ServiceNow recently released automated policy-based approval capability in EC. This is a direct touchpoint for Novaworks' core differentiation: Policy-as-Code. Testing automated approval routing based on Novaworks policy rules demonstrates that Novaworks can enforce policy decisions at the approval layer — not just recommend them.

Why it matters (customer): Low-risk, policy-compliant requests get auto-approved without manager interruption. Policy violations surface immediately at the approval stage with a cited rule — not after the fact.

What it does: - Novaworks Policy Engine evaluates approval requests against configured policy rules before routing to Approval Hub - Requests meeting auto-approval criteria are resolved by Novaworks and logged — not queued for human review - Requests failing policy checks are routed to human approvers with a policy citation attached - Audit trail written to Novaworks (and optionally synced to HRSD) for every auto-approved transaction

NOTE: This feature depends on F-04a being stable. It should not be prioritized ahead of F-04a. The newly released ServiceNow capability needs to be assessed for compatibility with external policy engines before committing to this feature.

  • approval-hub-integration (F-04a, #391): per the PRD note above, this Feature depends on F-04a being stable and should not be prioritized ahead of it.

Sources

  • GitHub issue #392
  • ../reference/sn-integration-v1.md, F-04b