Move a pending task to a different approver or group

approverExpr keeps the expression the task was created with, while
approverIds is replaced by what the target resolves to: a group's
members, or the one user id named directly. The move is recorded on
the task as reassignedFrom, reassignedBy, reassignedAt and
reassignReason.

The request and the task must both be PENDING (409). The resolved
set is pruned of the request's initiatedBy (four-eyes) and must not
end up empty (400) or equal to the current set (409); any member of
it may then decide. Any authenticated caller in the tenant may
reassign.

Path Params
uuid
required
Body Params
string
required
length between 1 and 255

The new approver: a group key resolved to its members on
submission, or a user id to name one person without a group,
stored as given, lower-cased and otherwise unvalidated. The task
takes the whole resolved set, minus the request's initiator, and
any member of it may decide.

string
length ≤ 2000
Headers
string
required
^\d+\.\d+\.\d+$

The version of the Quant Flow API the request follows, as major.minor.patch (for example 1.0.0). The request is interpreted, and the response shaped, according to that version.

Responses

Language
Credentials
Bearer
JWT
LoadingLoading…
Response
Click Try It! to start a request and see the response here! Or choose an example:
application/json