Released: Oct 7, 2021

v5.0.680 中的更新

特性

• Added Embedded Data Store action for easy storage and querying of data using the embedded document database.
• Added Embedded Files Store action for saving and retrieving files using the embedded document database.
• Added option to include numeric tokens in the Tokenize action.
• When %field% replacements are performed, the replaced value will be Json escaped it is is being replaced inside Json text (unless the replaced value is already Json).
• The Move Incoming Message action will now with Office 365, IMAP or Gmail message sources, allowing you to conditionally move an incoming message to a different folder on the source email account.
• Added Convert: JSON To CSV option to the Set Variable action.
• The default Automation Logging Level can now be set server-wide using the Server Settings. This can be overridden in an Automation using the Set Logging Level action.

修補程式

• Fixed issue with Office 365 Message Reader not moving processed files where more than 1 message was read in a batch.
• Fixed issue with Extract Field action not saving default value option in studio.
• Fixed issue with Create Json action where string values were sometimes not escaped correctly.
• Fixed issue with Exchange Web Services message source not using the configured proxy server settings.
• Fixed issue with Process Attachments action. If Rename Saved Files To was used without specifying a file extension, the saved file would not contain an extension.
• Fixed issue with Tokenize action returning blank value where Unique tokens option not enabled and text contained non-unique tokens.
• Fixed issue with Studio Send Message option - when debugging Automations a send message could cause the Automation to exit prematurely because the Studio updates the Automation during execution.
• Fixed issue with Studio: Dragging an action to move it in the Automation action list would sometimes not drag to the correct place causing the line numbers to show incorrectly until the Automation was saved & reloaded.
• CRM Actions will now use a proxy server if one is configured in the ThinkAutomation server settings.