Release Note

• In ScriptRunner, improved the password encryption for launch settings files.

  After applying this patch, perform the following procedure 
  to encrypt passwords again for all launch settings files:
  
  1. Open a launch settings file, and replace the value 
     for the password element with a plain text password.

  2. Specify [false] for the encrypt attribute of the password element, 
     or delete the attribute.

  3. Encrypt the password described in step 1 by following 
     the "Password encryption of launch settings file" section in the 
     "ScriptRunner" help page.

  To use the launch settings file in another environment, you must perform 
  the above procedure again.

• In ScriptRunner for Amazon SQS, 
  improved the secret key and password encryption for launch settings files
  and the secret key encryption for property files.

  After applying this patch, perform the following procedure 
  to encrypt passwords and secret keys again for all launch settings files 
  and property files:
  
  1. Open a launch settings file, and replace the values 
     for the secretkey element and password element 
     with a plain text secret key and password.

  2. Specify [false] for the encrypt attributes of the secretkey element 
     and password element, or delete the attributes.

  3. Encrypt the secret key and password described in step 1 by following 
     the "Secret key and password encryption of launch settings file" 
     section in the "ScriptRunner for Amazon SQS" help page.

  4. Open a property file, and replace the value 
     for the AWS_SECRET_KEY key with a plain text secret key.

  5. Specify [false] for the ENCRYPTED key, or delete the ENCRYPTED key.

  6. Encrypt the secret key described in step 4 by following 
     the "Secret key encryption of property file" section 
     in the "ScriptRunner for Amazon SQS" help page.

  To use the launch settings file and the property file in another 
  environment, you must perform the above procedure again.

• In Merge Mapper in Studio for Web, fixed an issue where if you map data to
  a Mapper logic with "three" or more input handlers and then close and
  open the project again, the mapping links to the third and subsequent
  handlers disappear.

• In Studio for Web, fixed an issue where a "Failed to load the component." error may occur when you open a project and the Call Script operation on the script may be lost.

• In Studio for Web, fixed an issue where a script other than the edited script is saved or committed and the version is increased when you perform the following procedure:

  1. Put a script in the edited state (the script is marked with the update icon).
  2. Execute the script.
  3. Save or commit the script after executing it.(*)
  * If the Team development function is enabled, the version is increased when the script is committed to the server, not when it is saved locally.

• When the team development function was enabled in OPC Spider Studio, if you executed "Import..." - "Differential import of projects" from "Control Panel" - "OPC Spider Server Settings", Manage the Local Script History disappeared. This bug is fixed.

• The script processing after firing HULFT Script trigger may be delayed and cause successive delays in firings of other triggers. This bug is fixed.

• In HULFT Script trigger, the temporary mounting method when the trigger fires changed. After applying this version, the mounting information of HULFT Script trigger will not be stored in the repository DB.

• Added Aes128Sha256RsaOaep and Aes256Sha256RsaPss to the security policy in the OPC UA connection function.

• Added OPC UA history reading function.

• Added a function to set the timeout time and number of retries for connection with the OPC server.

• Writing to all tags would fail if there was even one invalid NodeID. This bug is fixed.

• The item list import of the backup function failed. This bug is fixed.

• Even if the key number was duplicated in the value reading process, the process was executed and the wrong value was output. This bug is fixed.

• The error message for duplicate key numbers was always in Japanese regardless of language settings. This bug is fixed.

• Added mcframe SIGNAL CHAIN Adapter.
• Added mcframe SIGNAL CHAIN operation monitoring upload function.

• Changed the component names to "HCL Domino Adapter" from "IBM Domino Adapter".
• Added the HCL Domino 11.0 Adapter. This adapter can be connected to HCL Domino 11.0 and HCL Domino 10.0.

• In SAP Adapter, changed the supported version of SAP Java Connector to 3.1. Only version 3.1 of SAP Java Connector is supported.

• In global resources for SFTP connection of FTP adapter, added a function to connect by using HTTP Proxy server. This function is displayed when you select [SFTP] in [Security type] of the [Secure FTP settings] tab.

  <Property name>
  　[Use the HTTP proxy server] in the [Secure FTP settings] tab
  <Value description>
  　Checked : Use the HTTP Proxy server.
  　Not Checked : Do not use the HTTP Proxy server.
  <Default value>
  　Not Checked
  <Property name>
  　[HTTP proxy host] in the [Secure FTP settings] tab
  <Value description>
  　Enter the host address of the HTTP Proxy server.
  <Property name>
  　[HTTP proxy port] in [Secure FTP settings] tab
  <Value description>
  　Enter the port number of the HTTP Proxy server.
  * The user authentication for the Proxy server is not supported.

• Added the PostgreSQL 12 Adapter. This adapter can be connected to PostgreSQL 12.
• PostgreSQL 12 is supported as a repository DB.