Changes so far in 9.4.0:

[FEATURE] Client: Connection Explorer->Added FTP data logging to output according to Connection settings (VSPS-209)
[FEATURE] Client/Server: Database->Added copy database options (VC-1577)
[FEATURE] Client/Server: SQL Task/Trigger/SSISDB: Added better Credential validation (VSPS-219)
[FEATURE] Install: Added auto restart on unhandled crash (VC-1692)
[FEATURE] Install: Export settings Task->Added MFT and SSH keys (VC-1694)
[FEATURE] Client/Server: VMWare Tasks->Added support for vShere 7.0 (VC-1625)
[BUGFIX] Client/Server: MFT->Added some public key validation (VC-1690)
[BUGFIX] Client/Server: MFT->Switched to SSH key selection control with search (VC-1664)
[BUGFIX] Client: Email - Send->Fixed issue using Job Variable in Email - Send Task (VC-1622)
[BUGFIX] Client/Server: Cloud->Added option to ignore certificate errors (VSPS-207)
[BUGFIX] Client: Conditions->Fixed issue selecting a Condition (VC-1620)
[BUGFIX] Client/Server: Informatica->Handled crash refreshing Task settings (VC-1616)
[BUGFIX] Client/Server: Informatica->Username and password was not saved correctly (VC-1637)
[BUGFIX] Server: Informatica->Updated default url and made on-premise url configurable (VC-1633)
[BUGFIX] Server: Email->Get messages->Fixed issue saving email in network share (VC-1591)
[BUGFIX] Server: Variables->Handled problem when null Variable was used (VC-1634)
[BUGFIX] API: Variables->Updated max Variable count in single field to 10.000 (VC-1638)
[BUGFIX] Client: Remote file explorer->Fixed drag and drop issues (VC-1635)
[BUGFIX] Client/Server: Web macro Task->Better handling of unhandled exceptions (VC-1648)
[BUGFIX] Client/Server: Web macro Task->Fixed Task failure if last action was download (VC-1670)
[BUGFIX] Client/Server: Web macro Task->Fixed issue saving type speed (VC-1703)
[BUGFIX] Client/Server: Web macro Task->Fixed click JS detection issue (VC-1711)
[BUGFIX] Server: Event log->Better handling of a crash (VSPS-212)
[BUGFIX] Server: Connections->Fixed issue loading/importing SFTP/SSH Connections with private keys into SSH keys (VSPS-211)
[BUGFIX] Client/Server: Email - Get messages/headers/single message->Fixed issue saving which output columns to use (VC-1653)
[BUGFIX] Client/Server: SSH Connection->Changed default timeout to 0 (infinite) for new Connections as SSH component is aborting the command at the timeout set (VC-1667)
[BUGFIX] Client/Server: MFT->Fixed various crashed related to wrong key settings. Fixed start on import issue. (VC-1658)
[BUGFIX] Client/Server: MFT->Fixed public key logon issue when no key was selected in MFT user (VC-1680)
[BUGFIX] Client/Server: MFT->Fixed flood logging at upload issue (VC-1679)
[BUGFIX] Client: MFT->Fixed SSH console access issue (VC-1663)
[BUGFIX] Client/Server: MFT->Fixed flood logging at upload issue (VC-1679)
[BUGFIX] Server: MFT Trigger->Fixed issues with Login failed/session disconnected events (VC-1666)
[BUGFIX] Client/Server: MFT->Fixed an issue with importing settings (multiple MFT) (VC-1683)
[BUGFIX] Server: Exceptions->Changed general exception handling to better catch unhandled exceptions (VC-1661)
[BUGFIX] Server: SSH Keys->Fixed issue sending SSH Key after import (VSPS-217)
[BUGFIX] Client/Server: SSH Keys->Fixed empty password prompt (VSPS-204)
[BUGFIX] Client: SQL Task->Fixed problem switching from MSSQL Job to Text option (VC-1687)
[BUGFIX] Client: Logging->Reduced logging when Extended debugging is off (VC-1688)
[BUGFIX] Client/Server: SFTP->Fixed an issue with 0 byte file download (VSPS-215)
[BUGFIX] Server: SFTP->Fixed overwrite option (if smaller) issue (VSPS-216)
[BUGFIX] Server: Output->Fixed potential random crash in output reader (Execute/ExecuteHelper) (VC-1689)
[BUGFIX] Client: SNMP Get Bulk->Fixed issue saving SNMP version (VC-1695)
[BUGFIX] Server: Settings->Fixed issue updating Server settings after import (VC-1693)
[BUGFIX] Client: Variables->Fixed issues with Archive Compress Variable (VC-1698)
[BUGFIX] Client: Time exceptions->Fixed Client crash in Job window when lacking permissions to view Time exceptions (VC-1704)
[BUGFIX] Client/Server: Azure->Fixed dll mismatch (Microsoft.IdentityModel.Tokens) (VC-1705)
[BUGFIX] Server: Sync->Fixed an issue with syncing Variables (<string> addition) (VC-1700)
[BUGFIX] WebClient: Handled crash in w3wp.exe on disconnect (VC-1710)

