ynrajasekhar / lokad-sdk Goto Github PK

What steps will reproduce the problem?
1. Open LSSC (sample file is OK)
2. Click on the event button
3. Click OK (leaving all values provided by default)

Then, LSSC crash with the following error message (sorry, French version of
the OS).

************** Texte de l'exception **************
System.NotSupportedException: La collection était d'une taille fixe.
   à System.Array.System.Collections.IList.Add(Object value)
   à System.Windows.Forms.BindingSource.Add(Object value)
   à Lokad.Client.Forms.ManageEventsView._create_Click(Object sender,
EventArgs e)
   à System.Windows.Forms.Control.OnClick(EventArgs e)
   à System.Windows.Forms.Button.OnClick(EventArgs e)
   à System.Windows.Forms.Button.OnMouseUp(MouseEventArgs mevent)
   à System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons
button, Int32 clicks)
   à System.Windows.Forms.Control.WndProc(Message& m)
   à System.Windows.Forms.ButtonBase.WndProc(Message& m)
   à System.Windows.Forms.Button.WndProc(Message& m)
   à System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
   à System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
   à System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg,
IntPtr wparam, IntPtr lparam)

L3C must support the Excel export format as provided by Avaya.

// imported from
https://sourceforge.net/tracker/?func=detail&aid=2032632&group_id=186223&atid=91
6419

When trying to import data from an Excel 2007 spreadsheet the user
encounter the error "External table is not in the expected format."

This is due to a connection string change between Excel 2003 and 2007 as
described at
http://forums.asp.net/p/1286886/2475172.aspx

LSSC should be able to auto-select the correct connection string based on
file extension.

// imported from
https://sourceforge.net/tracker/?func=detail&aid=2169142&group_id=186223&atid=91
6416

Opening large files with L3C is relatively slow. We need to display a
progress status while the file load is in-progress.

// imported from
https://sourceforge.net/tracker/?func=detail&aid=2027108&group_id=186223&atid=91
6419

// same as another ticket for LSSC

The US edition of Sage named Sage Business Vision should be supported by
LSSC.

// imported from:
https://sourceforge.net/tracker/?func=detail&aid=2117891&group_id=186223&atid=91
6419

At the moment Forecasting add-in for Excel supports only Excel 2007. 

It might be a good idea to support Excel 2003 as well.

Please, star this issue in order to "vote" for it and receive any progress
notifications.

Currently, a week of data in L3C is loaded only if the week is finished,
that is to say if there is already at least 1 point available for the next
week. Yet, this behavior is very counter-intuitive with Excel, because it
means that if the sheet contains data up to Sunday 23h45, the week will
still be discarded: indeed a point has to be added for the "next" week.

This behavior is very annoying. Basically, if only a few points are missing
then the week should be included nonetheless - eventually adding an extra
zero at the end.

LSSC is basically a single report, we should add an "Export to Excel"
command in the file menu. In order not to rely on a specific Excel library,
we can generate a TSV file.

// imported from:
https://sourceforge.net/tracker/?func=detail&aid=2309085&group_id=186223&atid=91
6419

Subj.

Data is silently discarded when output range is smaller than the table with
forecast details.

We either need to add warnings for this situation or automatically expand
output range.

The view menu should provide toggling options to display/hide the various
columns of LSSC.

// imported from:
https://sourceforge.net/tracker/?func=detail&aid=2257619&group_id=186223&atid=91
6419

Base on the new "AddReport" web method that comes with APIv2, LSSC should
provide a way to dump the logs to Lokad in 1-click.

// imported from:
https://sourceforge.net/tracker/?func=detail&aid=2309094&group_id=186223&atid=91
6419

Currently, L3C is failing when the agent counts values are not present or
simply incorrectly provided. This is annoying for the customers. It would
be much  nicer if the retrieval was actually succeeding, eventually with a
warning concerning the agent data.

In the Lokad Settings panel of the LSSC config wizard, the password textbox
should be reachable with 2 tabs, yet, 3 tabs are needed. This behavior is
annoying.

// imported from
https://sourceforge.net/tracker/?func=detail&aid=1957228&group_id=186223&atid=91
6416

A template implementation must be provided to facilitate the design of new
inventory adapters.

It seems that data loading from Asterisk (through MySQL) is very slow.
Performance should be improved.


Reported by a user

====
I initiated that partial refresh process at 11:45 AM. I did not get any
error messages, however, the process is either running very slowly, or it
has frozen.

I'm not sure if this is because of the 512mb of RAM on this PC, it has
been upgraded to XP to make sure the OS was relatively current. I did not
get any temporary memory errors this time, however it appears that the
network traffic to and from my pc has come to a complete stop (According to
my Connection Status window).

The meter on the console that says "Retrieving call center data" is a
little less than halfway full. Then green bars have stopped right after the
letter "i" in the word retrieving), and haven't moved for at least 30 min.
====


