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; } } }

End task activation

mangetak

Hi,

I am executing a workflow from an application using Content Services... The workflow executes correctly but does not end. It´s a two task workflow. One of them is an external task and the next thing to do it´s to end the workflow with an End Task. We find in the Workflow view (in the proffessional interface") that the workflow is added, that the external task is complete but the instance is still there remaining with no action required from user.

I attach an example of the workflow definition. We are running out of ideas.

Thanks in advace

Find more posts tagged with

Comments

Migrateduser

Does the externaltask callback? Can you post the externaltask code?

Migrateduser

but the instance is still there remaining with no action required from user

What is showing in the task list for this job? Is it the externaltask or the endtask? Can you take a screen shot?

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

Dwayne

Does the workflow work correctly if you don't invoke it via CS?

My guess is that your external task handler is running, but it's not doing a callback to tell the workflow engine that it's completed. I would suggest running the iwgetwfobj CLT for the job and each of the tasks, to see if something jumps out that might indicate the problem.

mangetak

Well... we don´t do any callback by codding. We dynamicaly create the workflow and the attachment sent before with the workflow spec it´s actually what we execute. There is no code for external task.

Thanks again

Edited by mangetak on 07/27/04 10:31 AM (server time).

Migrateduser

Well there you go - you can't call an externaltask and not do a callback. Have you ever written a workflow before? This is basic stuff...

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

Dwayne

That doesn't make sense. Every <externaltask> has to have a <command v="..." /> tag. The value of the v attribute must be a valid command line on the TeamSite server. Otherwise, there's no point to having that external task.

If you're saying that the attachment you sent is a direct copy of what was sent as a job specification, then I can certainly understand why it's hanging. I thnk that perhaps you don't have a good handle on the function of an external task. What was this workflow supposed to do?

mangetak

OK... the workflow is executing and iwpt_compile command. I just removed it cause it was too long. The command works if you execute on the command prompt, Actually when executing the job, a page is correctly created. The problem must be not calling a callback function. And answering to the question, you are right. It´s the first time I develop a workflow and didn´t know about the need of writting a callback function.

Thanks again for the information

Dwayne

Yup, that's definitely the problem. Just write a simple wrapper perl script, which invokes iwpt_compile and then does the callback.

The following code will run any arbitrary command, and then tell the workflow engine that it's done. You'd put the reference to this code in the <command v="..." /> attribute, and then add below that
<variables>
<variable key="command" value="..."/>
</variables>

where the "..." in value="..." is replaced with your current iwpt_compile command line

(this is untested - I'm just typing it in as I go, so there may be syntax errors. It also has no error checking, which is not normally a good idea)

wrapper.ipl:

# Run a command line on the server, and do a callback to the workflow engine with the return code
use TeamSite::WFtask;

# Get the automatically added command line parameters
my ($jobid, $taskid) = @ARGV;

# Create a task object
my $task = new TeamSite::WFtask($taskid);

# Read that object to see what command line we're supposed to run
my $cmdline = $task->GetVariable("command");

# Run the command
my $rc = system $cmdline;

# Tell the workflow we're done
$task->CallBack($rc, "external task completed");

---
Good luck!

mangetak

Thanks a lot....

We tried what you posted and That was perfect...! Smiley Wink

Thanks again to all

Adam Stoller

# Run the command
my $rc = system $cmdline;

# Tell the workflow we're done
$task->CallBack($rc, "external task completed");

Uhm - I'm not sure you want to rely on $rc for the callback index value. If there's an error $rc might be something like -1, 1, 256, etc. and then the callback won't work if there's not a matching successorset for that index.

Instead - if you want to trap an error situation:# Run the command
my $rc = system $cmdline;

# Tell the workflow we're done
# Success - callback value is 0, Error - callback value is 1
$rc = 1 if ($rc);
$task->CallBack($rc, "external task completed");Otherwise it's just:# Run the command
system $cmdline;

# Tell the workflow we're done
$task->CallBack(0, "external task completed");

--fish
Senior Consultant, Quotient Inc.
http://www.quotient-inc.com

Dwayne

In reply to:

Uhm - I'm not sure you want to rely on $rc for the callback index value. If there's an error $rc might be something like -1, 1, 256, etc. and then the callback won't work if there's not a matching successorset for that index.

I have to admit - I was aware of that. I left it there intentionally, as sort of "fish bait." And I caught something.

. I was fairly certain that you wouldn't be able to let that pass.