shaunw wrote:
Hind sight is 20/20 for this one, the Flash interface was already being developed when iPhones were just being released and HTML5 was a pipe dream, obviously the landscape has changed significantly since then and the Flash interface is being phased out in favor of a pure HTML5 interface (currently in testing) that will be accessible from all smart mobile devices.
I look forward to seeing how the new interface looks!
Unfortunately this is caused by the additional flexibility in the reporting engine and the fact that future schedule data doesn't actually "exist" in the database. We have plans to revamp the entire recurring schedule system to make way for additional features and doing so will resolve this issue in the process, though likely with the new side affect of being limited as to how far in the future the recurring schedules will display.
We are open to feedback as to how far in the future users are wanting to see their schedules for.
I can say from the administrative team, we look out 90 days on schedules on a regular basis, and we will periodically pull up ALL holiday dates to see what our schedules look like (which can mean looking out up to 1 year). The Schedule interface gives us some of this info, But it only exports/prints as a PDF. If we were able to export it in a data/csv format then we could do our own pivot tables or summary reporting on it.
Our agents will want to be able to do the same. Some employees have 2 or 3 week rotating schedules and they want to find out if they will be scheduled on specific dates in the future (holidays, weddings, etc...). For this scenario they are happy to use the schedule interface (as opposed to the Schedule Summary Report).
The permissions around this will likely need to be reconsidered to be made more flexible, unfortunately its a little used feature and isn't a high priority at this time, but it will be corrected at some point.
Is there a reason to not allow regular employees to edit their City (but they can change their street address)? For an area such as ours, this is a problem. Right now, we're having to have people issue requests to have their own contact info updated when we'd MUCH rather allow them access to do this on their own.