General WF Question-Evaluation of Template Script

I was wondering whether the template script blocks within a workflow are evaluated only once after job instantation? If so, then once the job spec (?) has been created creating variables for a task or job could only be done by using WFtask and WFworkflow objects?

Clearly I'm a neophyte, but I was hoping for a little clarification. Also, would variables created for one task be passed onto another, how about from a parent job to a child job? Similar question for files attached to one task? Will the next one it transitions to have the same attached files?

Thanks, and yes these are pretty basic questions

Edited by sraza on 04/21/03 03:28 PM (server time).

Find more posts tagged with

Comments

Migrateduser

You are correct - once the job has been created, the only way to create job/task variables is through the modules or the iwjobvariable CLT.

I have never really understood why anyone would choose to use task variables over workflow variables, but what do I know. You can view any variable as long as you know the task ID or job ID they are associated with. As far as the concept of "passing" them, that isn't how it works. You use the modules and/or CLT to manipulate the variables.

Files must be attached to the first task in your job, I believe. Once attached they stay with the job through all the tasks. Files are attached to a job in a task, but they belong to the job. This isn't the last time you'll scratch your head when it comes to workflow.

Dave Smith
Sr. Software Engineer
Nike, Inc.
(503) 671-4238
DavidH.Smith@nike.com

Adam Stoller

I think iwsend_mail.ipl is a good example of why one would use a task variable over a workflow variable - it allows you to customize the mail for that particular task without having to create a whole new script for each notification task.

On the other hand, workflow variables are very useful for things that do not have task-level significance (even if they are refrenced by various tasks) - and are especially useful for communicating information from one externaltask/cgitask to another externaltask/cgitask.

Each has it's uses.

--fish
(Interwoven Senior Technical Consultant)

transparent_overlay.pdf

Migrateduser

Yes, I agree about the email script usage of task variables - in fact Template Based Email requires task variables be set. I was thinking more in general terms and if you are setting up variables that might be used by more than one task, it would be best to use workflow variables, which could be considered more like global variables for your workflow.

Dave Smith
Sr. Software Engineer
Nike, Inc.
(503) 671-4238
DavidH.Smith@nike.com