I am trying out a simple nested workflow using the <wftask> element. I tested both the main and nested workflows individually and they both work fine that way. But when I utilize the <wftask> element as follows:
<wftask name="BrandMainExecuteDBAWorkflow"
owner="dsmit6"
description="Brand Main - Execute DBA Process Workflow">
<areavpath v='/default/main/wally_test/WORKAREA/int'/>
<successors>
<successorset description="Done">
<succ v="End"/>
</successorset>
</successors>
<wftfile v="/interwoven/iw-home/local/config/wft/nike/brand_dba.wft" />
<activation>
<pred v="BrandMainAuthorWork" />
</activation>
</wftask>
It appears to execute the <wftask> but the parent workflow is now stuck in a "waiting for nested job" state and I see no other workflows being created. I view all jobs and there's nothing. I read Brinko's response to another person who had this same issue and he said that the new workflow should appear in the ToDo list waiting for the owner to perform a "Start Task" on it. I don't see anything at all. Help!!
Dave SmithSr. Software Engineer
Nike, Inc.
(503) 671-4238
DavidH.Smith@nike.com
