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

Group Task Timeout

Bhargav Coca

Hello,
Working on Teamsite 6.1 on win2k3. I have a group task workflow, where the task is assigned to the group , and each and every individual in the group can take the task and approve it. If the task is not taken by any one, it lays there forever. I want a group task not taken timeout thingy here. Please anyone let me know how can i do this.
Thanks

Find more posts tagged with

Comments

Adam Stoller

Have you specified a timeout element for the grouptask?

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

Migrateduser

There are a few good ways to do this --

As ghoti mentioned, specify a timeout element first and then, depending on what you want to do in case of a timeout, have an external task email someone and then have it proceed to the original grouptask (with the timeout clock restarting, of course). This way, someone can get emailed after every 4 days or whatever that the group task has not been claimed.

Dave

Current Environment(s):
(1) TS 6.1 SP1 on W2K3
(2) TS 6.1 SP1 on W2K
(3) TS 5.5.2 SP2 on Win2K

Bhargav Coca

Yes, I have a time put element and a *.tpl for my email ( timeout), well my problem is , that i have tried including a timeout task between stages of "email approvers" and "group review". this group review has a timeout of its own, and this kicks in once any member in the group has taken the task and not approved. So what i have done is included a timeout in "email-approvers" external task. and calling the *.tpl using variables. I am sure i am doing wrong some where, couldn't trace it till now.
Suggest me where to include the time out...?
Thanks

Adam Stoller

Hmm - Well there was an old bug (#36437) which was related to timeouts on grouptasks not working until the grouptask had been claimed ownership of - but that was fixed back in 5.5.2L SP1 and/or 5.5.2 SP2 (see this thread - but unless that problem was reintroduced since then, it should still work.

Can you post the actual wft code for your grouptask?- and if you are using a variable for the timeout value - please make sure to provide an actual value of what that variable contains.

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

Bhargav Coca

here is the wft, Well the time out usually takes in user id and task #, if this is what you meant in you reply. I am using a task group_task_timeout, between the stages of email sent to the approvers and my group review. There is a group task review timeout in this code too, but i think that is not for my use give this scenario. Please suggest

Adam Stoller

This code looks very confusing - could you please enable workflow debugging (remove the highlighted '#' from the following code):#======================================================================
# Uncomment following line if you wish to enable workflow debugging.
#======================================================================
#debug();then run your workflow and set iw_debug_mode to True and make sure the file specification for iw_output_file is valid - fill in the other stuff you need to, and then click on Run Job. This should give you the "yellow & green" screen - but it will also write out a job description file to the location specified for iw_output_file.

Then post that (as an attachment) - I need to see how this workflow is really written - which is difficult in the WFT format (where it looks like you're specifying usertimeouts in grouptasks and grouptimeouts in other places, etc.)

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

Bhargav Coca

there you go sir, I see my variables going smoothly in the workflow. Lets see if you can find some error.
Thanks

Adam Stoller

Either they changed the way debugmode works - or you didn't provide what I asked for - it looks to me like you gave me the output from iwgetwfobj - rather than the actual job description file generated from your workflow.

The information also only contains a definition for an externaltask ("Email_Approver") and a usertask ("Approver_Review") - no grouptask is shown, in fact a whole bunch of tasks don'e seem to be shown.

Is this actually the output from debugmode or did you use iwgetwfobj? If the latter - please do the former. If the former - check out the green portion of the yellow-and-green screen you should have seen and copy / paste that into a file and attach that.

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

Bhargav Coca

I am sorry for the wrong file, here is the right one.
thanks

Adam Stoller

Hmm - okay - it looks like you have a 5 minute timeout set on the grouptask Group_Review, that transitions to the externaltask Group_Review_Timeout, which runs the iw_solution_email.ipl script and then transitions back to Group_Review -- depending on how long it takes the iw_solution_email.ipl script to do its thing and perform a callback - there should be very little noticable time between activations of the Group_Review task.

If the grouptask is remaining active with no email seeming to have been delivered there are two possibilities that I can think of:
1) The email simply isn't getting delivered and the transitions are working fine, or
2) The bug I mentioned earlier has returned and you need to report the problem to Support.

Probably the simplest way to test this out is to swap out the command in Group_Review_Timeout to a script that does NOT perform a callback - and see if the job gets hung in the Group_Review_Timeout rather than Group_Review -- if this is the case - the problem is #1 above and you'll need to debug why your email isn't working. If, on the otherhand, the job continues to be hung in Group_Review - then you should contact Support -- though it will speed up matters if you can reproduce the problem with a much simpler wft - one that has 3 tasks:
- Group_Review (as a start task - with one transition to End, and a 5 [or less] minute timeout to Group_Review_Timeout )
- Group_Review_Timeout (with a script that does not have a callback - provide the simplistic script too)
- End

Let us know what happens.

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

Bhargav Coca

Thank You very much.
I had an extra timeout task in it, and chaging some *.tpls, i could get the timeout working. Thanks once again