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

Task is no longer valid

Ottawa_IWOV

Hi All-

I am experiencing weird behaviour when testing my workflow

I have a usertask w/ 3 successors. The 3rd successors call a group task, the group task succesor is an end task

Whenever I click the successor for the grouptask in my usertask, a screen immediately opens up that says the task is no longer valid. Seems to be a pretty simple thing, not sure why I am that message..

???

Lucas Cochrane
lucas.cochrane@baucanada.com

Find more posts tagged with

Comments

nipper

Sounds easy enough, post your WFT.

By chance do you have a timeout ?
Maybe that is set to 0 ?

Or someone is f***ing with your mind and approving the task

Ottawa_IWOV

here is the XML

Lucas Cochrane
lucas.cochrane@baucanada.com

nipper

Which is the last know good step ?

Ottawa_IWOV

ReviewApplication

The first two successors work fine. Just the last one (to the grouptask - Close JobFile) produces the wonky results.

I guess if you want to go right back, the last know good task (with successors working thru ET) would be SetEO

Lucas Cochrane
lucas.cochrane@baucanada.com

Migrateduser

Whenever I click the successor for the grouptask in my usertask

It would help to know the exact path you are taking through this workflow. There are many twists and turns.

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

nipper

Just for fun, change the group task to a user task and make it only to only apply to yourself.

Also, what rev ? 5.5.2 ? You may have found *gasp* a bug.

I use push tasks like that (group task with only one place to go) in 5.5.2 w/o trouble.

Though I do mark the predicessor tasks as well as the successors.

Andy

Ottawa_IWOV

<usertask name="ReviewApplication" owner="user1" description="Evaluation Officer Reviews Application">
<areavpath v="/default/main/CCMC/WORKAREA/development"/>
<successors>
<successorset description="Proceed with SEP">
<succ v="GenerateSEPLetter"/>
</successorset>
<successorset description="Assign New Master Format Number">
<succ v="NewMF"/>
</successorset>
<successorset description="Don't Proceed with SEP">
<succ v="CloseJobFile"/>
</successorset>
</successors>
<activation>
<or>
<pred v="SetEO" />
<pred v="ApproveSEPLetter" />
</or>
</activation>
</usertask>

3rd successor, CloseJobFile, pops up a window that says the task is no longer valid. All other successor choices function as expected.

Here is the grouptask

<grouptask name="CloseJobFile" description="Close Job File for CCMC Evaluation" readonly="f">
<areavpath v="/default/main/CCMC/WORKAREA/development"/>
<successors>
<successorset description="End Job">
<succ v="End"/>
</successorset>
</successors>
<sharedby>
<user v='user1'/>
<user v='user2'/>
<user v='user3'/>
<user v='user4'/>
</sharedby>
</grouptask>

Lucas Cochrane
lucas.cochrane@baucanada.com

Migrateduser

You don't use <activation> tags, which is weird to me. I always use <activation> tags in my workflows - that allows me to control everything. I also use <inactivate> tags in every task that can be reached by an <or> condition. Which task does it think is no longer active? The usertask?

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

Ottawa_IWOV

It thinks the group task is no longer valid

Lucas Cochrane
lucas.cochrane@baucanada.com

nipper

right, try making it a user task assigned to you only (for grins)

BTW, you are certain the WF has completed ? File -> properties on a file to be certain (view
all jobs as well).

You may want to put the activate tags in the group task as Smitty suggested.

Andy