James D. said:Wolfgang - I'm not very familiar with SQL, but that looks like nearly exactly what I was looking for. I'll have to read up on SQL a bit, but I'm thinking that will do nicely for 2. It's definitely the Object number. I'm not sure why they call it "running number" in the documentation.
James D. said:It seems strange that there's not a way within the scripting language to match up an object number to a jobname for a given workflow, even if it would only work for active ones. I might just have to accept it, and use my original idea or the variable table thing.
Syntax : GET_STATISTIC_DETAIL([RunID], Detail, [Object name])
: SET &NAME# = GET_STATISTIC_DETAIL(&$RUNID#,"NAME",)
: SET &RUNID# = GET_STATISTIC_DETAIL( ,"RUNID","MYJOB")
select EH_Client, EH_Name, EH_ah_Idnr, EH_ParentAct, EH_ParentPrc
Name or running number of the workflow task that should be replaced.Format: script literal, number or script variable. Within a workflow, a task can be identified via its nameor its running number. You can specify the task nameornumber within the workflow. Specifying both parameters requires that the name and the number comply with each other.