perl code in .wft file

All,
I am having some problems when I am writing Perl code in a workflow template. When I add my own custom code, the workflow half on a screen with "Run Job" and "Cancel", then when I click "Run Job" the workflow functions nicely. But when I take this custom code out, the workflow automatically runs with the first task (mtmetaproxy.cgi). Is there something about adding you own code (all I am doing is printing some variables to a log file) that make the workflow stop? Any help on this topic would be greatly appreciated.

Thanks,

Lucas.

Lucas Cochrane
lcochrane@dc.com

Find more posts tagged with

Comments

Migrateduser

You're not making sense. Post your WFT and highlight the code you are referring to.

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

Ottawa_IWOV

Here is the wft file. Right near the top there is some code that will get the file list and store it in an array @submit_file. Just below I try and write the contents of the array to a log file.

Lucas Cochrane
lcochrane@dc.com

Migrateduser

OK, now can you state the problem again as clearly as possible.

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

Adam Stoller

If you have no TAG_info() statements - or no required TAG_info() statements that do not have supplied default values - the workflow instantiator will skip past the input form and go directly to the start task (which you have as a cgitask with immediate="t" owned by the user running the workflow).

If you want it to go through the instantiation form - make sure you have a required TAG_info() variable without a default value specified.

Is that what you were asking about?

--fish
(Interwoven Senior Technical Consultant)

johnjamesmarsh

The workflow instantiator does not display the input form (with 'Run Job' on it) unless there is a required input field, i.e.

is_required => 'true'

Your custom code had one of these sections and that is why it displays.

Hope that helps

John

Ottawa_IWOV

OK :-)

What I am trying to do is pass variables from a workflow (wft) to an external task via iw_setwfarg_****. With my somewhat limited knowledge of workflow, you can only do this within a TAG_info function. I would like to pass templating category types and tpl(s) to an external task that will generate files.

So I introduced some perl that would make a decision based on the attached DCR(s) (submitting to STAGING), then pass the appropriate category type and tpl to the external task to generate the HTML files? When I do this, the workflow does not goes immediately to the start task, a screen appears that only lets me select Run Job, then it goes to the first task. I am obviously goofing up the TAG_info() section, but I don't know where.

Is there an easier way to accomplish this validation/decision making in the wft? Is my situation clear?

Thanks for all your help :-)

Lucas

Lucas Cochrane
lcochrane@dc.com

Migrateduser

Did Ghoti's and John's posts clear things up for you?

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

Ottawa_IWOV

I was able to clear a lot of things up, you help was great. But I do have one other question. How do I access a variable in a script (i.e. external task) from a .wft? Basically, we are going to present our users with a TAG_info screen that will ask them which tpl they want to generate their DCR with. I want to be able to access this value in a script that will generate the files. Here is some sample code:

TAG_info(
iw_tpl_select =>
[ html => "<input type='radio' value='/templatedata/sd-ps/en_sd/presentation/testing123.tpl'>Communications Press Release</input>" .
"<input type='radio' value='/templatedata/sd-ps/en_sd/presentation/testing345.tpl'>Basic HRDC Page</input>" .
"<input type='radio' value='/templatedata/sd-ps/en_sd/presentation/testing678.tpl'>New HRDC Page</input>",
is_required => "true",
label => "<tr bgcolor=yellow><td colspan=1><em><center>" .
"Which presentation template would you like to use" .
"</center></em></tr>",
],
iw_desc =>
[ html => "<textarea rows=5 cols=51>Submitting DCR(s) to Staging</textarea>",
label => "<tr bgcolor=yellow><td colspan=1><em><center>" .
"Description" .
"</center></em></tr>",
],
);

How am I able to get the value they select into a variable in a script as part of the workflow? For example iw_tpl_select

Thanks,

Lucas.

Lucas Cochrane
lcochrane@dc.com

james1

Store your data in job (and/or task) variables. The external task program will have access to those.

-- James

--
James H Koh
Interwoven Engineering

Adam Stoller

iw_setwfarg_ is a *convenience* feature - it takes the part following that prefix and uses it as the 'key' and the value filled in as a 'value' for a workflow variable upon instantiation - which can then be accessed using TeamSite::WFworkflow->GetVariable('keyname') - where 'keyname' does *not* have the 'iw_setwfarg_' prefix.

The same thing can be done by using a non-prefixed TAG_info() variable and simply writing out your own <variable key="keyname" value="__VALUE__('formvariable');"/> in the appropriate location within the wft.

Alternatively, if you are programmatically generating the value information - you can again set up a workflow variable with <variable key="keyname" value="__INSERT__($yourvarname);"/> in the appropriate location within the wft.

--fish
(Interwoven Senior Technical Consultant)