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

No workarea found

amaresh

Hi thanks in advance,

I am trying to fix a workflow, which was written by someone else. This is the code for the workflow.
<?xml version="1.0" standalone="no"?>
<!DOCTYPE workflow SYSTEM "iwwf.dtd">
<template_script><![CDATA[

use TeamSite::Config;

## Uncomment and paste into TAG_info to turn the debugging on
# iw_debug_mode => "<input type='text' value='true'>",

my $iwhome = TeamSite::Config::iwgethome();
# The path to TeamSite Perl.
my $iwperl = "$iwhome/iw-perl/bin/iwperl";

my $test_command = "$iwperl $iwhome/local/bin/iwodstart.ipl synchronize_workarea_assets";

]]></template_script>

<workflow name="External Task Test"
owner="__TAG__('iw_user');"
creator="__TAG__('iw_user');"
description="Synchronizing Preview Assets">

<externaltask name="DeployForPreview"
owner="__TAG__('iw_user');"
description="Synchronizing TS assets with preview environment"
start="t"
readonly="t">
<areavpath v="__TAG__('iw_workarea');"/>
<successors>
<successorset description="Finish Job">
<succ v="End"/>
</successorset>
</successors>

<command v='__INSERT__($test_command);'/>
</externaltask>

<endtask name="End">
<activation>
<pred v="DeployForPreview"/>
</activation>
</endtask>

</workflow>

The error I am getting is :
Invaild workflow:
Error: Bad area in task DeployForPreview
Error: 02007: No workarea found
Job 13412 does not exists
Error: 02007 No workarea found.

Please try to help me with your suggestions.

Your's truly,
Amaresh

Find more posts tagged with

Comments

iwovGraduate

TS version?
How are you starting the workflow? Which UI?

The error seems to indicate that iw_workarea does not have a valid value.

Use debug mode and see what iw_workarea evaluates to for the line <areavpath v="__TAG__('iw_workarea');"/>.

If you don't know how to get the green/yellow debug screen, refer to Adam's workflow tutorial (can be found in one of the KB articles/Tech notes.)

amaresh

I am using TS 6.5 and I am just invoking the workflow from the pop up, which we get after clicking the "New Job" button. Then this error pops up.

Adam Stoller

From which UI and from where within the UI are you invoking the job?

