Changes so far in 7.7.8:

[FEATURE] Client/Server: Cloud->Google Drive support
[FEATURE] Client/Server: HTTP Task->Added SSL/TLS version support
[FEATURE] Client/Server: Email Trigger->Added attachment filter settings
[FEATURE] Client/Server: SMTP->Added SASL mechanism support for controlling DIGEST-MD5 and NTLM for older email servers
[FEATURE] Client/Server: Added Set Job Variable Task
[FEATURE] Client/Server: Cloud Tasks->First beta of OneDrive Tasks
[FEATURE] Client/Server: Remote Execute->Added fallback method for buggy Windows servers
[BUGFIX] Client: Main grid->Fixed issue saving some columns permanently
[BUGFIX] Server: Performance counter Trigger->Fixed possible memory leak
[BUGFIX] Client/Server: Dynamics CRM->Update entity fixed problem displaying attribute values
[BUGFIX] Server: Web Client->Fixed an issue with folder extraction
[BUGFIX] Server: Cloud->Azure->Fixed upload issue
[BUGFIX] Client: Output/Test->Fixed an issue clicking on output urls with blank space in it
[BUGFIX] Server: SSH Task->Fixed an issue that no error was raised upon Connection timeout
[BUGFIX] Client: Connections->Removed duplicate confirmation
[BUGFIX] Client: Archive - Decompress->Fixed an issue decompressing 7z/zip files
[BUGFIX] WebClient: Various fixes and features (AD logon)
[BUGFIX] Server: File Trigger->Fixed problem with not retrying properly after error

Web client files below. Fixes issue in 7.7.6 where files could not be extracted;

1. download and place the 7z file in the installation folder
2. restart the VisualCron service
3. wait a minute and then try to connect via the Web Client

  WebClient.7z (8,085kb) downloaded 85 time(s).

---

New build, changes:

[FEATURE] Client/Server: Email Trigger->Added attachment filter settings
[BUGFIX] Client/Server: Dynamics CRM->Update entity fixed problem displaying attribute values
[BUGFIX] Server: Web Client->Fixed an issue with folder extraction

---

New build, changes:

[BUGFIX] Server: Cloud->Azure->Fixed upload issue
[BUGFIX] Client: Output/Test: Fixed an issue clicking on output urls with blank space in it

---

New build, changes:

[FEATURE] Client/Server: SMTP->Added SASL mechanism support for controlling DIGEST-MD5 and NTLM for older email servers
[BUGFIX] SSH Task: Fixed an issue that no error was raised upon Connection timeout

---

New build, changes:

[FEATURE] Client/Server: Added Set Job Variable Task
[BUGFIX] Client: Connections->Removed duplicate confirmation

---

New build, changes:

[FEATURE] Client/Server: Cloud Tasks->First beta of OneDrive Tasks
[BUGFIX] Client: Archive - Decompress->Fixed an issue decompressing 7z/zip files
[BUGFIX] WebClient: Various fixes and features (AD logon)

---

Sorry, I meant to post this here instead of the root of "Beta versions". I noticed the post in the General Problem solving forum regarding file triggers not working in version 7.7.8. I did some testing and it appears that the change made in version 7.7.7 regarding file triggers has caused this problem. Fortunately, we are still on version 7.7.4 in our production environment. In our test environment, I tested file triggers using version 7.7.6 and they work as expected. However, in version 7.7.7, they do not work with a file watch type of "Created". Can you please fix this in version 7.7.8?

New build, changes:

[FEATURE] Client/Server: Remote Execute->Added fallback method for buggy Windows servers

---

Sorry, I meant to post this here instead of the root of "Beta versions". I noticed the post in the General Problem solving forum regarding file triggers not working in version 7.7.8. I did some testing and it appears that the change made in version 7.7.7 regarding file triggers has caused this problem. Fortunately, we are still on version 7.7.4 in our production environment. In our test environment, I tested file triggers using version 7.7.6 and they work as expected. However, in version 7.7.7, they do not work with a file watch type of "Created". Can you please fix this in version 7.7.8?

There is no known problem with File Triggers. I recall a post but it was a misunderstanding.

---

