Question

Extend Timer Catch Event

Forms

Updated June 1, 2020

asked on August 8, 2017 • Show version history

Hi All,

I have a client using forms to create Work Orders.

Within these forms, they have a notification alert date, which is used as a variable for a Timer Catch event. Once the timer catch event date/time is reached, admin is notified via email that the Work Order is overdue.

Now the client has a request to extend this notification alert date whilst the job is still in progress. For example, they may have an open Work Order that has been granted an extended Due by Date.

Currently, if they enter the form and manually extend this due by date, it terminates the entire workflow and gives a red cross on the Timer Catch event.

Is there another way or a work around for this to be a possibility?

Thanks :)

0 0

Replies

replied on August 8, 2017

Hi Shane,

A timer's end date is defined when it starts running, and there is no way to extend it.

A workaround I could think of is to terminate current timer and start a new one when client requests to change extend date using a user task, like this:

0 0

replied on August 8, 2017

Hi Rui,

Gave this a shot, however, as soon as the original overdue timer variable has changed, it seems to want to terminate the entire workflow.

overdue timer.PNG (132.84 KB)

| Download

0 0

replied on August 8, 2017

The history I got was like this, the timer should be interrupted instead of terminated:

I have never encountered issue like running timer gets terminated after approving user task. Will the timer be terminated if the date variable is not updated in user task?

If that's the issue, can you open a support case and provide your process to us?

0 0

replied on June 1, 2020

Hi,

It is a real shame that Laserfiche timer events don't use living variables.

Another work around (which works for extensions, it does not work if you're bringing dates forward) is to put two or more timer events in series using the same variable.

Timer 1: Trigger on DateVariablA (1st of June)

Timer 2: Trigger on DateVariableA (Updated to be 3rd of June)

When 1st of June rolls around the timer proceeds to the next step and discovers another timer with the same variable but now set with the updated variable of 3rd of June. It waits until this date before continuing.

Add as many timers as you expect changes in your processes.

If the DateVariable is unchanged, all timers proceed without error.

If the DateVariable is set to be earlier, the first timer will be stuck with the first variable and thus it will complete only on the original date specified (as it isn't a living variable), all subsequent timers will proceed without error (as the date has already passed).

As mentioned above, for both HR, Legal, Property Management, Records Management.. basically every type of "case management" this variable being "living" with an hourly or daily refresh rate would REALLY improve the usability of Laserfiche Forms.

For now we just have to deal with a poor user experience.. and some embarrassing notifications when "things change" for employees who have their departure date extended.

0 0

You are not allowed to follow up in this post.

Question

Question

Extend Timer Catch Event

Replies

Sign in to reply to this post.