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

Question

Question

Completed via terminate end event notification

asked on April 27, 2024 Show version history

TLDR: I want a termination notifications only if is not because of a Terminate End Event.

I have a flow that starts a timer on one branch, and assigns a task on another.

  1. If the task is completed, it goes to a terminate end even to also stop the timer.
  2. If the timer ends, it will go through a loop to check if another process is complete.
    • If not, it will loop back and start the timer over again.
    • If so, it will hit a terminate end event itself, and cancel the task that was assigned.

Is there a way to still receive termination notification if a "bad termination" occurs, but not if the process gets to Terminate End Event?

0 0

Replies

replied on April 28, 2024

Hi Justin,

You can configure the termination email notification in Process Options tab, and it will be triggered whenever the instance get terminated, including the "bad termination" you want to catch, have you already enabled it?

0 0
replied on April 28, 2024

Yes, but since every end event in the process is a Terminate End Event, I get a notification every time. I want to keep the notifications for unwanted terminations, but stop the notifications for Terminate End Events.

0 0
replied on April 28, 2024

well, not knowing what background your process design is, but I don't think you need to use terminate end event everywhere, a normal end event will do.

0 0
replied on May 2, 2024

While, yes, I could redesign the form to not include terminate events, I dont want to avoid ever using them because of these notifications. I would like to know if there was a way to turn these ones specifically off, or request that feature add if not.

0 0
replied on May 2, 2024

Terminate End Events are meant for the error cases where a process does not go according to plan and somebody would need to address the problem. As such Forms (and Workflow, for that matter), don't distinguish between instances that terminate because the user designed it with a Terminate End Event or because of a system error. They get treated the same when reporting out through the termination notification.

I can see how it could be confusing that having the process end when the timer goes off is not considered a "bad termination". The process does go according to plan, even though it's not the "happy" case.

0 0
replied on May 2, 2024

To add a little more context here, I use the Terminate event in a few specific places because it cancels any other in-progress activities. That's a good use for it. Is there a way to get that functionality without it being treated like an error?

I, too, would prefer not to get error notifications for these situations where everything behaves as I have designed and intend.

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

Sign in to reply to this post.