nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

ownership

grego122

How can I extract the userid (whom took ownership) in a group task and assign it to a global variable so I can use it in other task commands?

Find more posts tagged with

Comments

Migrateduser

In an externaltask that you execute after the grouptask, run WFtask::GetOwner() on the grouptask.

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

grego122

How can I return it back to the workflow? There is not a command attribute for group task - so if I understand correctly, I would need to have a external task that is a successor to group task. This external task can call a perl script with the command tag and the script will do the following:
$workflow=new TeamSite::WFworkflow(ARGV[0]);
$task =new TeamSite::WFTask(ARGV[1]);
my $task_owner = $task->GetOwner();
$workflow->CreateVariable($var_name, $task_owner);

Migrateduser

That is correct, sort of. You would have your externaltask as a successor to the grouptask and then set a workflow variable as in your example. However you need to run WFtask::GetOwner() on the grouptask, not your externaltask. So you'd first have to do something like WFworkflow::GetTaskByName() in order to get the task object for the grouptask. Then you can do your GetOwner on that task. I don't understand what you mean by How can I return it back to the workflow?. What do you need to do with the information? I assume you want to send that person an email or assign the owner of some other task to be that person. You can do all that within the same or another externaltask script.

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

Edited by Smitty77 on 01/23/03 02:30 PM (server time).

grego122

I want to create a workflow variable using the CreateVariable() function. I want to use this variable as an argument to an email script(another external task) that send email to the author and the editor who took ownership in the grouptask. These calls to the email script would be external tasks not owned by editor.

Migrateduser

Then you are on the right track. Go back and re-read my previous reply - I had to edit it because you had missed something in your previous reply. I think you get the idea - ultimately you want to set up a workflow variable with the owner of the grouptask assigned to it. Then you can use it however you like down the road.

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

grego122

Great, that is what I thought I needed to do. One last question/confirmation.
(1) I cannot call a script in the group task because there isn't a command attribute.
(2) Do external task or user tasks support multiple command tags?
<command v="_INSERT_("$setvariable")/>
<command v="_INSERT_("$email_cmd")/>

Thanks again for all your help!!

Migrateduser

Nope, you cannot call a script in a grouptask. And you only get one command tag per externaltask. But you can have your script call other scripts, or have 2 externaltasks one after the other.

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

Adam Stoller

As a minor plug for iwsend_mail.ipl (5.5.2) - if you use the task-level variables such as mail_from, mail_to, and mail_cc, you could (as David suggested) do the entire thing from your externaltask script.

I've been doing quite a lot of this lately and it works very nicely, though the externaltask scripts tend to be tied very heavily to the workflows for which they were intended to work with - because I rely heavily on task names.

Once you get the owner of the grouptask, you then get a handle on the task object representing the notification task and either set or modify the appropriate task-level variable with this information.

Terse Example:
my $job = TeamSite::WFworkflow->new($jobid);
(my $s1, $gtask) = $job->GetTaskByName($gtaskname);
(my $s2, $n1task) = $job->GetTaskByName($n1taskname);
(my $s3, $n2task) = $job->GetTaskByName($n2taskname);
my $owner = $gtask->GetOwner();
$n1task->CreateVariable("mail_to", "$owner");
my $cc = $n2task->GetVariable("mail_cc");
$n2task->SetVariable("mail_cc", "$cc,$owner");

Hope that helps,

--fish
(Interwoven Senior Technical Consultant)

grego122

Thanks for the post. I was able to accomplish what I needed using an external task BUT as you said, the tasks are tied closely to the workflow. Do you know if I can call a perl script(or just inside the tag) to do this within a <template_script> tag in the grouptask? Not really sure when the <template_script> tags code get implemented???

Migrateduser

That doesn't make any sense. I'm still unclear as to what you are ultimately trying to accomplish and why externaltask scripts are not doing the job for you. Any <template_script> tags within your wft file will be resolved at instantiation. In other words, they will be resolved just after your initial user input screen is filled in and you click the "Run Job" button. Then you will have a job spec file which is pretty much carved in stone unless you use CLTs or the GUI to modify any of the modifiable fields.

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

