Joget Workflow v4 Training - Module 11 - SLA and Deadlines

All Rights Reserved © Joget Inc
Joget Workflow v4
SLA and Deadlines
http://facebook.com/jogetworkflow
http://twitter.com/jogetworkflow
Last Revised on March 2015Joget Inc Internal Use Only

Prerequisites
1. Good understanding on how to design a Workflow
Process.
Joget Inc Internal Use Only

Content
1. Service Level Agreement (SLA)
2. Deadlines

Chapter 1
Service Level Agreement
(SLA)

Service Level Agreement (SLA) Limit
• Why set limits?
– By setting limits to workflow activities, you are able to define
appropriate service levels for your processes.
– Participants in the workflow can be made aware of adherence to
these service levels.
– You can generate reports to determine the efficiency of your
processes e.g. identify bottlenecks, etc.

How to Set SLA Limit?
1. Define process-level duration unit
(Duration unit will be shared among activities in the
process)
2. Set SLA Limit on targeted activity or process

Define Duration Unit

Set SLA Limit
2-minute SLA Limit on “Approve
Leave” activity

SLA Limit Indicator

Service Level Monitor
• For activities that have defined limits, task assignments
will have due dates.
• When processes that have limits are deployed, you will
notice that the Service Level Monitor column in the Inbox
will display a colour coded square.
• The colour of the Service Level Monitor will change from
Green to Yellow as the due date approaches. Once the
due date is reached, the colour will be red.

Defining SLA Indicator
• Medium Warning Level
– Color: Yellow
– Default Value: 20% of elapsed time.
• Critical Warning Level
– Color: Red
– Default Value: 50% of elapsed time.
• Can be changed in the System Settings. (System wide effect)

• SLA Indicator will be seen in the task Inbox.
Service Level Monitor

Process Monitoring
• SLA Indicator is also available in the Process Monitoring
module for the administrator.

SLA Report on Userview
• SLA Report can also be made available for end user (e.g.
Manager) to inspect.
• Reference:
http://dev.joget.org/community/display/KBv4/SLA+Report+Userview+Menu

Chapter Review
• Set SLA limit to workflow activity, which enables the
implementation of service level monitoring.

Exercise
• Tweak the SLA settings to only turn to Yellow when half of
the remaining time elapsed and
• to red when all the remaining time runs out.

Chapter 2
Deadlines

Deadlines and Exceptions
• For each activity, a Deadline can be set.
• Deadlines act as a timer which triggers an Exception
transition to another activity when a specified duration
has elapsed.
Deadline reached
EXCEPTION

Deadlines
• Deadline execution can be synchronous or asynchronous.
• For synchronous execution, the current activity will no
longer be active when the deadline is triggered.
– Used in cases such as approval escalation.
• For asynchronous execution, the next activity will be
executed while the current activity is still waiting.
– Used in cases such as sending reminders.
• Multiple deadlines are supported for each activity.

Activating Deadline Checker
• The Process Deadline Checker needs to be enabled under
System Settings > General Settings
• This will enable periodic checks on activities’ deadlines as
defined by the checker interval.

Setting Deadlines and Exceptions
• Deadlines are set at activities.
• Exceptions are set at transitions.
• Both are required for the deadline feature to work.

Exercise: Setting Deadlines and Exceptions

Setting Deadlines and Exceptions
Asynchronous exception
When the “Send Email
Reminder” tool is started,
“Approve Leave” activity is still
active.

Process Monitoring
• Study on how deadline would affect your process instance
in Process Monitoring.
• Differentiate types of “state” of activity/process.
– closed.completed
– close.aborted
– open.not_running.not_started
– …

Exercise
• Verify that the deadline works as designed by mapping
the newly created Tool to a Email Tool plugin.
• Configure the Email Tool accordingly.
• Test if the Email Tool is triggered by the Deadline by
starting up a new process instance.

Exercise 2
• Add a second level approval for when the first level
approver does not respond in certain period, the second
approver will take over.
• Choose the appropriate time frame and type of deadline.
• Configure the new participant’s mapping accordingly after
deployment of the new process flow.

Good to know
• One activity may contains one or more Deadlines.
• Each Deadline has its own Duration Unit, unlike SLA’s.

Good to know
• It is also possible to set use a Workflow Variable as the
Deadline limit. (Remember to declare the Workflow Variable and
set the value according to the date format defined)

Good to know
• You may add in SLA Report Userview Menu to provide
users with insight of the state of process instances.
• See http://dev.joget.org/community/display/KBv4/SLA+Report+Userview+Menu

Important Note
• SLA will NOT manipulate the flow of your Workflow
Process, Deadline will.
• Deadlines will most probably NOT get triggered on the
dot as it depends on the Deadline Checker Interval cycle.
• Do NOT set deadlines on Tool, it’s only meant for
Activities.

Chapter Review
1. Set deadline and design exception handling.
2. Understand the difference between Synchronous and
Asynchronous deadline.

Module Review
1. Set SLA limit to workflow activity, which enables the
implementation of service level monitoring.
2. Set deadline and design exception handling.
3. Understand the difference between Synchronous and
Asynchronous deadline.

Stay Connected with Joget Workflow
• www.joget.org
• community.joget.org
• twitter.com/jogetworkflow
• facebook.com/jogetworkflow
• youtube.com/jogetworkflow
• slideshare.net/joget

Joget Workflow v4 Training - Module 11 - SLA and Deadlines

More Related Content

What's hot (20)

Similar to Joget Workflow v4 Training - Module 11 - SLA and Deadlines (20)

More from Joget Workflow (20)

Recently uploaded (20)

Joget Workflow v4 Training - Module 11 - SLA and Deadlines