HelperStable

Set metadata

Updates free-form metadata on a persisted platform object, then returns the reloaded object after the write.

Objet + metadata

Set metadata

Explicit write

Updated object

Vue d’ensemble

set_metadata is intended for integrator-owned free-form information. Data on which Ormuz behavior depends must remain in a canonical object field, not metadata.

Exemple

Store a campaign reference or system-specific flag on an invoice without modifying the canonical business model.

Parameters 3

resourceRequisCheckout session

Persisted platform object whose metadata must be updated. The node preserves the concrete type of this object in its output.

metadataRequismetadata

Flat common.metadata dictionary to write. Values are limited to scalar types allowed by the Ormuz metadata contract.

strategyRequisenum

merge preserves keys absent from the request and replaces supplied keys; replace replaces the complete map with the supplied one.

Outputs 1

resourceCheckout session

Platform object reloaded after its metadata update.

Behavior

Validate the object and map

The node requires a persisted platform object and applies common common.metadata limits before writing anything.

Apply the strategy

merge merges key by key; replace replaces the complete map.

Relire l’objet

The output is the canonical object reloaded after the write so subsequent nodes use its current state.

Key point Writing protected data into metadata declared normal is a declassification boundary and may require explicit consent.

Limits and responsibilities

Metadata is a flat map: nested objects, arrays, and null are not allowed.
This node is not an extensible business-schema mechanism: use a canonical field when information drives platform behavior.
replace removes keys absent from the new map; use merge for incremental update.