Time stamps, for example, insert dates or modification dates, are stored in One Identity Manager with the respective UTC. The object layer transforms this time data into the currently valid time zone data when an object is loaded. The user, therefore, sees all the values in local time. When an object is saved the current time zone data is transformed into UTC data.
Countries and time zones are linked to another in the One Identity Manager schema. This makes it easier to find out the time zones when web fronts such as the Web Portal are in use.
Related topics
Working hours are calculated for various function in One Identity Manager. For example, to determine working hours in the IT Shop or for determining reaction and solution times for calls in the Helpdesk Module. Weekends and public holidays are taken into account when calculating working hours.
To determine the working hours
-
Ensure that a state and/or county is entered into the employee’s master data.
-
Public holiday are entered by state (county) in One Identity Manager. You can add separate public holidays for states.
-
To exclude public holidays from the working hours calculation, in the Designer enable the QBM | WorkingHours | IgnoreHoliday configuration parameter.
-
To exclude wekends from the working hours calculation, in the Designer enable the QBM | WorkingHours | IgnoreWeekend configuration parameter.
Related topics
One Identity Manager requires country information at different stages, for example, employee country and state assignments are accessed when email notifications are created or IT Shop workflows are being determined.
Language, time zones, public holidays and working hours are mapped as well as countries and states. The basis data is loaded into the database during schema installation.
Detailed information about this topic
