This is documentation for Semarchy xDI 2023.2, which is no longer supported.

For more information, see our Global Support and Maintenance Policy.

File Actions

File actions perform operations in the Runtime engine file system.

Certain actions can provide the list of the files they manipulated:

This list can be stored in a table named IND_SESSION_FILE_OP_LST
1. Provide a SQL Connection to the action or define a Rdbms metadata link on the action
2. A table named IND_SESSION_FILE_OP_LST is automatically created and populated in the corresponding schema.
This list can be used through a bind link
1. Add a bind link to the action
2. Use the columns in the target action with the bind syntax.
  For instance: :{FILE_NAME}:

The following columns are available:

Column Name Description

Column Name	Description
SESS_ID	ID of the Session in which the file operation has been performed. This can be used in conjunction with ${/CORE_SESSION_ID}$ to retrieve the list of files of a specific Session.
SESS_NAME	Name of the Session in which the file operation has been performed.
ACT_ID	ID of the Action which performed the operation. This can be used in conjunction with ${CORE_ACTION_ID}$ to retrieve the list of files of a specific Action.
ACT_NAME	Name of the Action which performed the operation
ACT_ITER	Action iteration number.
FILE_ID	A number corresponding to the position of the file in the operation queue.
FILE_OPERATION	File operation executed. E.g. `Wait'',` Copy'', …
FILE_NAME	The file name.
FILE_DIR	Directory where the file is stored.
FILE_FROM_DIR	Original folder of the file.
FILE_FROM_FILE	Original file.
FILE_TO_DIR	Target directory.
FILE_TO_FILE	Target file.
FILE_OPERATION_DATE	Date when the operation has been performed on the file.
FILE_IS_HIDDEN	Indicates if the file is a hidden file in the file system (1=Yes, 0=No).
FILE_LAST_MODIFIED	Last modification timestamp.
FILE_LAST_MODIFIED_DATE	Last modification date.
FILE_CAN_READ	Indicates if the Runtime can read the file (1=Yes, 0=No).
FILE_CAN_WRITE	Indicates if the Runtime can write the file (1=Yes, 0=No).
FILE_CAN_EXECUTE	Indicates if the Runtime can execute the file (1=Yes, 0=No).
FILE_IS_DIRECTORY	Indicates if the file is a directory (1=Yes, 0=No).
FILE_LENGTH	Size of the file in Bytes.

SESS_ID

ID of the Session in which the file operation has been performed. This can be used in conjunction with ${/CORE_SESSION_ID}$ to retrieve the list of files of a specific Session.

SESS_NAME

Name of the Session in which the file operation has been performed.

ACT_ID

ID of the Action which performed the operation. This can be used in conjunction with ${CORE_ACTION_ID}$ to retrieve the list of files of a specific Action.

ACT_NAME

Name of the Action which performed the operation

ACT_ITER

Action iteration number.

FILE_ID

A number corresponding to the position of the file in the operation queue.

FILE_OPERATION

File operation executed. E.g. Wait'', Copy'', …

FILE_NAME

The file name.

FILE_DIR

Directory where the file is stored.

FILE_FROM_DIR

Original folder of the file.

FILE_FROM_FILE

Original file.

FILE_TO_DIR

Target directory.

FILE_TO_FILE

Target file.

FILE_OPERATION_DATE

Date when the operation has been performed on the file.

FILE_IS_HIDDEN

Indicates if the file is a hidden file in the file system (1=Yes, 0=No).

FILE_LAST_MODIFIED

Last modification timestamp.

FILE_LAST_MODIFIED_DATE

Last modification date.

FILE_CAN_READ

Indicates if the Runtime can read the file (1=Yes, 0=No).

FILE_CAN_WRITE

Indicates if the Runtime can write the file (1=Yes, 0=No).

FILE_CAN_EXECUTE

Indicates if the Runtime can execute the file (1=Yes, 0=No).

FILE_IS_DIRECTORY

Indicates if the file is a directory (1=Yes, 0=No).

FILE_LENGTH

Size of the file in Bytes.

The columns filled depend on the actions and parameters used.