Create nested entities in data factory

🌐 This document is available in both English and Ukrainian. Use the language toggle in the top right corner to switch between versions.
Table 1. A brief overview of the delegate
Name Description

The business name of the integration extension

Create nested entities in data factory

The internal name of the integration extension

${dataFactoryConnectorNestedCreateDelegate}

The file name in the extension library

dataFactoryConnectorNestedCreateDelegate.json

1. General overview

Create nested entities in data factory —  extension is a delegate for creating multiple entities within a single transaction, which is configured using the developed template of the same name Create nested entities in data factory (dataFactoryConnectorNestedCreateDelegate.json).

Before configuring the template in the Camunda Modeler, make sure that the /element-templates folder contains the dataFactoryConnectorNestedCreateDelegate.json.

  1. To model a service task (Service Task).

    nested entities 1

  2. Click on Open Catalog and select the Create nested entities in data factory template from the list.

    nested entities 2 nested entities 3

  3. Configure the selected template as follows:

  • In the Name field, specify the name of the task. For example, Save data to Data Factory.

  • In the Resource field, specify the resource, i.e. the name of the endpoint to which you need to make a request. For example, person-profile.

    At the API level, the endpoint looks like this: /nested/<resource name>, where <resource name> — is the name of the resource. This means that in the Resource field, you need to specify the value that comes after the last slash (/).

  • In the Payload field, enter the request body — a JSON object with a nested structure of multiple entities that need to be saved to the Data Factory. For example, ${payload}."

    Keep in mind that you need to build this JSON object, i.e. payload, beforehand within the scripting task.

  • In the X-Access-Token field, specify the access token.

    The access token is taken from EITHER the initiator (for example,$initiator().accessToken}), OR the task performer (for example, ${completer('taskDefinitionId').accessToken}).

    nested entities 4

  • In the X-Digital-Signature source field, specify the source of the digital signature.

  • In the X-Digital-Signature-Derived source field, specify the source of the system digital signature.

  • In the Result variable`field, specify the name of the process variable to which the result should be written (by default, it is — `response).

    nested entities 5

For details on how to use and configure the Create nested entities in data factory delegate in a business process, refer to the following link.