// imported from:
https://sourceforge.net/tracker/?func=detail&aid=2342326&group_id=186223&atid=91
6419

Now that the IInventoryEditor has a SelectOne method, a "Test" button could
be added to the LSSC editor to validate the SQL connection string first
(before actually designing the SQL queries).

// imported from:
https://sourceforge.net/tracker/?func=detail&aid=1960121&group_id=186223&atid=91
6419

Along with the tags, the user should be able to filter their products/SKU
through a plain text filter.

// imported from:
https://sourceforge.net/tracker/?func=detail&aid=2256675&group_id=186223&atid=91
6419

Currently, with LSSC, the user must manually select the SKU to be
forecasted. If the number of SKU is large, this task can become quite
lengthy.

It would be nice to provide a tool where the user could select the top N
most sold SKU to be forecasted (because users are usually interested in
forecasting highest sales volume SKUs).

This could come as a dialog box triggered from the Tools menu.

When the "AgentCount" column is not filled in the Excel spreadsheet, the
user end-up with an obscure error message saying that "One or several
required parameters are missing". Obviously, we need to provide more
meaningful error messages.

Then, it would be better if it was possible for the customer to exclude
entirely the AgentCount column when the data is not available.

// imported from
https://sourceforge.net/tracker/?func=detail&aid=2709881&group_id=186223&atid=91
6416

Currently, LSSC does not support user friendly error message (it's directly
the raw exception messages that get displayed). LSSC must support "user
friendly" error messages.

// imported from:
https://sourceforge.net/tracker/?func=detail&aid=2256615&group_id=186223&atid=91
6419

There are deprecated URL references in the code
http://lokad-sdk.googlecode.com/svn/trunk/dot-net/Api/Lokad.Api.Core/LokadApiReq
uestLimits.cs
(due to the migration toward Google Code)

Current graphical resources (ex: illustration in the AboutBox) are just
placeholder illustrations. Those illustrations need to be replaced by
Lokad-specific illustrations.

// imported from:
https://sourceforge.net/tracker/?func=detail&aid=1934177&group_id=186223&atid=91
6419

// same is for L3C

Report be saved
- when the refresh is triggered.
- when the refresh completes.

// imported from
https://sourceforge.net/tracker/?func=detail&aid=2119731&group_id=186223&atid=91
6419

Currently, the user is "scared" away (through dialog box message) of
closing LSSC while the wait is in progress. Yet, it would be more practical
if the user could close the application, and if the process was naturally
resumed next time LSSC is opened.

// imported from:
https://sourceforge.net/tracker/?func=detail&aid=2027583&group_id=186223&atid=91
6419

Reported by a user

===
I tried running Lokad again, this time I got an error
message stating: "Exception of type
'Lokad.CallCenter.Common.ValidationException' was thrown". However, after
this error message was displayed (in the Loading "progress bar"), the bar
continued to fill. When the progress bar got about halfway full, it began
again from scratch and then it seemed to freeze up (similar to the problem
I
was having originally).

Tried it again, this time using a calling period of only 2
hours (9AM-11AM) in hopes that the reduced "workload" might help. This did
not seem to have any positive effect.
===

Currently tags are treated like raw strings. It would be much better, if
tag autocomplete was provided.

// imported from:
https://sourceforge.net/tracker/?func=detail&aid=2256730&group_id=186223&atid=91
6419

Currently, the user has to specify values for past and future periods. This
choice might be a bit tricky because the value future periods value, if set
too low can actually "damage" the quality of report.

