Receive Items

Allows to receive items from partners. It must be used with the Send Items task.

Examples

Matching items using the EAN identifier

{
  "name": "exchange-receive-items",
  "taskReferenceName": "receive_items",
  "description": "Receive products",
  "type": "SUB_WORKFLOW",
  "optional": false,
  "inputParameters": {
    "new": "CREATE",
    "exist": "SUGGEST",
    "matching": {
      "first": "EAN"
    },
    "handleDeletedValues" : true
  }
}

Definition

Property	Type	Required	Description
			The name (or type) of the task
			The unique name of the task in your job. It is used to reference this task in the workflow.
			The functional description of this task in your job.
			The type of the task. It must be SUB_WORKFLOW.
			true: the job continues if there is an error on this task. false: the job fails.
			Input parameters of the task. See below

Inputs

Property	Type	Description
	:	Defines the behavior to adopt when collecting suggestions on an item (if it exists in the target table). SUGGEST: Propose an update to the user UPDATE: Automatically applies all suggested updates
		Allows to define reconciliation rules between items that have been published and items present in the target table. The identifier referenced in the first property is used to find a matching item. If the first match is not found then the second, third, fourth and fifth properties are used in this order. If no match is found, the item is considered as new and a new item is created.
		The key of the first identifier to be taken into account when reconciling items
		The key of the second identifier to be taken into account when reconciling items
		The key of the third identifier to be taken into account when reconciling items
		The key of the fourth identifier to be taken into account when reconciling items
		The key of the fifth identifier to be taken into account when reconciling items
	:	Enables you to collect deleted field values from your partner so that you can see and accept fields deletion and update your items A field deletion is published when it is empty and there was a value in the last published suggestion. This feature is in access for a limited number of accounts and will soon be available to all users.
	:	Default: false When set to true, the report generation is skipped and thus the report is not available in the output parameters.

TIP

The handleDeletedValues parameter allows to compare the current version of the item and the last published version of it (the last publication made). So if the current item does not have a value for a field, and the last suggestion contains a value for it, then deletion will be suggested in the suggestion sent to the partner.

Outputs

Property	Type	Description
		Number of items created by this import
		Number of items updated by this import
	:	YES: all items have been created or updated successfully. NO: at least one item has not been created or updated.
		An XML file containing a set of logs related to the execution of the task. This output is not available if the input skipReportGeneration=true.

Limits and additional notes

• Publish and receive up to 10 000 items at a time.
• Publish and receive items on up to 3 screens.