ormuz
Home/Orchestration/Nodes Core/Get payment allocations
HelperStable

Get payment allocations

Charge les allocations of the payment or document à partir d’un objet plateforme déjà présent dans le processus.

payment or commercial document
Get payment allocations
Business relationship
payment allocations

Vue d’ensemble

get_payment_allocations suit une relation canonique Ormuz au lieu de demander au designer de transporter ou reconstruire des identifiants techniques entre objets.

Exemple

Le processus possède un payment or commercial document et doit travailler sur ses payment allocations. Le node résout la relation à partir de l’objet source et retourne des objets plateforme directement utilisables.

Parameters 3

resourceRequisPayment
Objet payment or commercial document dont le node doit résoudre les relations. Le type doit être payment, psp_payment, supplier_payment, invoice, supplier_invoice, order, or purchase_order; credit notes are recognized automatically.
statusOptionnelenum
Optional filter on the business status of returned resources.
limitOptionnelinteger
Maximum number of resources returned by this read. Use has_more to determine whether additional results exist.

Outputs 3

payment_allocationsPayment allocation[]
Payment allocations actuellement reliés à la source selon les filtres configurés.
countinteger
Nombre de payment allocations présents dans cette sortie.
has_moreboolean
Indique si d’autres payment allocations existent au-delà de la page retournée.

Behavior

Results are sorted newest first, with stable ordering for identical dates. Default limit is 20 and maximum is 100. An allocation covering several documents is returned in full, with all its lines, exactly once.

Validate the source

Le node exige un payment or commercial document adressable avec un ID. Les sources supportées sont payment, psp_payment, supplier_payment, invoice, supplier_invoice, order, or purchase_order; credit notes are recognized automatically.

Resolve the relationship

Ormuz recherche les payment allocations liés selon la relation métier et les filtres configurés.

Expose the results

Les payment allocations deviennent disponibles pour les bindings en aval, with has_more when the read is intentionally bounded.

Limits and responsibilities

  • The node neither creates nor modifies linked resources; it reads an existing relationship.
  • An empty collection is a valid result when the relationship currently contains no object.
  • The read is bounded by limit; when has_more is true, this output does not represent exhaustive history.