Specification limitations

Designer

• No script variable or component icon can have the same name as any other script variable or component icon.

• Changes in the permissions aren't reflected in the project open in Designer. To reflect changes in the permissions, reopen the project.

• When you press the Enter key in the properties dialog, even if any other button or field is selected, the settings are completed and the dialog closes.

• When you try to open the properties dialog of a component by double-clicking and you double-click again before the dialog opens, multiple properties dialogs may be opened.

  If this happens, use the dialog in front to set the properties and close it by clicking Finish. Then, close the remaining dialogs by clicking Cancel.

• When you set a component variable of a component that isn't connected to the process flow to an item in the properties of a component that is connected to the process flow, script compilation fails.

• In the Running script error dialog, which appears when script execution fails, the vertical size of the error detail area does not increase beyond a certain size, even if you enlarge the size of the dialog.

• When a script is run in debug mode, process flows to the end icons of flow operations (such as Loop or Conditional Branch) aren't highlighted.

• If one of the following events occurs, select Initialize layout from the View menu:

  • When you close Designer with the script canvas maximized and then reopen Designer, the frames appear in a closed state.

  • When you maximize the Execution log window or the Error log details window, and then return it to its original size, the layout appears collapsed.

• When you paste data with a newline in a field that can only take a single line, only the data before the newline is pasted.

• In the screen to select a project that appears when you select Open project in the File menu, when filtering with Equals or Not Equals, the column for date and time data sometimes doesn't work as intended. In this case, use filters such as Greater Than, Greater Than or Equals, Less Than, or Less Than or Equals.

Exclusive control

• There is no guarantee of the behavior of the operation when write or other operations for a file are processed in multiple threads.

Project explorer

• When a script is loading, you can't select Properties in the right-click menu.

Execution history

• When Call Script is performed multiple times inside a thread operation, the tree structure in the execution history isn't displayed correctly.

• During the Call Script execution, if the call destination script isn't open in Designer, the processing information of that script doesn't appear in the execution history.

Execution log

• When a value is assigned to a binary script variable, the variable type displayed in the execution log is String. It's not binary.

• When binary data is assigned to a binary script variable, it's displayed in the format "/0101/0110/1" in the execution log and "B@12498b5" in the debug information.

• When scripts like those described below are executed and the number of log records exceeds 10,000, the upper limit for display is reached, and only errors and completion messages are displayed.

  • The log level is set as DEBUG, and a large amount of data is handled during debugging

  • A large volume of processing is required because of loop execution or other reasons

  You can view all the log records in the event log of HULFT Integrate. Use the filter function by specifying hours, minutes, and seconds for Date or specifying error for Log level to narrow down the records to view.

Previewer

• The previewer can read files within 1 MB.

  When a file of 1 MB or more is specified, the first 1 MB is read.

Chooser

• When you use the file chooser to select a directory, the selected directory name is set to the input field of the file name.

Connection resource settings

• The names of connection resources can't be changed in Designer.

  = Reference =

  For details about making changes in connection resources, refer to Connection resources.

Script component

• If a script includes a Call Script operation as a check target of the Monitor Exception operation and the script is stopped during the Call Script operation, the process can't be interrupted.

• If scripts more than the maximum number of simultaneous executions are executed simultaneously, there is no guarantee that the execution of scripts that are waiting will be executed in the order given.

All connectors

• For all the connectors, if no response is returned from the request before 350 seconds have elapsed, even if the response is subsequently returned, the script won’t be able to detect the response and the status may remain as running.

  If a timeout can be specified in the connector's settings, specify a time that is shorter than 350 seconds.

  For the connectors without a timeout setting, you can implement a timeout for the script execution with the Thread operation, the Conditional Branch operation, and the Wait operation.

  For details, refer to the FAQ for HULFT Square (https://support.square.hulft.com/hc/en-us/articles/12512042730388).

  To reference the FAQ, a support agreement is required.

• In table properties such as Column list/Column name of the CSV connector, if the required input items aren't set, the x icon appears only when the field is in the input state.

• When operations are placed newly on the script canvas, the x icon, which indicates an unselected state, may not appear in the list properties of required inputs such as the database connector Table name.

• When you select a component icon for which a connection resource is set that can't connect because of incorrect settings or similar causes, you may not receive a response for some time.

• Microsecond data can be used with a part of connectors.

  Connectors that support microseconds are listed below:

  • DB2 connector

  • Oracle connector

  • PostgreSQL connector

  • SQL Server connector

Connectors that perform file operations

• In the file read operation of connectors that perform file operations, insufficient disk space may occur when large files are read. Even if this occurs, the script execution won't become an error, and the processing continues with the file data missing.

  This problem occurs when you execute a script that exceeds the file size limit that can be handled, such as when you execute multiple file operations simultaneously with a single HULFT Integrate service.

  As of May 2023, the approximate file size that can be handled simultaneously is about 12 GB. For cloud-based connectors, it's about 6 GB.

  Workarounds

  Avoid hitting the upper limit by dividing the files into separate quantities or by shifting the processing timing.

  Applicable connectors related to file operations

  Basic

  • Assertion

  • Compare File

  File

  • CSV

  • Excel

  • Excel(POI)

  • XML

  • Fixed-Length

  • Variable-Length

  • File Operation

  • Filesystem

  Network

  • REST

  • FTP

  Cloud*

  • Amazon S3*

  • Azure BLOB Storage*

  • Google BigQuery*

  • Google Cloud Storage*

  • Google Drive*

  • Google Sheets*

  • Box*

  • SharePoint*

  Cryptography

  • PGP

  *

  :

  For cloud-based connectors, the consumed disk amount may be double the file size that the connector handles.