The Xeelo Import Attachment connector allows you to import new requests, sub-grid items and attachments directly from Integray. For a detailed explanation of how to setup up Xeelo for import, please refer to the Official Xeelo Import tutorial.
The imported data has to be provided as a single line string, where the values are separated by a pipe symbol (|
). These values has to correspond to the import lines defined in your import section. The import process itself can be executed either on foreground (synchronously) or on a background (asynchronously). The foreground type is executed immediately, while the background import is executed as part of the the Import data process
job.
Xeelo prerequisites
To successfully perform an import into Xeelo, you must have:
-
A defined service account in your Xeelo instance with:
- An access token (needed in configuration).
- Defined access to the imported objects.
- Defined user allowed to execute the import.
-
Defined an Import in your Xeelo instance with:
- Import ID (needed in configuration).
- Import sections (needed in configuration).
- Import section lines (needed in configuration).
Quote
Keep in mind that import line of attachment must be type of attachment.
Configurations
Xeelo Connection configuration
Server URL
URL of your running Xeelo site.
Authorization token
The access token for the service account defined on your running Xeelo site.
Xeelo Import configuration
Import ID
The ID of the import defined on your running Xeelo site.
User ID
The user ID under which the import batch will be created.
User ID | User name |
---|---|
0 | System |
1 | Administrator |
2 | ID of a specific user from the User List of your import |
Timeout
Import timeout in seconds. The default value is 100 seconds.
Run on Background
Option | Description |
---|---|
Checked |
The import will be executed as part of the Import data process job. |
Unchecked |
The import will be executed immediately. |
Fail on Errors
Sets the task step run as Failed
if there is at least one failed import record.
Input & Output Schema
Input
Xeelo import input (ver. 1.0.0)
Column | Data type | Allow null | Description |
---|---|---|---|
SectionID | integer | No | ID of internal import section (not the ID of an import!) |
RequestorLogin | string | Yes | User assigned as a requestor in the newly imported request. |
NextUserLogin | string | Yes | User to whom the request will be assigned after the import. |
Data | string | No | Pipe | separated values to import, one record per row. |
NextUserLogin
Do not populate NextUserLogin
if not necessary. This value is used to assign request to a specific user, so for example, if you have an import that updates a request (where import is set), and that request is assigned to multiple users, the import will only assign it to the one user whose user ID is filled in this value. If you do not want to reassign the request, leave it blank.
Data
Make sure that the number of values separated by a pipe exactly corresponds to the number of import lines defined in your import section (in Xeelo).
Output
Xeelo import output (ver. 1.1.0)
Column | Data type | Allow null | Description |
---|---|---|---|
ImportDataBatchID | integer | No | ID of an import data batch. |
State | string | Yes | Detailed error message filled in if the import fails. |
StatusID | integer | Yes | Import status ID (see table below). |
StatusName | string | Yes | Import status name (see table below). |
Import statuses
Status ID | Status name |
---|---|
10 | Created |
20 | Uploading |
25 | Uploaded |
30 | Processing |
31 | Pending |
32 | Pending broker |
80 | Validation failed |
85 | Validation completed |
90 | Process failed |
95 | Process completed |
Release notes
3.1.0
- Added new description and icon.
3.0.3
- Fixed shared nuget package versions.
3.0.2
- Fixed right processing of nullable properties.