Official |[HULFT Transfer App]Get Send Result

Operation name

Get Send Result

Function overview

Obtains the send results.

This operation is for HULFT Transfer Application. Use this operation in combination with Send Files - Dynamic.

The result is obtained from the send log based on the specified transfer name and execution ID (transfer ID). The result can't be obtained before or while the file is being sent.

Properties

= Remarks =

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.

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

<?xml version="1.0"?>
<send_file>
  <file_id>transfer name</file_id>
  <execution_id>execution ID</execution_id>
</send_file>

Element name	Required/Optional	Description
send_file	-
file_id	Required	Enter the transfer name of the file whose send result you intend to obtain.
execution_id	Required	Enter the execution ID.

Output schema

<?xml version="1.0"?>
<send_file>
  <status_code>status code</status_code>
</send_file>

Element name	Description	Remarks
send_file
status_code	Outputs the status code of the send result. The status code format is 000000-00000 (six digits - five digits).	Outputs null if the send result isn't found. For details on status codes, refer to How to look up the error code.

Element name

Description

Remarks

send_file

status_code

Outputs the status code of the send result.

The status code format is 000000-00000 (six digits - five digits).

Outputs null if the send result isn't found.

For details on status codes, refer to How to look up the error code.

Transaction

Transaction isn't supported.

Parallel Stream Processing

PSP isn't supported.

Available component variables

Component variable name	Description	Remarks
message_category	When an error occurs, the category of the message code corresponding to the error is stored.	The default value is null.
message_code	When an error occurs, the code of the message code corresponding to the error is stored.	The default value is null.
message_level	When an error occurs, the severity of the message code corresponding to the error is stored.	The default value is null.
error_type	When an error occurs, the error type is stored.	The default value is null. The format of the error type is as shown below. Example: java.io.FileNotFoundException
error_message	When an error occurs, the error message is stored.	The default value is null.
error_trace	When an error occurs, the trace information for the error is stored.	The default value is null.

Message codes, exception messages, and limitations

Connector	Message code	Exception message	Limitations
Messages and limitations of the HULFT connector