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

Workflow validation - bad workarea

rocketman

Hi.
Im recieving the following error:

Invalid Workflow:
ERROR: Bad area" /default/main/..../WORKAREA/**** in task YYY

while this is correct - workarea **** does not yet exist, it will be created in the start task. Task YYY is not the start task, it is an update task much later in the workflow. Is there any way to work around this? Or turn this piece of validation off?

Find more posts tagged with

Comments

Adam Stoller

Set the workarea for that tast to be an existing workarea, and in the externaltask script (or cgitask script) that you use to create the workarea - after the new workarea is created - then set the workarea associated with that task to be the new workarea.

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

rocketman

Ghoti-
thanks for the advice, but i'm a little confused. Perhaps I was not clear in my describing my problem.
I have built the workflow to operate in the following way:

1.external task - create a branch and workarea specific to the job
...
...
user tasks, group tasks - import code/files, etc...
...
...
submittask - submit to staging
updatetask - copy the files that have been imported into the branch/workarea created in the first task.

when the workflow is instantiated, it is throwing the error on the final task b/c the workarea created in the first task does not exist yet

Migrateduser

What ghoti suggested will solve your problem, and is probably the only way to solve your problem. In your updatetask, instead of the workarea that isn't created yet, initialize the value of this path to a known existing workarea. Then once you create the new workarea in your initial externaltask, use the tools available in the WFtask module to rename the areavpath of the updatetask to the new area. The workflow instantiator evidently verifies all the areavpaths in the job spec prior to allowing a job to instantiate. This will get you around that verification.

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

nipper

I am confused, when the job starts is there a WA ?

in the external task use some generic existing WA & use the new WA in the steps
after it was created. (I am not certain if this will work, I assume the WA vailidation is
done at task execution, not at the job instanciation.

If it does not work, can you put the WA creation logic in the Perl preprocessing
of the WF ? It can create the WA & then complete the XML. That will work.

HTH, say hi to elton for me.

Andy

rocketman

Smitty-
got it. I think I just didn't understand the way Ghoti worded it.
makes sense.

Thanks all!

JonathonG

Now that's got to be some kind of record...Smitty explaining something more clearly than ghoti Smiley Wink

Jonathon
Independent Interwoven Contractor

Migrateduser

Hey now, every dog has his day. Someone toss me a biscuit and take me for a walk.

And thank you for the opportunity to make a completely garatuitous post to boost my total.

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

Adam Stoller

Smitty ... catch! ... walkee time :-)

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

Migrateduser

Keep those biscuits coming or I'll pee on your leg!

Woohoo - another gratuitous post!

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