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

TS 6.1 workflow error

Ottawa_IWOV

All-

I am encountering some weird behaviour in TS 6.1 workflow. I have set-up a group task in which I am the owner. But I am unable to take ownership of the task in workflow. I get permission denied errors. I assume I don't have to be part of the <sharedby>...</sharedby> element as well?

Any thoughts on this one. BTW, it is part of a nested workflow.

Thanks,

Lucas.

Lucas Cochrane
lcochrane@itnet.ca

Find more posts tagged with

Comments

Dwayne

Yes, you most certainly do need to be a part of the <sharedby> element. Setting the owner="..." attribute in the WFT for a grouptask would do absolutely nothing. It's not used.

As far as I know, this has always been the behavior.

--

Current project: TS 5.5.2/6.1 W2K

Ottawa_IWOV

DO you know how to call a wft file from the
<wftfile>...</wftfile> element. I am trying to call the wft from the TeamSite server (i.e. /iwmnt/...) but if can't find it. Is this supported?

Lucas Cochrane
lucas.cochrane@baucanada.com

Dwayne

I've never attempted that before, but I don't know of any technical reason why it shouldn't work. The only thing I can think of is permissions. Does the user who owns the wftask have read access to the wft file, and read/execute permission for all of the directories from the root down to the directory that contains the WFT?

A (pared down) example of the parent WFT, as well as the text of any error message, might help with diagnosing the problem

--

Current project: TS 5.5.2/6.1 W2K

Ottawa_IWOV

Here is the workflow:

<workflow name = "CCMC_Eval" owner = "admin" creator = "__TAG__('iw_user');" description = "CCMC Evaluation Dev">

<endtask name = "EndTask">
<activation>
<or>
<pred v = "AppReview"/>
</or>
</activation>
</endtask>

<wftask name = "OpenJob" owner = "__INSERT__($sUser);" start = "t" description = "Open CCMC Job File">
<areavpath v = "__INSERT__($sWorkArea);"/>
<successors>
<successorset description = "Go to AppReview">
<succ v = "AppReview"/>
</successorset>
</successors>
<wftfile v = /iwmnt/default/main/CCMC/WORKAREA/development/workflow/ccmc_open_job.wft"/>
__INSERT__($iw_selected_files);
</wftask>

<wftask name = "AppReview" owner = "__INSERT__($sUser);" start = "f" description = "Review Application">
<areavpath v = "__INSERT__($sWorkArea);"/>
<successors>
<successorset description = "Go to EndTask">
<succ v = "EndTask"/>
</successorset>
</successors>
<wftfile v = "/iwmnt/default/main/CCMC/WORKAREA/development/workflow/ccmc_app_review.wft"/>
<activation>
<or>
<pred v = "OpenJob"/>
</or>
</activation>
</wftask>

</workflow>

Lucas Cochrane
lucas.cochrane@baucanada.com

Dwayne

The only thing that jumps out at me right away is this line, and I assume this is a cut/paste error, rather than an actual problem with your WFT file:

    <wftfile v = /iwmnt/default/main/CCMC/WORKAREA/development/workflow/ccmc_open_job.wft"/>

You're missing the open quote mark. That it, it should read:

    <wftfile v = "/iwmnt/default/main/CCMC/WORKAREA/development/workflow/ccmc_open_job.wft"/>

Beyond that, I'll have to spend a little more time looking at it.

--

Current project: TS 5.5.2/6.1 W2K

Migrateduser

<wftfile v = /iwmnt/default/main/CCMC/WORKAREA/development/workflow/ccmc_open_job.wft"/>

You're missing the beginning double quote " at the beginning of the v= section. Also, when I use this tag, I do it this way:

<wftfile v="/interwoven/iw-home/local/config/wft/nike/brand_dba.wft" background="t" />

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

Ottawa_IWOV

The double-quote was just a cut and paste error actually.

Lucas Cochrane
lucas.cochrane@baucanada.com

Migrateduser

The big difference I see is that your WFT is in TeamSite where mine is not. Mine just lives with my other workflows in the place thay are expected to be. Do you have all your workflows under TeamSite control? I'm curious what happens if you point to the:

<iw-home>/local/config/wft/...

path for your WFT file instead of the TeamSite path.

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

Ottawa_IWOV

I am actually doing some development workflows from TeamSite because I can't access anything else (very sticky client).

Here is some interesting behaviour:

-From my main workflow, it seems to find the file in the WFTFILE because it display the TAG_INFO options, then when I click "Start" is complains that it can't find the wft file (debug mode). How weird is that???

Lucas Cochrane
lucas.cochrane@baucanada.com

Dwayne

Nothing is jumping out at me as being a problem. Can you include the text (or screenshots, if not too big) of any error message?

I am assuming that:

You've got code elsewhere in the WFT file that's defining the $sUser and $sWorkarea variables
Since this is Unix (at least, I'm assuming so based on the presence of /iwmnt) have you verified that the path is correct, including upper/lower case? I know that sounds like a dumb question, but you never know..

Current project: TS 5.5.2/6.1 W2K

lhdavis

Do you have the workflows listed in your available_templates.cfg file? Having not used the wftfile tag, I'm not sure if you need them listed there but that could be one reason why the workflow instantiator gets to the TAG_INFO but then doesn't find the workflow. Maybe. Possibly. Just a wild guess here.

Luke Davis
Open Technology Group, Inc.
luke.davis@med.va.gov

Ottawa_IWOV

here is a screen capture. just rename to a .doc file

Lucas Cochrane
lucas.cochrane@baucanada.com

Edited by Ottawa_IWOV on 08/16/04 11:11 AM (server time).

Migrateduser

That shouldn't be an issue. It should just do the right thing. I would add this to the TAG_info section of my nested workflow:

iw_output_file => "<input type='text' value='/tmp/my_job.xml'>",

and then run iwjobc on the /tmp/my_job.xml job spec. The error messages you get from the instantiator are ****. You get better error messages, usually, when you run a job spec through iwjobc. This is yet another thing Interwoven has negelected to fix for workflow over the years.

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

Migrateduser

What are the permissions on your WFT in TeamSite? Go into a shell and do an ls -l on it and paste the results here.

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

Ottawa_IWOV

$ ls -al /default/main/CCMC/WORKAREA/development/workflow
total 124
drwxrws--- 2 cochranel irc-users 512 Aug 17 11:44 .
drwxrws--x 6 traafat irc-users 512 Aug 16 09:27 ..
-rwxrwxr-x 1 cochranel irc-users 7742 Jul 13 09:42 ccmc_admin.wft
-rwxrwxr-x 1 cochranel irc-users 11830 Aug 16 10:29 ccmc_app_review.wft
-rwxrwxr-x 1 cochranel irc-users 0 Aug 16 09:27 ccmc_dev.wft
-rwxrwxr-x 1 cochranel irc-users 9342 Aug 17 11:44 ccmc_evaluation.wft
-rwxrwxr-x 1 cochranel irc-users 11873 Jul 9 10:58 ccmc_open_job_t.wft
-rwxrwxr-x 1 cochranel irc-users 11728 Aug 16 13:33 ccmc_open_job.wft
-rwxrwxr-x 1 cochranel irc-users 7723 Jul 13 09:41 ccmc_SEP.wft

Lucas Cochrane
lucas.cochrane@baucanada.com

Adam Stoller

The fact that neither '.' nor '..' have *both* read *and* execute bits set for 'other' users could be a source of the problem... (just guessing here)

FYI - there's no reason for the wft's to be listed as executable they should probably be either 664 or 644

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