FinanceApprovalRule Object
Fields
#
glCompanyId
recordTypes
Record types written before this vocabulary was sealed are dropped on read rather than mapped: only bankTransaction was ever evaluated, so every other stored value was inert, and mapping one onto an enforced type would invent a gate the workspace never had.
minAmount
maxAmount
minChangePercent
Materiality, in percentage points of the figure being restated. A magnitude like the amount band, and an additional condition rather than an alternative: a rule carrying both holds only what clears the band and moves the figure by at least this much. Only record types that restate an earlier figure can answer it, so the save refuses it on the others.
projectId
departmentId
legalEntityId
vendorAccountId
customerId
quarantineReason
Why this stored rule cannot be applied, or null when it can.
A quarantined rule is skipped by the evaluator, and its steps are served empty because serving them would describe a route no document ever takes. Empty steps alone are indistinguishable from a rule that genuinely gates nothing, so the reason travels with them: it is what lets the authoring list say "Quarantined" — and say what to fix — instead of "Active, 0 approval steps".
Usages
#
References
#
- Field getFinanceApprovalRules from Query
- Field createFinanceApprovalRule from Mutation
- Field updateFinanceApprovalRule from Mutation