"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.

Could you be more specific about the Task structure in the Job and where among the Tasks the Condition is used. I guess you are not using any loop in this Job?

For example:

I have Job A with Tasks:

1. Task 1
2. Task 2
3. Task 3 <-Condition is set on Task 3 and checks Task 2 (Previous Task)

---

Yes, sorry, I can be more specific:

I have a job with 2 tasks:

1. Task 1
2. Task 2 <- Condition is set on task 2, which is run if previous task has output.

The error is that: Task 2 is never run. Doesn't matter if task 1 has output or not. This work in version 5.8.0 (haven't tested 5.8.1).

The log gives me the following debug information:
"VisualCron Condition (TaskOutputIs) returned: MatchError: Task not found"

No loops. No nothing else.

:)

We have updated the exe. Please uninstall and install this latest download.

In this version (15111 ) we have done the following:

• Fixed a problem with PrevTask in Conditions

Thanks for the report René - we would really appreciate if you could upgrade to this latest version and verify the fix. Thanks.

---

The specific bug was solved. Thanks. :)

However, now I discover new bugs.

I have the following Job:
1) Task 1
2) Task 2
3) Task 3 (sometimes fails, and thus I have "on Error" => continue)
4) Task 4
5) Task 5 (disabled)
6) Task 6

The bug is that the job stop after Task 4. It doesn't run Task 6. If I move Task 6 above Task 5, then it is executed correctly.
In version 5.8.0 Task 6 is executed correctly, even if it is located after the disabled Task 5.

-René

We have updated the exe. Please uninstall and install this latest download.

In this version (20260) we have done the following:

• Fixed a problem related to the inactivate Tasks and the last Task in a Job

Thank you again René. Please verify if you can.

---

The more features the more difficult is the overview. Having beta testers is a blessing. Thanks hawkings for your time! 👍

Regards,
Erik

---

The more features the more difficult is the overview. Having beta testers is a blessing. Thanks hawkings for your time! 👍

Regards,
Erik

Yes, it is. And especially this version where the core was rewritten. It is really hard to test each scenario again. Thanks again!

---

I finally dared upgrading again, and the specific bug seems to be fixed. :)

Also I am not sure what you mean by beta tester...I test in our 50 job production environment. 🙂

New bug:

I have 6 tasks, but the conditions don't work properly now:
1) Task 1 (no output)
2) Task 2 (no output)
3) Task 3 <- Conditioned: If Task 1 and Task 2 has output (match all), then run, else Next (match any or match none)
4) Task 4 <- Conditioned: If Task 1 and Task 2 has output (match all), then run, else Next (match any or match none)
5) Task 5 <- Conditioned: If Task 1 and Task 2 has output (match all), then run, else Next (match any or match none)
6) Task 6 Bug: Is never run
7) Task 7 Bug: Is never run

The job is now saying it is "Running" although there are no running tasks. Last run task is Task 2 (since Task 1 and 2 had no output). I have not tested if one task had output (eg. Task 1 has output and Task 2 had no output), but the condition should on "Match Any" (= only 1 output) do the same as "Match None".

-René

New bug:

I have 6 tasks, but the conditions don't work properly now:
1) Task 1 (no output)
2) Task 2 (no output)
3) Task 3 <- Conditioned: If Task 1 and Task 2 has output (match all), then run, else Next (match any or match none)
4) Task 4 <- Conditioned: If Task 1 and Task 2 has output (match all), then run, else Next (match any or match none)
5) Task 5 <- Conditioned: If Task 1 and Task 2 has output (match all), then run, else Next (match any or match none)
6) Task 6 Bug: Is never run
7) Task 7 Bug: Is never run

The job is now saying it is "Running" although there are no running tasks. Last run task is Task 2 (since Task 1 and 2 had no output). I have not tested if one task had output (eg. Task 1 has output and Task 2 had no output), but the condition should on "Match Any" (= only 1 output) do the same as "Match None".

-René

Hi René, thanks for the report. We were not able to reproduce this fully. Could you export this Job and Condition?

---

Hi Support

Okay found another issue with V6.00 (although I'm not sure if it also applies to earlier version as I don't have any installed).

Have created a new job and added an XML 'Read Node' task. Have defined an XML filename, and also a simple Xpath command (/CyBizXML[1]/Statement[1]). However, if I click in the XML Filename field and try to amend the filename that I have already defined, VC crashes. Have tried this many times and time it does the same thing. I haven't got around to testing this in a loop yet (the idea was I could change the filename to a wildcard - *.XML and re-write the XML to a merged xml output file).

As a side note - there is absolutely no documentation in the help file for the XML tasks - I need to merge thousands of XML files into a single XML file - is this possible? Where can I find more documentation about xml file handling?

Cheers

Andy

Hi Support

Okay found another issue with V6.00 (although I'm not sure if it also applies to earlier version as I don't have any installed).

Have created a new job and added an XML 'Read Node' task. Have defined an XML filename, and also a simple Xpath command (/CyBizXML[1]/Statement[1]). However, if I click in the XML Filename field and try to amend the filename that I have already defined, VC crashes. Have tried this many times and time it does the same thing. I haven't got around to testing this in a loop yet (the idea was I could change the filename to a wildcard - *.XML and re-write the XML to a merged xml output file).

