Power Platform Developer
Criteria for Importing Events from Outlook Initial Setup of Outlook Categories
Project Name: Timesheet Calendar Importer App
This app is a productivity tool that allows the user to quickly import their Outlook calendar events into their ServiceNow Timesheet for the current week.
- Only events that have a valid category assigned will be imported. All ServiceNow related categories must begin with a "#" prefix followed by text that matches a generic bucket (ex. "#Staff Meeting") or matches a ticket number such as a project or change request number (ex. "#PRJ123456").
- Events that are not categorized or have a category assigned that does not begin with a pound sign will be ignored/skipped.
- Only events where you are marked as "busy" or "out of office" will be included. If your status is marked as tentative or free then that event will not be included.
A one-time use script is available (windows computers only) that will automatically create for you categories that match all of the standard generic buckets in ServiceNow! It is strongly encouraged to take advantage of this to more easily utilize the app.
Normal Pattern of Usage
- User in Outlook reviews their calendar entries for the current week and insures all desired work-related events are tagged with an appropriate category matching a ServiceNow bucket.
- User loads the Timesheet Calendar Importer app
- User clicks button "Import Calendar". System will retrieve all matching events for the current week.
- User reviews/confirms list looks good.
- User clicks button "Submit to Time Sheet" to transfer the data into ServiceNow.
- User jumps to ServiceNow to review, finalize their timesheet for the week and submit.
Submitting to ServiceNow
Note the following rules will be adhered to when submitting data to ServiceNow.
- Time can only be transferred if your timesheet has not yet been submitted in ServiceNow.
- Only events that are categorized with a valid ServiceNow ticket number of generic bucket will be logged/added. When the system cannot match an error will be shown to the user to explain.
- If a user have multiple events with the same category for the same day, the system will total those hours automatically and be reflected in the timesheet for that day.
- When no timecard with that category/task exists for a given day it will be created.
- When a timecard matching that category/task exists on that day already, and hours match, no change will be made.
- When a timecard matching that category/task exists on that day already and the hours do not match, but was last updated by the API, the total hours will be overwritten to match the payload.
- When a timecard matching that category/task exists on that day already and the hours do not match, but was last updated directly by the user, the total hours will NOT be overwritten and an error will be shown to the user to explain.