Duration triggers

The duration triggers include:

  • Job Duration Triggers

  • Activity Due Date Triggers

Job duration triggers

A job duration trigger for a process is set up to execute when the set time period in relation to the expected job due date has passed. The Job Duration triggers help to monitor the progress of a business process and ensure timely escalations.

See Create job duration triggers.

Triggers are only executed for an active job; they are not executed if the job is on hold or completed. See the following table for an example.

Job Due Date

Job Escalation Date

Job Status

Current Date

Trigger Fired?

Yes/No

12.00.00 26.06.2013

12.00.00 26.06.2013

Job Alive

12.00.00 26.06.2013

Yes

12.00.00 26.06.2013

12.00.00 26.06.2013

Job Complete

12.00.00 26.06.2013

No

12.00.00 26.06.2013

06.00.00 27.06.2013

Job Alive

06.00.00 27.06.2013

Yes

Activity due date triggers

An activity trigger is set up against an activity due date.

See Create activity due date triggers.

For example, you may need an alert 2 days before an activity due date if no resource is picking up and completing the activity (which means the business process is not progressing as it should). There could be numerous reasons for an activity becoming overdue, the assigned resource may be overloaded with work or may be sick. Timely escalation helps in taking actions in time.

There could be numerous reasons for an activity becoming overdue, the assigned resource may be overloaded with work or may be sick. Timely escalation helps in taking actions in time.

An activity trigger is executed when the time period relative to the activity due date has past and as soon as the activity becomes pending or is taken. However, you can set the activity trigger to execute before the activity due date is reached. A trigger cannot execute for an activity that is either complete or on hold.

For example, you may need an alert 2 days before an activity due date if no resource is picking up and completing the activity (which means the business process is not progressing as it should).

For example, create the following triggers against the Notify Customer activity in a Loan Request process map.

Activity

Due Date

Target Firing Date

Escalation Process

Notify Customer

12.00.00 28.09.2012

+ 2 days

Loan Application

Notify Customer

12.00.00 28.09.2012

0 day

Loan Application

Notify Customer

12.00.00 28.09.2012

- 1 day

Loan Application

  • If the Notify Customer activity becomes pending at 12.00.00 26.09.2006, the trigger executes on the following dates.

    A

    27.00.2006 at 12.00.00 - when the trigger firing target duration is -1 day

    B

    28.09.2006 at 12.00.00 - when the trigger firing target duration is 0 day

    C

    30.09.2006 at 12.00.00 - when the trigger firing target duration is +2 days

  • If the activity is completed after the first trigger is executed, or after 27.00.2006 at 12.00.00, triggers B and C are not executed.