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

calling a particular task repeatedly on time out.

TeamsiteUser

Hi,

I want to call a particular task in workflow file which sends e-mail to owners regarding the approval for the content submitted repeatedly for few times in case task remains stuck in the workflow when owner does not approve the content.

Can a particular task be the successor of itself?

Find more posts tagged with

Comments

Pawan

...Can a particular task be the successor of itself?

I assume you mean to say, a request for approval email is sent to the approvers to approve/reject.
You can specify a dummy timeout task alongwith the approver(usertask) task waiting for approval and on timeout you can have email task as the approver and loop again.

HTH

Adam Stoller

Hi,

I want to call a particular task in workflow file which sends e-mail to owners regarding the approval for the content submitted repeatedly for few times in case task remains stuck in the workflow when owner does not approve the content.

Can a particular task be the successor of itself?

If you're talking about individual tasks - you would have:

...(NotifyForReview)->(Review)->(<proceeed>)
           ^              |
           +<--timeout----+

So the task would not be calling itself.
If you're looking at a "ReviewTask" in WFM which combines both notification and the review step, you should be able to make it link back to itself on timeout, but I'm not sure that they accounted for that possibility when they designed the interface (in which case I'd file it with support as a bug) - note that the documentation indicates that "built-in" notification for Review Tasks only works if it is a user-task Review task, and not if it is a group-task Review task (sigh)