As a side note - there is absolutely no documentation in the help file for the XML tasks - I need to merge thousands of XML files into a single XML file - is this possible? Where can I find more documentation about xml file handling?

Cheers

Andy

Thanks for the report. We have now fixed this for next version.

About documentation. We will soon start to fill all documentation gaps. Please post separate questions in the forum if you need to know something specific now.

---

Hmmm - okay another issue....

In the XML 'Read Node' task, I tried to reference a 'Variable' rather than a filename (i.e. I want to take the value from the Loop 'FOR EACH ROW IN {TASK(PrevTask,StdOut)} which processes through each XML file found in the previous 'GET FILE' task). The problem is in 'Read Node' task, if I select 'Variable' it will not accept it, telling me that I must define a Filename.........

Cheers

Andy

Hmmm - okay another issue....

In the XML 'Read Node' task, I tried to reference a 'Variable' rather than a filename (i.e. I want to take the value from the Loop 'FOR EACH ROW IN {TASK(PrevTask,StdOut)} which processes through each XML file found in the previous 'GET FILE' task). The problem is in 'Read Node' task, if I select 'Variable' it will not accept it, telling me that I must define a Filename.........

Cheers

Andy

Could not reproduce this. It only says this if you have not selected Variable radio button. Please attach a screen shot.

---

Hi Henrik

Screenshot attached - if you need any further information then let me know

Cheers

Andy

Hmmm - okay another issue....

In the XML 'Read Node' task, I tried to reference a 'Variable' rather than a filename (i.e. I want to take the value from the Loop 'FOR EACH ROW IN {TASK(PrevTask,StdOut)} which processes through each XML file found in the previous 'GET FILE' task). The problem is in 'Read Node' task, if I select 'Variable' it will not accept it, telling me that I must define a Filename.........

Cheers

Andy

Could not reproduce this. It only says this if you have not selected Variable radio button. Please attach a screen shot.

Got it. Thanks. Fixed.

---

Hi all

has anybody used the XML tasks (Read Node etc) to merge multiple XML files into a single output file? There is no documentation about this in the Help file so was hoping someone had managed to figure this out?

I have approximately 150,000 XML files to merge (from a billing system). I am using V.C V6 with the new Beta Looping functionality. In the Job I have three tasks:

1. List the XML files in a particular folder.
2. Start Loop - FOR EACH FILE IN STDOUT of previous task
XML READ NODE from XPath Expression '/CyBizXML[1]/Statement[1] using STDOUT variable from LOOP
3. Write File from previous task STDOUT to a default output file.
END LOOP

In this scenario, (i.e. Looping), in Read Node task I am using the variable {LOOP(CurrentValueXArray,0)} to reference each file identified in the loop (from task 1) but I am getting an error message (Exception in Task: Data at the root level is invalid. Line 1, position 1.) However, if I don't use the loop and specify a specific XML file (which will use the contents from one specific file 'x' times), I don't get the error

If anybody has tried this kind of thing before and can offer some guidance it would be very much appreciated

I have attached some screenshots showing what I have set up

Cheers

Andy

[EDIT]MOVED TO BETA FORUM[EDIT]

So quick :-)

Thanks Henrik

Andy

We just uploaded build 13918 with the following changes:

• Fixed a bug causing Tray client to disconnect (did not recognize new loop settings)
• Fixed a crash in XML File Read Task when file path was edited manually
  
• Fixed a problem saving XML File Read Task with Variable type
  
• Added the .NET code execute Task
  
• Added the .NET Condition

Uninstall and then install.

We now hope that René (hawkings) can send us a smaller, reproducable sample of the other Condition bug. 😁

---

Hi Henrik

Installed build 13918 and have discovered another issue.

I have a task that starts a Loop and that task points to files stored on an external drive (R:\). If that Drive is not available when I try to edit the task, VC Crashes. I can't change the task to point to another drive.

Also, the previous issue reported with the XML Read Node not allowing to define a VARIABLE without defining a File Name as well does not seem to be resolved. I am currently backing up my R: drive but when that is done I will take screenshots.

Cheers

Andy

Hi Henrik

Just wondered why my post (#42 above) about usage of XML ReadNode task has been moved from the General forum to this one (Beta releases)

Cheers

Andy

Hi Andy,

I did move your post tot the beta forum, because the looping functionality you mentioned in your post is still in beta.


Regards,
Erik

---

Hi,

A long time ago I mentioned something about running jobs with or without conditions.
(old post )

It is still a strange GUI issue.
I made a small movie, so you can see what I mean.

Regards,
Erik

---

Hi Erik

Ahh - okay - thanks for the explanation. I just wondered where it had gone to as I am hoping to get a response from it :-)

Henrik - I will also add an enhancement request in the feature requests forum for a specific XML Merge task, just in case I am trying to do something that is not easily possible.

Thanks

Andy

My collegue has an issue with adding tasks to a job. After adding tasks, they are not shown in the main gui.

Regards,
Erik

---