Since the Resolution Time business logic module does not take into account the timeslots of the customers the events came from, the Timeslot Events Sender business logic module and Resolution By Timeslots Extension library have been created. If your company is multinational and you are handling tickets that you need to resolve within a certain number of days in the customer's timeframe, you need to take the location of the customer who originated the ticket into account. The resolution time must take into account the time zone and timeslots of the specific location, which may be different from the location of the metric that does the actual calculation.
This module sends timeslot enter and timeslot exit events, using event reusability. To implement this module, the user must create a metric that includes it. Each sending metric should be specific to a location, and the name of the location should be part of the name of the metric. The metric must have the timeslot and time zone relevant to the location. It must also populate the single parameter called LocationId. The content of this parameter is the name of the location, as it will appear in the event details of the events relevant for this location.
Module Interface
The following table lists the parameter.
|
Name |
Description |
|
LocationId |
The unique name of the location for the metric. |
Module Dependencies
The following table lists the included modules.
|
Name |
Description |
|
Parameters Kernel Library (PKL) |
Library responsible for verifying and populating module parameters. |
|
Callback Kernel Library (CKL) |
Library that enables the callback functionality. |
|
Copyright © 2012 CA.
All rights reserved.
|
|