Capture Recurring Events as Timesheet Entries

Capture Recurring Events as Timesheet Entries

We implemented Timesheets over a year ago and have yet to realize its true value, due to the fact that we cannot capture recurring events.

Our engineers have many recurring meetings that we are syncing via Salesforce for Outlook. We want to capture these types of events in our timesheets. If these times aren't represented then it makes it hard to identify how utilized the engineers are, essentially making the Timesheets useless.

We were told this feature is in the product backlog. Please vote this up so this can be acted on added to Time Entry capture for Timesheets.

What is the underlying problem do you intend to solve with this idea?
Obtain complete view on Engineers' untilization
How is the problem being addressed today, if at all?
combining data from other sources and making estimates.
Product Area?
Timesheets
What version of ServiceMax are you on?
18.3
1 Comment
Product Team
Product Team
Status changed to: Active
 
In order to better understand your requirements, I have a couple of questions regarding your use of recurring events for your technicians:
 
  • Do you use Salesforce Events or ServiceMax Events in your org?
  • When using Salesforce for Outlook, is each instance of the recurring event synced to the technician's calendar? Meaning, does the technician see that event on their calendar in SFDC every time it recurs? Or does it only show up once and have some kind of indicator as being "recurring?"
  • Is your timesheets module configured to process both work detail lines and events? 
  • Are you expecting timesheets to be created/processed for recurring events, even if those events are in the future and not part of the current week?
 
The good news is that the Timesheet module in ServiceMax is currently capable of processing Events as Time Entries on a Timesheet. So if your recurring event is being integrated onto your technician's calendar as an event in ServiceMax, and your Timesheet setup has been configured to create time entries from events, then a recurring event should appear as a processed time entry in the current active timesheet for a technician. So that way, the current product offering works! 
 
What timesheets cannot currently do is generate timesheets into the future, or process time entries for all future occurrences of a recurring event in a single run. Timesheets are meant to be a reflection of "actual" time worked by a user, processed in the current week that a timesheet is active. This means that it will only be able to process the instances of a recurring event that happen within the timesheet's active window/week. This doesn't mean that the recurrences won't ever process into a timesheet, just that they will not be processed as time entries until a timesheet for their day has been created by the system. This is because timesheets are not meant to be used as an estimating/forecasting tool. 
 
I hope this helps in your understanding of Timesheet functionality. If I'm missing a crucial detail, please feel free to provide some additional insight into your objectives for capturing recurring events in timesheets.