Share
ReportOur organization recently converted to SL Web Apps for timecards, for which I had high hopes as an end user. I am thus far disappointed. But before I start following up locally, I wanted to know if my ... well, my complaints were anything that could have been avoided or if they are baked into the app code. I actually have several - I hope it is okay to have included them all here!
1) The number of clicks to get to my timecard - counting login it takes navigating through several layers: Login->Project->Timecard Entry -> Current Entry. Is there a way to shortcut this for users, like me, who basically just mostly go to update their timecard? This is also true of the duplicating a timecard process (Project -> Timecard Entry -> TimecardHistory -> Actions -> Duplicate).
Could our local implementers create such shortcuts? Note that this is exacerbated by the fact that the system is really slow and each step has significant lag. That is almost certainly a local issue, of course.
2) Saving a timecard with an empty row, deletes that row. Assume I had 5 projects I charge against in week N. I submit that timecard and then create a duplicate timecard for week N+1. On Monday I only work on two of those projects. After I save the hours for that day, it removes the other three rows! I then have to either re-add them manually, or (what I actually did) reduplicate and overwrite the timecard and put in placeholder hours in the other entries that I eventually have to go back and fine tune.
Is there a setting our local implementers could enable to not remove empty rows on save?
3) Location of the daily summary. This line appears in the lower right corner while the timecard itself is in the upper left. I would prefer to have the summary line below the timecard, aligned by days. And if you resize the browser window to try to simulate that, you run into:
4) The page formatting gets somewhat confused when you resize the window - the vertical lines do not go back correctly . This might actually be a bug in SL Web Apps. I am current on my Chrome instance.
5) While I am on the topic of readability -
a) The summary line mentioned in #3 has a line running through the day/dates, making them hard to read
b) The day/date headings in the timecard are not being vertically centered, hence they are also harder to read than need be.
c) Gray scale only? I feel like a character from Cormac McCarthy's The Road.
Are any of these configurable?
TIA
All responses (
Answers (
290,552
