
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎08-31-2015 01:30 PM
We're looking to allow our project workers the ability to create Time Cards as well as make the Week starts on field editable so they can capture things like admin work, training, etc, This would also allow them to go back and create time cards in case they forgot to create one. In the Access Control time_card.week_starts_on in the description it says "This field's value is calculated, and therefore cannot be modified manually.". Are there any consequences in doing what I'm proposing and how have other people captured admin tasks and creating past time cards if a worker forgets to do one?
Thanks,
Aryanos
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎08-31-2015 08:37 PM
I can't really think of a truly negative outcome of what you are considering. The week_starts_on field is a date field that defaults to the start of the current week as defined per the properties (Sunday, Monday, etc.). It can be changed to any valid date, even one that technically isn't an actual week start. So you could end up with some randomness in the Week_starts_on field if end users fail to pick a valid week start date. However, if you do not care to have accurate reporting on hours submitted to the day, then you may still be ok. As an example, if your utilization reports or time submission reports are configured to report on time cards submitted within a given quarter, or a month, or even a week, then having time cards with odd week_starts_on dates doesn't really matter, we look at the big picture and aggregate all hours reported for the given month, quarter, etc.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎08-31-2015 06:20 PM
Looking at the Properties on the day of the week calculations should start, it says: What day should time cards start on, default is Sunday. Changing this value may create duplicate time cards for the week of the change, since time card queries are based on this value.
So allowing users to set their own values could result in duplicate entries is how I read it.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎08-31-2015 08:37 PM
I can't really think of a truly negative outcome of what you are considering. The week_starts_on field is a date field that defaults to the start of the current week as defined per the properties (Sunday, Monday, etc.). It can be changed to any valid date, even one that technically isn't an actual week start. So you could end up with some randomness in the Week_starts_on field if end users fail to pick a valid week start date. However, if you do not care to have accurate reporting on hours submitted to the day, then you may still be ok. As an example, if your utilization reports or time submission reports are configured to report on time cards submitted within a given quarter, or a month, or even a week, then having time cards with odd week_starts_on dates doesn't really matter, we look at the big picture and aggregate all hours reported for the given month, quarter, etc.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎09-01-2015 09:48 AM
Hi Anna,
My manager is looking to have Time Card reports weekly, monthly, quarterly and yearly and I'm researching how Time Cards work in ServiceNow for him. One thing he's inquired is if it's possible to get a report on the Time Worked [task_time_worked] table that sums up all the time for a worker? If we do are report on the Time Card [time_card] table we can get the total for all the worker's time cards but don't see the tasks.
I'm a little confused on how other companies are reporting on Time Cards and the Time Worked. Ideally we'd just like to have one Time Card per worker and have all the tasks, incidents, project tasks listed under it but that doesn't seem possible out of the box in ServiceNow.
Thanks,
Aryanos

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎09-01-2015 10:01 AM
There is a property setting that you can turn on: