ImportResponder (_data-Responder)

The ImportResponder (_data-Responder) performs an Import into Lobster Data Platform / Orchestration, which can create, modify, or delete entities, or trigger events (see Custom action event).

When creating the response path, the category Custom class must be selected so that the ImportResponder (_data-Responder) is selectable under Class:

images/download/attachments/62853878/image2020-11-4_14-2-48-version-1-modificationdate-1604670767397-api-v2.png

The content for the response path must be an XML structure for the core:Import object (see Single import) or core:BatchImport (see Batch import), which defines the Import to be executed.

As Additional parameters, login data for Lobster Data Platform / Orchestration must be provided as a base LobsterDataLoginRequest.

The expected XML structure of a LobsterDataLoginRequest may refer to profile variables in the @VARIABLENNAME@ format. It can also be taken from a variable as a whole, e.g. if its value is to be defined in mapping by Lobster_pro: Create Login Request (_data function) or transferred from a calling profile.

In addition, instead of direct text input, a a configuration file can be referenced, which must then contain the LobsterDataLoginRequest structure.

NOTE◄ it is not possible to refer to profile variables within the configuration file.

Example

The following base LobsterDataLoginRequest combines static assignments for the user name (userName="edi") and the role (selectedRole=2) with a dynamic assignment for the company (selectedCompany) whose ID is provided via a profile variable (var__Company_id).

Example for a login request
 <base:LobsterDataLoginRequest xmlns:base='SCM.BASE' userName="edi" selectedRole="2" selectedCompany="@var__Company_id@" skipCheckCombination="true" />

The option skipCheckCombination ensures here that the Import is executed even if the dynamically assigned company is not explicitly assigned to the Users account "edi".