You are viewing limited content. For full access, please sign in.

Question

Question

Issues with Timers keeping forms in Inboxes

Forms
Updated August 28, 2015
asked on August 26, 2015

With some of our processes we have timers set up to remind people to fill out a form. One of the issues we've seen is that when the timer is set off and the form that is sent to remind them is filled out, the process will be completed but the project stays in the Process Modeler and doesn't leave the inbox.

Here is an example of the inbox showing the process as complete, but because the initial email sent, (before the timer), wasn't filled out the process doesn't leave the inbox.

I'm just wondering is there something to add to the process modeler that can make a stop marked as complete if the process moves on?

0 0

Answer

SELECTED ANSWER
replied on August 28, 2015 • Show version history

Usually the only reason you would NOT want to interrupt the activity is if you just wanted to shoot a notification off to someone, but still leave the submission at the current user task. So you could notify a manager that the task has been sitting for x amount of days and they can check up on it, but the task still stays with the same user to complete.

In your case, that is not what you want so it needs to interrupt it.

0 0

Replies

replied on August 26, 2015

Can you attach a copy of your process modeler?

0 0
replied on August 27, 2015

Here's a screenshot of the process. Each timer will go to the HR manager in case the president doesn't get to it in time.

 

0 0
replied on August 27, 2015

I'm guessing that this is happening because on the timer settings you have not told it to Interrupt the Attached Activity. Can you check and see if that has been selected in your timer activities?

1 0
replied on August 28, 2015

I think we've set it to not interrupt the activity because we're scared to stop the process. Are there any downsides to interrupting the activity?

0 0
SELECTED ANSWER
replied on August 28, 2015 • Show version history

Usually the only reason you would NOT want to interrupt the activity is if you just wanted to shoot a notification off to someone, but still leave the submission at the current user task. So you could notify a manager that the task has been sitting for x amount of days and they can check up on it, but the task still stays with the same user to complete.

In your case, that is not what you want so it needs to interrupt it.

0 0
You are not allowed to follow up in this post.

Sign in to reply to this post.

Details
Related Posts
Loading ...