Concept: Time Zone and Due Date
You can set a due date for the business process as a whole, or on each business process step. The due date is the elapsed time from when the step starts until the step is complete. When you view the business process history, you can determine if appropriate action was taken on a step and if the step completed on time.
When you configure a due date on a business process step, Workday displays the due date of the step in the user’s local time zone if the user is located in UTC-1 or greater. Example: Ireland and Australia. This doesn’t apply to users located in time zones of UTC-2 or less. Example: Canada and New York
To determine a step’s due date, Workday uses the end of day (23:59:59) in the Pacific Time Zone (UTC-8) of the system and converts the due date to the user's local time zone.
We display the user’s local time zone for the due date in the:
- Awaiting Your Actionsection on the Workday Home page.
- My Tasks item.
- My Tasks item'sProcess History.
- Up Nextmessage.
- You have submitteddialog box.
- Due Datecolumn on theView Eventpage.
The functionality only applies to how we display the due date and not how the system calculates the due date.
If you set a due date on a business process step and you select the
Due Date Is Based On Effective Date
check box on the step or the business process definition as a whole, Workday might add 1 additional day to the due date based on how the system persists the effective date of the business process.Example 1:
Betty is based in San Francisco, California and she initiates a business process on 07/14/2024. On the business process definition, a
To Do
step has a due date of 1 Day
which means the due date is 07/15/2024. The To Do
step is assigned to Yumiko. She is located in Tokyo, Japan. Based on the UTC offset, Japan is in UTC+9. On the View Event
page, we display the Due Date
as 07/16/2024
to Yumiko. If Betty views the event, Workday displays 07/15/2024
as the due date for the To Do
step.Example 2:
The
Title Change (Default Definition)
business process definition has an Effective Date
of 06/13/2024
. On the Approval
step, the:
- Due Datefield is1 Day.
- Due Date Is Based On Effective Datecheck box is checked.
- Step is assigned to the HR Partner security group. James is an HR Partner based in Singapore. Singapore is in UTC+8.
Mike is located in Pleasanton, CA. On 06/13/2024, he initiates the
Title Change
business process. Workday sets the persisted effective date of the business process as 06/13/2024. The Approval
step’s due date is calculated as end of day on 06/14/2024 in Pacific Time Zone. When we reach the Approval
step, Workday converts the due date to the local time zone for James in Singapore.In Workday, we display the
Approval
step due date as:
- 06/15/2024for James in his local time zone, Singapore.
- 06/14/2024for the business process administrator in Pacific Time Zone.
In some cases we might add 1 extra day to the due date if the business process is initiated in a non Pacific Time Zone and the initiator selects a business process effective date. In the above example, a worker in Singapore initiates the
Title Change
business process and selects an effective date of 06/14/2024
. Workday persists 06/14/2024 as the business process effective date. When viewing the event in Workday, we display the Approval
step’s due date as:
- 06/15/2024to a user in Pacific Time Zone. (06/14/2024 plus 1 day.)
- 06/16/2024to a user in Singapore. (06/15/2024 plus 1 day.)