Send Files
Operation name
Send Files
Function overview
Requests a Send File for multiple files.
This operation is for HULFT Transfer Application.
Properties
For details on use of variables, refer to Variables.
Basic settings
|
Item name |
Required/Optional |
Use of variables |
Description |
Remarks |
|---|---|---|---|---|
|
Name |
Required |
Not available |
Enter a name to use on the script canvas. |
|
Required settings
|
Item name |
Required/Optional |
Use of variables |
Description |
Remarks |
|---|---|---|---|---|
|
Send config list |
Required |
Not available |
Specify the send configurations list. Each send configuration can be operated with the following buttons:
|
|
|
Send config list/Configuration name |
Required |
Not available |
Select a send configuration. |
|
Comment
|
Item name |
Required/Optional |
Use of variables |
Description |
Remarks |
|---|---|---|---|---|
|
Comment |
Optional |
Not available |
You can write a short description of this connector. |
|
Schemas
Input schema
None.
Output schema
<?xml version="1.0"?>
<send_files>
<send_file>
<file_id>transfer name</file_id>
<execution_id>execution ID</execution_id>
</send_file>
</send_files>
|
Element name |
Attribute name |
Description |
Remarks |
|---|---|---|---|
|
send_files |
- |
|
|
|
send_file |
- |
Appears once for every time Send File is executed. |
|
|
file_id |
- |
Outputs the transfer name of the file that was sent. |
|
|
execution_id |
- |
Outputs the unique identifier that is issued for each execution of the send processing. |
Outputs null if the execution of Send File fails. |
Transaction
Transaction isn't supported.
Parallel Stream Processing
PSP isn't supported.
Available component variables
|
Component variable name |
Description |
Remarks |
|---|---|---|
|
count |
The number of times Send File was executed successfully is stored. |
|
|
message_category |
When an error occurs, the category of the message code corresponding to the error is stored. |
|
|
message_code |
When an error occurs, the code of the message code corresponding to the error is stored. |
|
|
message_level |
When an error occurs, the severity of the message code corresponding to the error is stored. |
|
|
error_type |
When an error occurs, the error type is stored. |
|
|
error_message |
When an error occurs, the error message is stored. |
|
|
error_trace |
When an error occurs, the trace information for the error is stored. |
|
Message codes, exception messages, and limitations
|
Connector |
Message code |
Exception message |
Limitations |
|---|---|---|---|
| Messages and limitations of the HULFT connector |