Thus, those two settings should be assigned to default (meaningful) values
bound to the chosen "Period". Then, the user should be "discouraged"
(somehow) to change those settings (making them part of the "advanced"
settings").

// imported from:
https://sourceforge.net/tracker/?func=detail&aid=1952381&group_id=186223&atid=91
6419

When queue settings are changed, there is no immediate effect. This
situation is a bit disturbing, because the user is expecting some
feedback.

Then after changing the queue settings and re-downloading the forecasts,
computed agent counts appears as "manually modified".

The correct behavior would be to recompute and redisplay the form
on-the-fly. In particular, the values have not been manually modified
should be directly be set to the newly computed values.

// imported from
https://sourceforge.net/tracker/?func=detail&aid=2025883&group_id=186223&atid=91
6416

Currently LSSC does not support custom proxy settings - as a result, some
users do not succeed at connecting with Lokad servers.

// imported from
https://sourceforge.net/tracker/?func=detail&aid=2127885&group_id=186223&atid=91
6419

// could be implemented at the shared codebase for reuse

A customer is reporting a failure with QuickBooks Canada Multicurrency. See
the attached file.

// imported from
https://sourceforge.net/tracker/?func=detail&aid=2758208&group_id=186223&atid=91
6416

Just noticed that the documentation produced at
http://build.lokad.com/doc/shared/
is including the docs for 3rd party assemblies such as autofac, cecil, log4net.

It would be better if those tools were excluded from the sandcastle output.

Call center managers need for the next quarter / semester
- average calls per day
- total calls per month

Thus, L3C should deliver those low-frequency forecasts, in addition to the
high-frequency forecasts.

// imported from:
https://sourceforge.net/tracker/?func=detail&aid=2091004&group_id=186223&atid=91
6419

It seems that when the add-in is updating itself, it interrupts the loading
of Excel. This behavior is really annoying, because you do not want Excel
to be interrupted by anything when you open a spreadsheet. It would be much
better if the add-in was updating in the background.

It appears that the dates generated in the SQL queries always follow the
pattern "yyyy-mm-dd"; yet, certain OleDb or OBDC adapters do not support
this format (ex: Sage Line 50). Thus, we need to provide an optional date
format if a custom formatting needs to be applied.

// imported from:
https://sourceforge.net/tracker/?func=detail&aid=2042613&group_id=186223&atid=91
6419

Currently, the logic to enable/disable control availability is rather
messy. This would need to be cleaned-up.

// imported from:
https://sourceforge.net/tracker/?func=detail&aid=2041872&group_id=186223&atid=91
6419

The waiting time must be adjusted to the number of queues. More queue means
a longer waiting time (to ensure a proper accuracy).

Forecasting tasks should deleted if and only if the task definition has
been changed in the report settings.

Currently, the tasks do not get deleted unless a "Clear Account" operation
is performed.

What steps will reproduce the problem?
1. Edit task
2. Hit "Cancel"

Task should stay in its initial state, it is deleted instead.

Extract from the support:

> I looked at my account after I uploaded the excel files 
> and I think I had them in the wrong format - I used 
> product as a column instead of a row.

As a result the user uploaded 700 empty series to Lokad. Large number of
empty series are pretty much the sign that something is wrong in the data
layout.

I would suggest
- prevent upload of empty series in the addin.
- warn user (not sure about the GUI) if there are more than say 25% empty
series.

Currently, we are only supporting a an *horizontal* while importing data
from Excel in LSSC. This layout is practical for DB import, but very
painful for "manual" import.

Thus, we need to support both layout. The horizontal layout expects the
product names or IDs to be put in the first column, and then one column per
date.

The bitmaps that decorate the Configuration Wizard of LSSC are now cropped.
It's purely aesthetic, but still a bit weird.

// imported from:
https://sourceforge.net/tracker/?func=detail&aid=2629544&group_id=186223&atid=91
6419

Customers are asking for a more convenient way to edit all queue settings
at once. Currently, the user has to navigate to to each queue to adjust the
settings, whereas our users are asking for a way to adjust all settings in
a single view. I guess that a GridView would be fine, with the ability to
cut-and-paste from or toward Excel.

// imported from
https://sourceforge.net/tracker/?func=detail&aid=2684888&group_id=186223&atid=91
6419

For now, the forecast errors are reported as [0, 1] values by the Excel
add-in which can be confusing for the users that are not familiar with
percentages. It would be better if the percentage formatting was applied to
the cells containing the forecast errors.

Cut and paste lines in LSSC for mass update
http://www.lokad.com/lssc-user-guide.ashx#Mass_update
is just too difficult to handle for unskilled users (i.e. people that have
never used keyboard shortcuts in their entire live).

Thus, it would probably be best to add a "Mass update" menu item that would
provide operations such as "Update all services levels" and "Update all
lead times".

Currently, when the user is canceling the update of the Excel add-in
(because it's slowing down the start-up of Excel), the add-in retries to
update itself on the next launch of Excel which is quite annoying. It would
be nicer if the add-in wasn't making more than one attempts total per week.

Opening a large LSSC report file is going to be a long operation (more than
a few seconds), thus it would be much nicer if the File->Open operation had
its own progress status (either dialog or main report progress bar).

Ideas: the time to load the report file can be easily "guessed" from the
size of the file.

// imported from:
https://sourceforge.net/tracker/?func=detail&aid=1932993&group_id=186223&atid=91
6419

Since the option of multiple tasks per series is now deprecated, the idea
of specifying a task name is deprecated too.

We should remove the task name option from the configuration wizard of LSSC
and L3C.

For some reason the progress bar of LSSC is blinking (and the visual effect
is rather annoying) during the async works (probably because being
"touched" too frequently no sure). As a cosmetic fix, it would be better if
the progress bar wasn't blinking that way.

// imported from:
https://sourceforge.net/tracker/?func=detail&aid=2495852&group_id=186223&atid=91
6419

Since async operations cannot be executed concurrently, controls are
disabled when an async operation is in progress.

Currently, the logic relies on the progress bar settings which is an ugly
hack. This behavior should be properly refactored.

// imported from:
https://sourceforge.net/tracker/?func=detail&aid=1951801&group_id=186223&atid=91
6419