Sorry, I meant to post this here instead of the root of "Beta versions". I noticed the post in the General Problem solving forum regarding file triggers not working in version 7.7.8. I did some testing and it appears that the change made in version 7.7.7 regarding file triggers has caused this problem. Fortunately, we are still on version 7.7.4 in our production environment. In our test environment, I tested file triggers using version 7.7.6 and they work as expected. However, in version 7.7.7, they do not work with a file watch type of "Created". Can you please fix this in version 7.7.8?

There is no known problem with File Triggers. I recall a post but it was a misunderstanding.

You can do a very simple test using versions 7.7.6 and versions 7.7.7 or 7.7.8 and see that the triggers work in 7.7.6 and they don't work in 7.7.7 & 7.7.8. I don't think it was a misunderstanding.

Sorry, I meant to post this here instead of the root of "Beta versions". I noticed the post in the General Problem solving forum regarding file triggers not working in version 7.7.8. I did some testing and it appears that the change made in version 7.7.7 regarding file triggers has caused this problem. Fortunately, we are still on version 7.7.4 in our production environment. In our test environment, I tested file triggers using version 7.7.6 and they work as expected. However, in version 7.7.7, they do not work with a file watch type of "Created". Can you please fix this in version 7.7.8?

There is no known problem with File Triggers. I recall a post but it was a misunderstanding.

You can do a very simple test using versions 7.7.6 and versions 7.7.7 or 7.7.8 and see that the triggers work in 7.7.6 and they don't work in 7.7.7 & 7.7.8. I don't think it was a misunderstanding.

We did a test with Created + Filename (when polling is false) with success. Did you try any othe test?

---

Sorry, I meant to post this here instead of the root of "Beta versions". I noticed the post in the General Problem solving forum regarding file triggers not working in version 7.7.8. I did some testing and it appears that the change made in version 7.7.7 regarding file triggers has caused this problem. Fortunately, we are still on version 7.7.4 in our production environment. In our test environment, I tested file triggers using version 7.7.6 and they work as expected. However, in version 7.7.7, they do not work with a file watch type of "Created". Can you please fix this in version 7.7.8?

There is no known problem with File Triggers. I recall a post but it was a misunderstanding.

You can do a very simple test using versions 7.7.6 and versions 7.7.7 or 7.7.8 and see that the triggers work in 7.7.6 and they don't work in 7.7.7 & 7.7.8. I don't think it was a misunderstanding.

I have a set of test jobs that I run after installing a new version of VC. One of the jobs copies 30 PDF files into a folder. There is another job that has a file trigger with a watch type of Created on that folder. That job executes list, rename and delete tasks which result in the folder being empty after the job runs. After I initially installed 7.7.7, the job with the file trigger was no longer triggering. I installed 7.7.6 and the job started triggering again. I just reinstalled 7.7.7 and now the file triggers are working again. Very odd!

We did a test with Created + Filename (when polling is false) with success. Did you try any othe test?

New build, changes:

[BUGFIX] Server: File Trigger->Fixed problem with not retrying properly after error

---

Hi Henrik,

Minor Point, but in Set Job Variable Task you can prompt on Variable Name without Specifying Job and it prompts OK (Active Job). I think this is OK, but perhaps "No Job Selected" could be "Active Job" or "Current Job" or it could default to Current Job Name ?



*But* if you leave the Job as "No Job Selected" and chose a Job variable from the current job and set its value you are allowed to save that task.
Then when you run that Task it will be "Exception in Task: Job not found"



Which is correct, but not as helpful as defaulting to the Active Job, or stopping a save of that task until a Job is specified ?

---

p.s. HTTP Task additions to set Security Protocols nice addition - Thanks

Hi Henrik,

Minor Point, but in Set Job Variable Task you can prompt on Variable Name without Specifying Job and it prompts OK (Active Job). I think this is OK, but perhaps "No Job Selected" could be "Active Job" or "Current Job" or it could default to Current Job Name ?



*But* if you leave the Job as "No Job Selected" and chose a Job variable from the current job and set its value you are allowed to save that task.
Then when you run that Task it will be "Exception in Task: Job not found"



Which is correct, but not as helpful as defaulting to the Active Job, or stopping a save of that task until a Job is specified ?

---

p.s. HTTP Task additions to set Security Protocols nice addition - Thanks

Thanks for the feedback. We did some changes in the final version. However we do not preselect the current Job if it is totally new because, in most cases, the name is not set which might be confusing. Other changes were implemented.

---

Final version of 7.7.8. was released today - thank you for your testing!

---