Release Notes for Laserfiche Cloud 2020.4.1

January 13, 2021 | KB: 1014236
Laserfiche Cloud

Summary

This article documents new features and changes in Laserfiche Cloud 2020.4.1, released on November 5, 2020.

Laserfiche Bots

  • The bot local tool and recorder installation process has also been updated to use a new installer that guides you through the installation process.

Remote Agents

  • The remote agent worker installation and registration process has been improved. A new installer allows you to install multiple workers, and a configuration utility guides you through the registration process. You can install three process automation workers and one bot worker per machine

Data Management

  • Data in a lookup table can now be completely replaced utilizing the new Replace Lookup Table Data activity in a workflow.

Business Processes

  • Invoking business processes with multi-value tokens now sends all values to a table/collection instead of just the first (276836)

    Note: Republish the business process to address the issue.

Known Issues

  • Laserfiche Bots do not work on applications that run as chromium processes. (154214)
  • Only one user per machine can open the Laserfiche Bot local tool. (174307)
  • The Invoke Bot activity fails with error: "The requested plug-in could not be run by the remote agent" when multiple remote agent workers with the bot plugin are registered on the same machine. (195733)
  • Plain text with the format "%(value)" entered in a input field will be regarded as a token. If you need to use this format as plain text, use "%%(value)."
  • If a bot queue is deleted, all remaining bot instances in that queue will not be run. If a new bot queue is added, these instances will not appear in the new queue and they will not be run. These bot instances must be re-invoked in order to run in the new queue. (249732)
  • If a remote agent worker has multiple queues assigned to it, the tasks will still only be run one at a time. This makes it easier to queue up too many tasks without realizing it, causing tasks to sit in queues for more than 24 hours and time out. When a task times out, the associated bot instance will be terminated. (259186)