ormuz
Home/Orchestration/Nodes Core/Request multiple approvals
RouteurStable

Request multiple approvals

Requests approval from all eligible contacts and suspends the process until the multi-approver policy is resolved.

Destinataire + contenu
Request multiple approvals
request_multiple_approvals
4 routes

Vue d’ensemble

Requests approval from all eligible contacts and suspends the process until the multi-approver policy is resolved.

Exemple

Require joint approval from two authorized representatives before a sensitive operation.

Decision routes

approved

Approved

The approval policy is satisfied.

Recommended actionContinue on the authorized business path.
rejected

Rejected

The approval request was rejected according to received decisions.

Recommended actionHandle the rejection or request a new decision according to your policy.
expired

Expired

The request was not resolved before its deadline.

Recommended actionRemind or escalate if the business case permits it.
no_eligible_approver

No eligible approver

No contact satisfies the configured role, certification, or conflict criteria.

Recommended actionCorrect targeting or route to administrative review.

Parameters 14

companyRequisCompany
Company whose contacts are considered potential approvers.
requestorOptionnelContact
Contact initiating the request, used to apply the conflict policy with approvers.
role_typesRequisenum[]
Accepted contact roles for resolving eligible approvers.
certification_levelsRequisenum[]
Minimum or accepted certification levels for approvers.
selection_strategyRequisenum
Selection strategy used when multiple contacts meet the criteria.
requestor_conflict_policyOptionnelenum
Rule applied when a requester is also among the eligible approvers.
mailerRequisref(extension_config)
Email configuration utilisé pour cette opération de communication.
approval_titleRequisstring
Approval title utilisé pour cette opération de communication.
email_subjectRequisstring
Subject of the approval email sent to resolved contacts.
email_bodyRequisstring
Approval message body. It may contain the action link generated for the approver.
approval_markdownRequisstring
Business context presented to the approver before the decision.
waiting_markdownOptionnelstring
Message displayed while the human decision is still pending.
expires_inRequisduration
Validity period of the temporary access or approval request.
rejection_reason_requiredRequisboolean
Whether a justification is required when an approver rejects the request.

Outputs 10

statusenum
Current normalized state of the mailing, approval, or verification.
selected_routeenum
Business route selected from the observed state or decision.
decided_atdatetime
Date and time at which the approval request was resolved.
expires_atOptionneldatetime
Expiration date and time of the access or request.
reasonOptionnelstring
Decision reason when provided.
contacted_approversContact[]
Contacts actually requested to approve.
requestor_conflict_detectedboolean
Whether a requester/approver conflict was detected.
excluded_approversContact[]
Eligible contacts excluded by the conflict policy.
approval_requestOptionnelApproval request
Canonical approval request created to track the human decision.
decisionsApproval assignment[]
Set of decisions collected for a multiple approval.

Behavior

The node resolves the approver population, creates a request with multiple assignments, and aggregates their decisions according to the product's multi-approver rule.

Limits and responsibilities

  • Receiving one email response is not enough to satisfy a policy that requires multiple decisions.
  • The composition of the approver population must be stable and auditable.
  • Exclusions caused by requester/approver conflict are exposed separately.