Ok, I managed to access the previous output lines in subsequent set variable tasks like this. Thanks!
Just one further question. The procedure worked fine with global user variables, but actually I would like the variables to be bound to the job they refer to.
When I used {JOB(Active,Variable,myVariable)} in the "Name/unique key" field of the set variable task , where myVariable is the name of the job variable that I want to update, I got the following output after running the job
Variable '' was added with value: {STRING(FirstLine|{TASK(ce0ba517-37e2-48cc-b9f3-1b6cc31413c7,StdOut)})}
which says that a variable with empty name was added the value. In other words, the job variable was not updated.
When just using myVariable in the "Name/unique key" field then a global user variable with the name myVariable is created.
Is it possible at all to write to job variables from a set variable task (or any other task) or can I just access global user variables?
Thanks for any help,
Benjamin
BennyHa attached the following image(s):