TacticSheet Connection String And Timesheet Period
Rajiv Popat
Adding this to the the mailing list for future reference of others.
--
Rajiv.
---
From:
Rajiv Popat
Sent: dinsdag 6 november 2007 17:58
To: Frans Rampen
Subject: Re: TacticSheet
Hi Frans,
My Answers below:
> - at this moment multiple connectionstrings are used, even one compiled into the code! So that needs to be redesigned so you have to edit only
> one connectionstring. For now I have my sa account credentials matched to yours
Thanks for pointing this out. I'll try and fix this during the weekend.
> It's not clear to me how the timesheet edit screens are setup. Are timesheets based on weeks? So you give a date, fetch timesheets and this
> returns a timesheet for that week?
Yes, for now timesheet screens are based on weeks; primarily because most organizations I've looked at seem to be working on weekly timesheets. In future we intend on making this configurable to some extent so that administrators can decide if they want to allow weekly, bi-weekly or other time-periods. Also want to try and give a feature that allows administrators to end weekly timesheets by month-end if the month ends in the middle of a week. Some folks have told me that, it helps accounting invoice their clients if they have monthly billing.
(Given the current stage at which TacticSheet stands, I thought we would just support weekly timesheets for now and then come back to this feature and enhance it.)
It seems like most folks I've talked to tell me that weekly timesheets are what most organizations use. Would you agree? Do you see a strong need for making time-periods for timesheet configurable in your / other deployment scenarios?
Here's how the edit screens basically work:
In the current system we just let you pick a date and we fetch the timesheet for that week if it's already there ( i.e. if you had created it earlier). Whether you can edit it or not depends on multiple other scenarios like if the Timesheet is submitted or not. ( http://www.thousandtyone.com/blog/TacticSheetNewFeaturesAnnouncement1.aspx contains more details). If the timesheet doesn't exist, we create it for you.
> PS if you like I can send comments like this through the google groups..
Definitely! Having archives of these discussion there adds value for folks who might want to join and browse through these in the future. If you're ok I can go ahead and forward this email to the group so that it's archived there for future reference. You can directly send future emails to the group.
Thanks for your comments. Feel free to send in any others that you might have and we can discuss.
--
rajiv.
On Nov 6, 2007 5:41 PM, Frans Rampen wrote:
> Hello Rajiv,
>
> Thanks for the build. A couple of comments:
>
> - at this moment multiple connectionstrings are used, even one compiled
> into the code! So that needs to be redesigned so you have to edit only
> one connectionstring. For now I have my sa account credentials matched
> to yours
> - it's not clear to me how the timesheet edit screens are setup. Are
> timesheets based on weeks? So you give a date, fetch timesheets and this
> returns a timesheet for that week?
>
> Regards,
>
> Frans.
>
> PS if you like I can send comments like this through the google groups..
>
>
Frans
> what most organizations use. Would you agree? Do you see a strong need for
> making time-periods for timesheet configurable in your / other deployment
> scenarios?
I have used only monthly-based timesheets in the past. The
organization i worked for previously did use monthly timesheets with
an option to generate an authorization sheet for the weeks of this
month, detailed by days of week.
Frans
Rajiv Popat
It appears that in the long run we will have to make the time period in
TacticSheet configurable rather than the weekly timesheets we have for now.
I suspect this configurability won't make it into Release 1 however.
--
Rajiv.