---

Is it possible to get a clarification on what VC-1622 addressed? Was it a recent issue or long-standing? I ask because I want to make sure it doesn't reflect something that might mean I need to hold off on upgrading from 9.3.0 to 9.3.5 and wait for 9.4.0 instead, or at least go through all my email tasks and make sure I'm not affected.

Is it possible to get a clarification on what VC-1622 addressed? Was it a recent issue or long-standing? I ask because I want to make sure it doesn't reflect something that might mean I need to hold off on upgrading from 9.3.0 to 9.3.5 and wait for 9.4.0 instead, or at least go through all my email tasks and make sure I'm not affected.

I'm in the same situation. Is it safe to upgrade to 9.3.5 (now 9.2.5) ?
I have a lot of variables in both header and body of email notifications.

Is it possible to get a clarification on what VC-1622 addressed? Was it a recent issue or long-standing? I ask because I want to make sure it doesn't reflect something that might mean I need to hold off on upgrading from 9.3.0 to 9.3.5 and wait for 9.4.0 instead, or at least go through all my email tasks and make sure I'm not affected.

I'm in the same situation. Is it safe to upgrade to 9.3.5 (now 9.2.5) ?
I have a lot of variables in both header and body of email notifications.

I will point out the entry above specifically says job variables in Email - Send task. Since notifications were changed to be more like tasks under the hood a while back I don't necessarily assume notifications aren't affected, but I suspect that would have been specified, and I am even more certain they wouldn't have specified job variables if other variables had the same problem as well. I am pretty sure I don't have any notifications that use job variables, but I may have a few Email tasks that do, and I have at least one upcoming configuration that might call for them.

Is it possible to get a clarification on what VC-1622 addressed? Was it a recent issue or long-standing? I ask because I want to make sure it doesn't reflect something that might mean I need to hold off on upgrading from 9.3.0 to 9.3.5 and wait for 9.4.0 instead, or at least go through all my email tasks and make sure I'm not affected.

I'm in the same situation. Is it safe to upgrade to 9.3.5 (now 9.2.5) ?
I have a lot of variables in both header and body of email notifications.

I will point out the entry above specifically says job variables in Email - Send task. Since notifications were changed to be more like tasks under the hood a while back I don't necessarily assume notifications aren't affected, but I suspect that would have been specified, and I am even more certain they wouldn't have specified job variables if other variables had the same problem as well. I am pretty sure I don't have any notifications that use job variables, but I may have a few Email tasks that do, and I have at least one upcoming configuration that might call for them.

Yes, correct, this is mainly related to Job Variables but I see now it can affect Task Variables as well. It is only affecting the Client. The problem was that the current Job and Task was not passed to this window so we could not resolves Job/Task Variables.

---

<snip>
Yes, correct, this is mainly related to Job Variables but I see now it can affect Task Variables as well. It is only affecting the Client. The problem was that the current Job and Task was not passed to this window so we could not resolves Job/Task Variables.

Ah, I missed that it was only flagged Client. I'm so used to things like using PrevTask in notifications (where the edit window can't know what it's going to be yet) - and making sure I get what I expected afterward - that I probably wouldn't have noticed if I ever ran into this, then. Thanks for the clarification!

Official 9.4.0 version was released today. Thank you for your feedback and testing!

---