Released: Jan 19, 2022

v5.0.770 中的更新

特性

• New ThinkAutomation Client Application. This is a stand-alone application that can be optionally installed on network PC's. Users can use the Client to execute Automations by sending messages and dragging/dropping files. Emails & attachments can also be dropped directly from Microsoft Outlook (desktop). See: The ThinkAutomation Client Application for more information. A stand-alone Client installer is available here: Download ThinkAutomation Client Setup (35mb).
• The Studio Send Message form now supports dragging and dropping of emails directly from Microsoft Outlook (desktop).
• You can now restrict non-admin users to specific Solutions. When a user connects using the Studio or Client they will only be able to see Solutions that they have been granted access to. Administrator users have access to all Solutions by default.
• You can now restrict the option of Reprocessing messages to specific users.
• The Select Case action can now use Contains One Of and Contains All Of case operators. These allow a list of values to be checked against on each Case.
• The Contains, Does Not Contain, Contains One Of and Contains All Of conditional operators for If and Select Case blocks now support wildcards. For example: The Contains value of 'P123*' will match on text 'P1234' and 'P123456' etc.

修補程式

• Fixed issue with File Pickup message source when used to read Excel or CSV rows as individual messages. If a column name ended with a dot or contained { } or [ ] characters the auto-created Extract Field action would not extract the value correctly.
• Fixed issue with IMAP message source not reading messages.
• Fixed issue where multiple Message Sources read the same email at the same time causing an error when attachments are saved to the temporary location during Automation execution. During Automation execution attachments are now saved to a unique path.
• Fixed issue with Distributed Setup where the Message Processor or Message Reader services are configured to run on separate computers. The Node Configuration utility was not setting the remote server address in the registry correctly.