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

transition from child task to parent task

Vishakha

We are using the perl module to construct workflows.
In the workflows manual it is mentioned that a child task can transition to a parent task.
How can we do this ...

Thanks

Find more posts tagged with

Comments

Migrateduser

You can transition the parent task the same way as any other task.

Vishakha

When I give the parent task name in the link_tasks in the child job and since this task name is not there in the child workflow while starting the nested job it gives the error that the task is not defined.

Adam Stoller

If you know the parent task's ID (or name) you can create a TeamSite::WFtask object for that task and then use the TeamSite::WFtask->CallBack() method to transition the parent task.

You cannot transition the parent task from the child task's object

Vishakha

That worked! Thanks a lot.
Now I can callback to the required parent task.However I can still see the child job in the "Jobs" tab.How can I end this child job since I no longer need it?

Vishakha

We are facing problem in doing the callback to the parent job from the child job.
We have the parent task id from the "task_id" variable in the child job.In an external task in the child, using the WFtask object we are trying to do the callback to the 1st successor however the child simply transitions to the 0th successor.

Trying to figure out hard.Please help.

Migrateduser

Task successors are numbered from 0. Could you post the code snippet that you are using to call the parent task.


my $p_task_id = "1234";
my $c_task_id = "12345";
my $p_task = TeamSite::WFtask->new($p_task_id);
my $c_task = TeamSite::WFtask->new($c_task_id);

# to transition the parent task 
$p_task->CallBack(0, "");

# to transition the child task
$c_task->CallBack(0,"");

Vishakha

Following is the code in the parent wft file.

link_tasks("resend_reject_reviewer", "resend_review_nested_job", "Select reviewer again");

link_tasks("resend_review_nested_job", "SiteEditor_review_reject", "Rejection from child");
link_tasks("resend_review_nested_job", "SiteEditor_review_approve", "Approval from child");

Task "resend_review_nested_job" is the nested task that calls the nested workflow

in the external task called by the child job follwing is the code

#!/apps/iw-home/iw-perl/bin/iwperl
use TeamSite::Config;
use TeamSite::WFworkflow;
use TeamSite::WFtask;

my $iwhome=TeamSite::Config::iwgethome();

my $wfid=$ARGV[0];
my $workflow = new TeamSite::WFworkflow($wfid);

my $childTaskId=$ARGV[1];
my $childTaskObj=new TeamSite::WFtask($childTaskId);

my $p_task_id=$workflow->GetVariable("parentTaskId");

#The parent task id was evaluated in the parent workflow using #variable "task_id"

my $p_task = TeamSite::WFtask->new($p_task_id);

my $callback_parameter=$childTaskObj->GetVariable("callback_parameter");

if($callback_parameter eq 'Approve'){
$p_task->CallBack(1, "Call to Parent on Approval");
}
elsif($callback_parameter eq 'Reject'){
$p_task->CallBack(0, "Call to Parent on Reject");
}
exit 0;

When we see the parent task xml using iwgetwfobj we can see the successors sets with proper taskid in the "v" attribute of the successors.

i.e the 0th successor has taskid of the reject task and 1st successor has taskid of the approve task

Still the nested job transitions to the rejected job irrespective of the option chosen.

Adam Stoller

Have you verified that:

 my $callback_parameter=$childTaskObj->GetVariable("callback_parameter");

is actually returning 'Approve' ?

Vishakha

yes we have verified that it gets the proper parameter "Approve".We are writing debug messages in the file.

Here is some output from the debug file
----------------------------------------------
child Task Id : 18809 -- parentTaskId :18799

callback_parameter => Approve

entered Approve **

Reached Last

Adam Stoller

yes we have verified that it gets the proper parameter "Approve".We are writing debug messages in the file.

Here is some output from the debug file
----------------------------------------------
child Task Id : 18809 -- parentTaskId :18799

callback_parameter => Approve

entered Approve **

Reached Last

Since I don't know where you placed the debugging lines I cannot tell if the data is meaningful or not.
The second line doesn't put any delimeters around the string so we cannot tell if there's any white-space surrounding it.
The third string is only meaningful if it was placed within the first if conditional just prior to performing the callback.

You should also add WFT debugging to verify that the successorsets in the generated wft are as you expect them to be - you only posted a small subset of the WFT code.

Also - you should look at the iwevents log to see whether it offers any insights to the transition that's taking place.

Migrateduser

Try running the external task from the command line in debug mode and inspect the values at run time.

Vishakha

We atlast registered a case with Interwoven and have received a reply that a child workflow, after it ends simply transitions to the next task in the workflow and cannot make a callback to a specific task in the parent workflow.