Official |[File Operation] Check File/Directory Exists

Operation name

Check File/Directory Exists

Function overview

Determines whether a file or directory exists.

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.

Required settings

Item name	Required/Optional	Use of variables	Description	Remarks
Target path	Required	Available	Enter a path to verify the existence of a file or directory. The Browse button launches a file chooser that allows you to select a file.	Note Specify an absolute path of HULFT Square Storage for the file path. With the exception of the path separator "/", the Restricted characters of HULFT Square Storage can't be used.

Item name

Required/Optional

Use of variables

Description

Remarks

Target path

Required

Available

Enter a path to verify the existence of a file or directory.

The Browse button launches a file chooser that allows you to select a file.

Note

Specify an absolute path of HULFT Square Storage for the file path.
With the exception of the path separator "/", the Restricted characters of HULFT Square Storage can't be used.

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

None.

Mass data processing

Mass data processing isn't supported.

Parallel Stream Processing

PSP isn't supported.

Available component variables

Variable name	Description	Remarks
success	The result of the operation is stored.	The default value is null. When succeeded, "true" is stored. When failed, "false" is stored.
exist	The presence or absence of the specified file or directory is stored.	The default value is null. When the specified file or directory exists, "true" is stored. When it doesn't exist, "false" is stored.
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 File Operation connector