How to handle Lifecycle Activity Sets that trigger based on date field in another region

[alijubran]

Here is a unique situation related to dates and regional offsets:

You have a new hire in Australia and the employment start date is 8/1/2019. Your Day 1 Activity set is triggered on the employment start date. The Workflow that handles the trigger evaluation is running as the system in Pacific time-zone. The system date is 7/31/2019 so it will not trigger the Day 1 activity set for the Australia Employee for another 17 hours (Australia is +10 hrs UTC, Pacific -7 hrs UTC). 

How have you handled this in your org avoiding a hard code for the timezone difference?

[Mahesh Krishna2]

Have you tried triggering the Activity Set by an event?

Typically when you have such a situation where you are dealing with multiple timezones using an event-based approach is more effective.

I have not specifically worked on the HR Activity Set but I am certain you can create a workflow to trigger it.

[Pradeep Waghmar]

Hi Aliubran,

This is interesting. Would you mind sharing how you manage to resolve this situation? Thank you. 

[Sreeja1]

Hi Alijubran,

Were you able to achieve to this scenario. We have a similar situation and can you please help if you have any resolution.

Thanks in advance,

Sreeja