grego122

I was thinking I can do the following w/in a grouptask w/o having to call an external task. My next task after the group task is an external task to deploy to staging. This can work but can see it getting lost w/future changes.
<template_script><![DATA[
$cmd=$perl . " " c:/iwhome/local/bin/groupowner.ipl";
]]</template_script>
__INSERT__"<command v = $cmd/>"

The above would be ideal but understand the this wouldn't work because grouptasks do not support command tags.

Edited by grego122 on 01/29/03 01:49 PM (server time).

logs.zip

Migrateduser

Well sure, in a perfect world we could do everything in every task. But I guess I don't see the drawback of having the externaltask after the grouptask. It'll do exactly what you need and you can control everything about the email you send.

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

grego122

I'm trying to set a workflow variable that has been previously defined as $cgrouptaskowner and reset it in an external task script to use in other tasks. I am able to get the owner of the grouptask using GetTaskByName and GetOwner(). I then try do the following:
my $workflow = new Teamsite::WFworkflow(ARGV[0]);
my $oldvalue=$workflow->GetVariable("cgrouptaskowner");
my $newvalue="anything";
$workflow->SetVariable("cgrouptaskowner", $newvalue);

The GetVariable above does not return anything and the SetVariable does not set anything.

Thanks!!

Adam Stoller

$workflow->GetVariable() returns *workflow* variables:

<variables>
    <variable key="xyz" value="123"/>
</variables>

not Perl variables ($foo)

($task->GetVariables() returns task-level variables that are defined in a similar manner to job-level variables)

However if you are prompting for information during instantiation like:

TAG_info(
         cgrouptaskowner => ....
        );

there's a little [supported] trick that unfortunately I don't think ever made its way into the official documentation (Smitty - we know) - and you can change the above to:

TAG_info(
iw_setwfarg_cgrouptaskowner => ...
        );

And when the workflow instantiates it will create a job variable for you like:

<variables>
    <variable key="cgrouptaskowner" value="input from instantiation"/>
</variables>

And then you can use $workflow->GetVariable("cgrouptaskowner"); in your workflow and it will work.

Not sure if that's what you were doing since I haven't seen your actual wft code.

--fish
(Interwoven Senior Technical Consultant)

grego122

We're at 5.5.2 SP1. I tried the trick of using the iw_setwfarg_cgrouptaskowner in the TAG info; called an external task script and did:
$workflow->GetVariable('cgrouptaskowner') # This worked
$workflow->SetVariable('cgrouptaskowner', $new_value);
$workflow->Refresh();
$workflow->GetVariable('cgrouptaskowner'); # This worked
----Now, going back to the workflow, I did the following inside another external task.
__INSERT__(<command v = '$email_cmd -t $ciwuser, __TAG__(cgrouptaskowner); ..../>');

In debugging the $email_cmd script, the cgrouptaskowner was blank. Is my usage correct?

Thanks!!!

Migrateduser

I believe if you refer to a tag variable set up as iw_setwfarg_cgrouptaskowner with the __TAG__ directive within your wft file, you need to use this syntax:

__TAG__(iw_setwfarg_cgrouptaskowner);

However, keep in mind that the value of the __TAG__ directive will be resolved at instantiation time, and so if you change the value of iw_setwfarg_cgrouptaskowner using SetVariable in one of your tasks during execution of the job, it won't be reflected in your <command> tag. You will have to refer to this workflow variable within your $email_cmd script by evaluating it via a GetVariable call.

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

Adam Stoller

As Smittty points out there are a couple of problems with your effort here.
(1) within the wft, you need to refer to the full tag name (iw_setwfarg_****) when referencing it with __TAG__(); __VALUE__(); etc.
(2) the value is established at instantiation time not real-time.

So once again, I recommend using task-level variables for iwsend_mail.ipl for your notification script and *not* using the command line flags, that way you can set/adjust the value of those variables from [another] externaltask.

Please see the earlier posting I made (2003-01-23) regarding using iwsend_mail.ipl's task-level variables, in this thread.

--fish
(Interwoven Senior Technical Consultant)