[cisco-voip] UCCX Wrap up codes

[sarjot at googlemail.com]

Anthony thanks that makes sense.

Sarj
Sent from my BlackBerry® smartphone

-----Original Message-----
From: Anthony Holloway <avholloway+cisco-voip at gmail.com>
Sender: avholloway at gmail.com
Date: Thu, 16 Aug 2012 12:42:25 
To: <sarjot at gmail.com>
Cc: <cisco-voip at puck.nether.net>
Subject: Re: [cisco-voip] UCCX Wrap up codes

Sarj,

The best approach here is to pick a date, like the end of a month, and make
the change then.  Next, you would limit your reporting periods, to pre- and
post-change date ranges.  In my opinion, this makes the migration much
easier.

So for example (assuming an IT help desk):

You have wrap-up codes:
100 = Print & Fax and 101 = E-Mail

And on July 31, 2012 you switch them to:
100 = E-Mail and 101 = Print & Fax

Now, you would tell your reporting personnel about the change, and they
would never report on a date range which spans all of July and August.
They would instead, run a report which ends on July 31, and then run a new
report which begins on August 1, and compare them independently.  The
ability to continue to report on the pre-July 31st change will not last
forever, as the amount of storage used for retaining report data is
limited, and generally only nets you about 13 months.  What that means is,
at some point in the future, all traces of the old wrap-up codes will be
out of the system completely.

Anthony

On Thu, Aug 16, 2012 at 9:48 AM, <sarjot at googlemail.com> wrote:

> Hi All,
>
> We have a customer who want to change a number of Wrap up codes, but
> before doing this they wanted to know the impact on reports or any other
> functions of these were change.
>
> Any advice on this will be appreiciated.
>
> Sarj
> Sent from my BlackBerry® smartphone
>
> _______________________________________________
> cisco-voip mailing list
> cisco-voip at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20120816/b4204868/attachment.html>