This release contains some major changes in the core to support looping. We have done some regression testing but this version needs more testing and we will release updates to this version in this thread.

Major change is the support for looping. Right now we have an online documentation here:

https://docs.google.com/...zZK4PqZ64s/edit?hl=en_US 

We will update this document constantly. We will create an example video tutorial later. Take a look at this thread here for future updates of this version

Changes in 6.0.0

[FEATURE] Client/Server: Added Loop support for Tasks in Jobs
[FEATURE] Client/Server: Added the .NET code execute Task
[FEATURE] Client/Server: Added the .NET Condition
[FEATURE] Client/Server: Added List files Task
[FEATURE] Client: Some new features in the Variable window. Helps you pick up the Active and PrevTask Variables.
[FEATURE] Client/Server: Added support to base FTP upload on size comparison
[FEATURE] Client/Server: Added support for selecting multiple nodes in the XML Read Task
[FEATURE] Client/Server: Added support for loading a Variable instead of File in XML Read Task
[FEATURE] Client/Server: Added option to "post process" new name with a Variable in File Read Task
[FEATURE] Client: Added Task re-ordering through buttons in the grid (Edit Job->Tasks)
[BUGFIX] Server: Fixed a bug where files were not deleted in the Archive - Compress Task
[BUGFIX] Client: Fixed a crash when opening the web service Task
[BUGFIX] Server: Fixed a problem with VisualCron event deactivation
[BUGFIX] Server: Fixed a Credential problem in the XML Read Task
[BUGFIX] Server: Handled a potential crash when no Connection was specified in SQL Notification
[BUGFIX] API: Fixed a permission problem concerning multiple connections against the same Server (with same Client)
[BUGFIX] API: Fixed a problem where Allow AD logon settings where overwritten when stopping the VisualCron Server
[BUGFIX] Server: Fixed a possible synchronization problem in the core scheduling. Could cause scheduling to fail in some scenarios.
[BUGFIX] Server: Improved database logging performance - Tasks do no longer hang if db (disk performance) is slow
[BUGFIX] Client: Fixed a problem with closing tabs in the “FTP Explorer”
[BUGFIX] Client: Fixed a problem in the “Remote save files dialog”. The dialog could crash in some situations.

Please report any bugs here in this thread.

---

Downloadable exe updated. Please re-download and install. Same "version" but build 22423.

The following changes has been made:

• Added CurrentValueXArray so you can retrieve another column (at the same line) in For each list.
  
• Fixed a couple of errors in the Variables window
  
• Added support for selecting multiple nodes in XML Read Node Task
  
• Added post process Variable support for File rename Task
  
• Fixed a problem with running a single Task
  
• Fixed some version updates of all installation files
  
• Fixed a permission problem in API concerning multiple connections against the same Server (with same Client)
  

---

We have added an example of how to use the For Each loop here:

http://www.visualcron.com/Tutorials.aspx 

---

Hi,

My 1st reaction whithout installing the new version is WOW!! Looping! YESS!!

So I downloaded the beta and began testing.
Here are my results so far:

1. Beginning a new job the buttons 'edit loop' and 'delete loop' are enabled, but no loopings/tasks are there yet.
   
2. If I added the 1st loop, the buttons 'edit loop' and 'delete loop' are not enabled. I have to click around and back on the task to enable them.
   
3. I tested the for each x on y and this was working perfectly with output from a previous task with only one task in the loop.
   
4. I like the Variable Key addition.
   
5. The Start/End task loop dropdown is showing tasks in task adding order, not the right task order.
   
6. If I use the for each x row in y, and I have more tasks in the loop, the loop is infinitive.
   
7. If I open the variable window in the for x to y and closing it by pressing the x in the upper corner, the for each x row in y becomes empty.
   
8. It looks like I can't see which tasks is running in the job with a loop. Job status/result isn't updated while running.
   
9. Using the 'for x to y' with two tasks in the loop, the 1st time both tasks are run, the next itterations, only the 1st runs, the 2nd task is skipped.
   

I do not have the time to test some more, but the above list are some things to check I think.

I will test some more later.

Regards,
Erik

---

Thanks Erik.

We are addressing this issues now and we will release a new version later today. Please wait with any testing until this new version comes out.

Thank you.

---

New version uploaded. You need to uninstall previous first if you already have version 6 installed.

We think that we have fixed everything in your list Erik. Except 8 - we believe that loops is so fast so you don't see the updates. Try using a wait Task and you will see that update is correct.

Thanks

---

Good stuff! I will continue testing tomorrow.

Thanks for all the hard work!

Regards,
Erik

---

Hi,
I downloaded the new version and redo my steps. Here's the result:

Hi,

1. FIXED
   
2. NOT FIXED. If I have a task is selected which belonges to the loop and I create the loop, after closing the loop window, the buttons are not enabled. I have to select an other task to get the buttons enabled.
   
3. ...
   
4. ...
   
5. FIXED
   
6. FIXED
   
7. FIXED
   
8. but I think it has to do with me taking over a machine and it looks like I do not get all the screen updates. If I force screen udpdates it shows me the correct info, so this wasn't an issue at all I think, so FIXED ;-)
   
9. FIXED