If you are doing it in CCPro's main navigation tab - it should work.
If you are doing it in CCPro's workflow tab - it won't work - because there's no context for the workarea there.
If you are doing it in CCStd's main portal interface - it won't work - because there's no context for the workarea there either.
(I believe some folks have customized CCStd's navigation interface to include a New Job link so that the job can be started with a workarea context - I haven't had to deal with it so I don't have any details on the implementation of the customization)

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

sunsun

try this

Dont start the new job from the outside (i Mean without selecting any workarea from the left navigation)

you have to go to a specific branch/workarea before you click on new job button.
you are not in the workarea and are trying to access the workarea value.

Thats the reason for that error

see if it helps

amaresh

Hi thanks for the responses,

I am in the right workarea and I still get the same error. I am using CCPro as UI. I was able to run the debug mode with the yello and green screen. But still it doesn't show up any errors there. Thanks!

Amaresh

iwovGraduate

Post the lower portion of the yellow/green screen - which has the workflow xml. (can't remember if its yellor or green at the bottom)

or just post the whole thing.

amaresh

WF Specification Generator
[ 1] package WFtemplate_script;
[ 2] use utf8;
[ 3] $_this_->set_chunk_number(1); # (auto generated)
[ 4]
[ 5]
[ 6] use TeamSite::Config;
[ 7]
[ 8] ## Uncomment and paste into TAG_info to turn the debugging on
[ 9] $_this_->TAG_info(
[ 10] iw_debug_mode => "<input type='text' value='true'>",
[ 11] );
[ 12] my $iwhome = TeamSite::Config::iwgethome();
[ 13] # The path to TeamSite Perl.
[ 14] my $iwperl = "$iwhome/iw-perl/bin/iwperl";
[ 15]
[ 16] my $test_command = "$iwperl $iwhome/local/bin/iwodstart.ipl synchronize_workarea_assets";
[ 17]
[ 18]
[ 19] $_this_->set_chunk_number(3); # (auto generated)
[ 20] $_this_->__TAG__('iw_user');
[ 21] $_this_->set_chunk_number(5); # (auto generated)
[ 22] $_this_->__TAG__('iw_user');
[ 23] $_this_->set_chunk_number(7); # (auto generated)
[ 24] $_this_->__TAG__('iw_user');
[ 25] $_this_->set_chunk_number(9); # (auto generated)
[ 26] $_this_->__TAG__('iw_workarea');
[ 27] $_this_->set_chunk_number(11); # (auto generated)
[ 28] $_this_->__INSERT__($test_command);

WF Specification
<?xml version="1.0" standalone="no"?>
<!DOCTYPE workflow SYSTEM "iwwf.dtd">

<workflow name="External Task Test"
owner="D4DTDA01\interwoven"
creator="D4DTDA01\interwoven"
description="Synchronizing Preview Assets">

<externaltask name="DeployForPreview"
owner="D4DTDA01\interwoven"
description="Synchronizing TS assets with preview environment"
start="t"
readonly="t">
<areavpath v=""/>
<successors>
<successorset description="Finish Job">
<succ v="End"/>
</successorset>
</successors>

<command v='D:\iw-home/iw-perl/bin/iwperl

\iw-home/local/bin/iwodstart.ipl synchronize_workarea_assets'/>
</externaltask>

<endtask name="End">
<activation>
<pred v="DeployForPreview"/>
</activation>
</endtask>

</workflow>

Thank you
Amaresh

iwovGraduate

Are you sure you are in the workarea?
The value of areavpath, which should come from the variable iw_workarea, is empty - hense the error.
<areavpath v=""/>

Edited by iwovGraduate on 08/17/05 01:07 PM (server time).

sunsun

i just now ran your wf and it works fine.

Is it possible for you to send the screen print of your computer screen when you are clicking on the new job?

just press Atl+Print Scrn

amaresh

Thank you very very much sir. I fixed it. I appreciate your help.

AMARESH
Interwoven Consultant

sunsun

can you tell what was the problem?

so we can also know

amaresh

Actually, the path was empty.

I specified the below path in the template script section
my $area_vpath='/default/main/DIRECTV/SITE_LAUNCH/WORKAREA/DIRECTV_CONTENT';

and <areavpath v="__INSERT__($area_vpath);"/> in the worlflow section. It worked for me. Thank you for your suggestions.

AMARESH
Interwoven Consultant

Adam Stoller

<!-- <command v="iwodcmd start synchronize_workarea_assets"/> -->
<command v='D:\iw-home/iw-perl/bin/iwperl D:\iw-home/local/bin/iwodstart.ipl synchronize_workarea_assets'/>

FYI - neither of the above will work correctly - since neither iwodcmd nor iwodstart.ipl know anything about workflows and therefore they will not perform a callback to the workflow engine - so your externaltask will just hang until someone comes along and removes the job from the system.

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

amaresh

hi fish

You are right. Is there any way I could make that deployment command

<command v='D:\iw-home/iw-perl/bin/iwperl

\iw-home/local/bin/iwodstart.ipl synchronize_workarea_assets'/>
execute?. and make the job disappear without any user interaction?

When i run the the following command,

\> iwodstart.ipl synchronize_workarea_assets',
the deployment works good.

Thank you,
AMARESH

Adam Stoller

Put that command in a script - execute the script from the workflow. The script should check the return status from OpenDeploy and then make the appropriate callback to the workflow (all workflows should have error-handling tasks to which failed externaltask and cgitask processes can transition to so an administrator and examine the problem, attempt to resolve it, and then push the work back to where it originally failed).

If you don't want to figure out how to develop and error-handling task - you can always just callback to the workflow with whatever will push the task to its next transition -- it's not solid design, but its the way a large portion of workflows have been written...

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

amaresh

hi fish.
Thank you for your suggestion. But see, when i can execute other .ipl files like iwsend_mail_new.ipl from the same location where the iwodstart.ipl is, why dont the work flow start invoking the iwodstart.ipl even when I pass the required parameters ie. the file name synchronize_workarea_assets.xml. I am right not not concerned about the task mannualy terminated. So do you think I should create the perl program to invoke the iwodstart.ipl. But I want the deploy to take place. Thank you.

AMARESH

nipper

that is because other scripts are meant to work directly from workflows. WFs sens information in the command line of scripts it invokes, WFs
also require special calls (Task->CallBack) when scripts complete. The WF will hang otherwise.

Take a course in WFs, you need it