and more in a single search tool across platforms. Read the announcement here. |
08/10/2022 02:58 AM
Hi Team,
I have a scenario where I have to offboard users from all the applications they had access to based on their timezones. Let's say I'm importing details from the source of truth and it has a list of all users who are getting terminated for the day. Currently from the update rule that we have, it creates tasks instantly for all users who are terminated and they get executed in the next wsretry run (or) gets executed instantly if instant provisioning is enabled.
How do I make sure termination gets executed based on the user's timezone?
Thanks,
Siva
08/10/2022 04:20 AM
If we can store user's timezone in customproperty & use advanced query option in update rule
10/13/2022 12:42 AM
Hi Siva,
Did you implement time zone based offboarding in Saviynt? We also have similar client requirement. Can you please provide some more insights on the configurations done in Saviynt.
Thanks in advance !
Prajakta
10/14/2022 07:40 PM
let's assume users are imported from Workday or HRIS
You could make two terminated user import (US / NON-US - filter is applied on Workday RaaS or API level) and run this import job in different time. you can consider this option if user is imported from HRIS.
10/18/2022 01:18 AM
Thanks for the reply.
The offboarding should happen based on the timezone of the user. The employees are widely spread across 10 timezones. How to configure offboarding based on the user's respective time zone's end of working hrs.
10/18/2022 02:04 AM
In the past I have used the Saviynt for Saviynt (SfS) connector on a user import. The SQL query sets a 'Leaver' flag based on the user's country and end date. (The query contains a case statement, with a condition for each country.) A user update rule then picks up this flag has been set, and offboards the user.
A similar method is to have the same logic in the pre-processor of your HR connector (if all your users come from a HR source.)
The big disadvantage of these methods is the connectors needs to run regularly with a full user import, which if you have a lot of users might not be feasible. So, I'm looking for a better way of doing this.
10/19/2022 07:05 AM
Absolutely right. In terms of periodic execution, what would be the efficient way to handle this.
Also, how to efficiently identify the exact time on the end date w.r.t user time zone. Have you added all countries/timezones in the SQL query ? If not then in case of addition of new country, it will involve manual intervention to add country in SQL.
10/19/2022 11:36 AM
use LOCALE from users table
select LOCALE from users
10/19/2022 11:47 PM
Can you please elaborate. I am not clear how to leverage Locale
10/20/2022 12:10 AM
It is user localization i.e. language set by user to view own profile once logged in
10/20/2022 12:14 AM
I think there is some disconnect. The requirement is about triggering offboarding of user based on user's timezone.