Zen ERPInstall

Summary

The node dispatches to a PickingOrderItemUpdate handler for the Material resource and returns the handler's result as the output item's json field.

Inputs

• material_pickingOrderItemUpdate_bodyJson — The JSON body for the picking order item update. Type: collection. Default: {}. Contains an option 'json' (type: json) with a default template showing expected structure: id (integer), pickingOrder (object*), stockCluster (object), productPacking (object*), quantity (number*). Only displayed when operation is /material/pickingOrderItemUpdate.

Output shape

Each item on the main output connector contains a 'json' field with the handler's result. If the handler result is an array, multiple items are emitted; otherwise a single item with the result json is emitted. Error items are emitted when continueOnFail is enabled.

The execute method extracts 'resource' and 'operation' from node parameters per item via getNodeParameter, resolves the handler via getOperationHandler (which uses createHandler from ZenErp_helpers), and returns the result as output item json.

Examples

Example 1: Workflow author configures the Zen ERP node for Material resource and selects PickingOrderItemUpdate. They set the Body parameter to a JSON object matching the declared structure, e.g., { id: 123, pickingOrder: { /*ref */ }, stockCluster: { /*ref */ }, productPacking: { /*ref */ }, quantity: 10 }. The node processes the item and outputs the handler result as the item's json field.

Resource: Material. Operation: PickingOrderItemUpdate. Body JSON must include at minimum the fields documented in the default template (id, pickingOrder, stockCluster, productPacking, quantity). Optional fields may be omitted depending on handler implementation.