So I went further with this version and I encountered some other issues:

1. If I start a loop I can set the start and end loop. I can set the beginning as the 2nd task and the end as the 1st task. This is not the in right order and the loops images shown on the tasks are not right.

Regards
Erik

---

We have updated the download once again. Thanks for the testing Erik!

Here is what has been fixed:

• Fixed activation/inactivation of buttons/menus when new Loop was created
  
• Warning when trying to do a reverse Task order in loop
  
• Added buttons in Task grid (Edit Job) for changing order
  
• Fixed a bug when a Task in loop was moved into other loop (original loop was not deleted)

---

Thanks!,

I did not have the time to test it further today though. I might get back on this next week.
About the loop buttons in task window, you have to look out moving tasks out of the loop and keeping the buttons enabled.

Regards,
Erik

---

In the loop iteration amount, you can enter your own value.
This works fine if I reduce the amount, but there is no error handling here if I enter a big number:


I can even enter a negative number...

Regards
Erik

---

In the loop iteration amount, you can enter your own value.
This works fine if I reduce the amount, but there is no error handling here if I enter a big number:

System.OverflowException: Value was either too large or too small for an Int32.
   at System.Decimal.FCallToInt32(Decimal d)
   at UCLoop.EDIJALCCOEHLBHHOBDOADIEHMPOHHIDIJPAN()
   at frmAddTaskLoop.EDIJALCCOEHLBHHOBDOADIEHMPOHHIDIJPAN()
   at frmAddTaskLoop.BLBCMNDIJJMKNPNFIKBBIPLMKAAKGPLAOLFD(Object , EventArgs )
   at System.Windows.Forms.Control.OnClick(EventArgs e)
   at Infragistics.Win.UltraControlBase.OnClick(EventArgs e)
   at Infragistics.Win.Misc.UltraButtonBase.OnClick(EventArgs e)
   at Infragistics.Win.Misc.UltraButton.OnMouseUp(MouseEventArgs e)
   at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
   at System.Windows.Forms.Control.WndProc(Message& m)
   at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
   at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
   at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lpara

I can even enter a negative number...

Regards
Erik

Thanks, we can try validating but sometimes a Variable might be used here which can only be accessed at runtime. But in most cases we should be able to validate.

---

I can not enter a variable here.
The box won't allow a-z characters.
If I paste the uservariable it will show my variable name, but if I close the window the previous number is restored.

---

I can not enter a variable here.
The box won't allow a-z characters.
If I paste the uservariable it will show my variable name, but if I close the window the previous number is restored.

Which box are you talking about exactly? Sounds strange.

---

In the loop settings, the Limitation box, Max itterations.

---

In the loop settings, the Limitation box, Max iterations.

Ah, ok, sorry, I thought you were thinking about the x and y values.

---

Uploaded a new version. Fixed the following in build 12952:

• Added some validation to loop values
  
• Fixed a problem with validating a Job with File Trigger
  
• Fixed a problem with RunTasksInOrder = false

Uninstall current first - then install new version.

---

I just downloaded and upgraded to 6.0.0, and I need to say that I truly love the LOOP function.

I just discovered one curiousity:
I created a "While" loop, where I checked the output of a task.
For this loop I had to check the "Sleep/Wait in each iteration", which I set to 1 minute. However it turned out that it waited exactly 1 minute between each step instead iteration.

Am I the only one to have this bug?

Best regards,
René

I just downloaded and upgraded to 6.0.0, and I need to say that I truly love the LOOP function.

I just discovered one curiousity:
I created a "While" loop, where I checked the output of a task.
For this loop I had to check the "Sleep/Wait in each iteration", which I set to 1 minute. However it turned out that it waited exactly 1 minute between each step instead iteration.

Am I the only one to have this bug?

Best regards,
René

Thanks René, we will verify and look at this now. Thanks for the report.

---

We have updated the download. Uninstall current and install this version.

The following changes has been made:

• Fixed a possible synchronization problem in the core scheduling. Could cause scheduling to fail in some scenarios.
  
• Fixed a problem with Wait waiting for each Task instead of each loop
  
• Fixed a problem with finding next Task when a While loop did not match

Thanks René for your findings - please test if this version works better.

---

Super.

Now I've come across another weird issue. ...well several actually.
a) The semicolon-separator in the sql-tak now actually works. I had to compensate for this :)
b) I had a condition: "if previous task has output then continue". I don't think I need to explain the simple nature of this task . However - it stopped working. It now always exits. Doesn't care if there is output or not.

I checked the extended debug in my condition, and it exits on "Task not found". So previous task is not found in the condition. The condition's match is "previous task is <blank>".

I checked the extended debug in my condition, and it exits on "Task not found". So previous task is not found in the condition. The condition's match is "previous task is <blank>".

When you say previous Task, is it a Task in a loop or? Please explain the Task structure in the Job.

---

"Previous task" as in a condition.
I have a condition, which matches on "output previous task is not <blank>" and a "match all" and "match any" => continue, "match none" => exit.

This condition doesn't work. And I realized that's bad. very bad. since I have a lot of task in different jobs that use this condition.

For now I had to downgrade to 5.8.0. Good thing the settings are backwards compatible. 🙂