Process model deadline configuration

RE: Process model deadline configuration

jeanmichelm0001 — Tue, 17 May 2022 13:40:46 GMT

i am creating it just in case the related action was triggered and kept on hold without the user filling the form or submitting, I want the process to end so that there is no process engine running in the background.

The 15 mins is just an example, but it will be configured based on the business requirement

RE: Process model deadline configuration

Stewart Burchell — Tue, 17 May 2022 13:38:16 GMT

It won't block but you are now essentially creating a "race condition" - will the user complete the Task before the Exception trigger?. If the latter happens then the User will get a generic message from Appian that the Task has been completed (not very user friendly I know). I'm still not convinced this pattern makes any sense. If you're asking a User to complete a User Interface why is there a 15-minute time-sensitive window in place for them to do so?

RE: Process model deadline configuration

jeanmichelm0001 — Tue, 17 May 2022 13:35:33 GMT

Here you go

RE: Process model deadline configuration

jeanmichelm0001 — Tue, 17 May 2022 13:34:40 GMT

I tested this and it worked. but I am using chaining in the process and i am afraid the timer will block the chaining.

RE: Process model deadline configuration

Shubham Kumar — Tue, 17 May 2022 12:35:57 GMT

Hi Michel,

As I know the deadline works for the process model, not the interface. Could you please share some code or screenshot where you are enabling it?

RE: Process model deadline configuration

Stewart Burchell — Tue, 17 May 2022 12:32:46 GMT

Firstly: Deadlines on/in Process Models are just measures/provide metrics. You cannot use them programmatically to take action.

Secondly: what you're looking for is the Exception on the User Input Task node. You can set a time-based exception on the node and when the time threshold is reached you can have the process flow to the next logical step in the process (note: this doe snot have to be the end node and you need to ask yourself whether this is the correct thing to do - if you'd assigned a Task to a User for a purpose, does that purpose go away after 15 minutes? If not then the Exception is probably the wrong thing to be implementing.

Here's a screenshot of an implementation that matches what you described:

...but be very clear that this may not be what is actually required. Check your use case carefully!