Exception Processing with Timer and Rule

RE: Exception Processing with Timer and Rule

helmuta0001 — Tue, 04 May 2021 16:31:46 GMT

Thanks! I will look into the advance option.

RE: Exception Processing with Timer and Rule

Chris — Tue, 04 May 2021 16:30:58 GMT

Yes, the timer will only fire if all advanced conditions are true(). Sounds like that could be your issue.

RE: Exception Processing with Timer and Rule

helmuta0001 — Tue, 04 May 2021 16:29:34 GMT

I did find an advance option in the timer. It is checking if a boolean variable is true. If the variable is false will it not fire the timer?

RE: Exception Processing with Timer and Rule

helmuta0001 — Tue, 04 May 2021 16:23:53 GMT

It is an interface that gives the user an option of clicking on one of three links. Since that will change the screen for the user the node needs to timeout to terminate and is the rule isunlock is true it should terminate as well.

RE: Exception Processing with Timer and Rule

helmuta0001 — Tue, 04 May 2021 16:22:02 GMT

Same node. User Input that when one of the two fires should terminate.

RE: Exception Processing with Timer and Rule

Chris — Tue, 04 May 2021 16:21:11 GMT

Additionally, in a stuck instance, can you verify that pv!isUnlock is true(), and this node is still active?

For the Timer, are there any Advanced Options configured?

RE: Exception Processing with Timer and Rule

Mike Schmitt — Tue, 04 May 2021 16:19:21 GMT

are these configurations both on the same node or on separate nodes? what type(s) of node are they contained in? what does the process flow do after these are executed - does it just go to a terminate node, or something else?

RE: Exception Processing with Timer and Rule

helmuta0001 — Tue, 04 May 2021 16:14:49 GMT

This is one of the configurations that I can share.

This the rule portion

This is the timer. We are using a constant for the number of minutes

RE: Exception Processing with Timer and Rule

Mike Schmitt — Tue, 04 May 2021 16:04:19 GMT

Redacted screenshots of process instances would work well and should be easy to produce (my favorite freeware screenshot tool, "Greenshot", has this built right in).

If all else fails, you might be able to reproduce the issue in a separate/new process model with no sensitive information contained in it.

RE: Exception Processing with Timer and Rule

helmuta0001 — Tue, 04 May 2021 16:01:17 GMT

Thanks Chris. We will take a look. Unfortunately, I can't share a lot more information because of the client's security requirements.

RE: Exception Processing with Timer and Rule

Mike Schmitt — Tue, 04 May 2021 16:00:36 GMT

I agree with Chris above, this might require some sort of screenshot showing how and where your process instances are stuck.

Just a hunch (but not sure if this is directly related), instead of using an AND() statement in a rule node, you should just add separate expression inputs for each part, since the rule already functions like AND(). This is partly because the AND() function itself has a quirk (last i checked) where it will evaluate NULL values as if they're TRUE, causing unintended side-effects sometimes. My suggestion here merely simplifies this somewhat.

RE: Exception Processing with Timer and Rule

Chris — Tue, 04 May 2021 15:53:46 GMT

We use this type of setup and I haven't had any issues with it. I would say it is standard practice to have a few exceptions on a User Input Task. Are you able to verify in a 'stuck' process by monitoring, that the variable values are false for pv!isManageSubmit and true for pv!isUnlock, where the exception should be firing but it is not?

If you are able to share screen shots of the variables when monitoring, and the exception configurations, that would be helpful.