Because your users can be distributed globally, it is very important to understand how can you configure and manage the time zones used in Bizagi. This section explains how you can configure this.
Within a project Bizagi lets configure a timezone at different levels:
The following is the hierarchy that Bizagi uses to determine a user's Timezone.
•Individual: Individual users can have a timezone defined. If an individual's timezone is set, then Bizagi will use that one. Else, Bizagi will evaluate the following condition. If a user HAS a timezone defined, and it is different form the project's one, then Bizagi will DISPLAY ALL dates for this user matching his/her timezone. But all dates will be stored in the project's time zone
•Location: Each user may belong to one Location. A Location may o may not have a Timezone defined. If the user belongs to a Location and it has a Timezone defined, Bizagi will use it. Else, Bizagi will evaluate the following condition.
•Organization: Each user belongs to one or more Organization(s). Organizations may have a Timezone set. Bizagi will take the first organization created that has a Timezone set, and uses the zone set on that one. if the Organizations have no timezone set, then Bizagi users the project's timezone.
•If a user travels, changing timezone, Bizagi will still consider the timezone defined in his/her preferences. It will only change if the Preferences are updated. The update will affect every single date the users sees.
•Users should know that Bizagi converts the dates to match their individual timezone to avoid problems when entering dates.
We recommend the following timezone setup:
Project Server configuration
Server configuration is setup in the development environment (Bizagi Studio). You can review this configuration in the Business Options, within the Localization menu. For the server configuration we recommend to leave the default option. See business configuration.
Changing the Server Time zone defines the time zone considered for the date times stored in the database. For example, the server where you have your Work Portal has the time set at 2 pm. Bizagi does not consider the time zone of the physical server (the one defined in the operating system). Bizagi only considers the time, which is the time used to stored date-time attributes.
Then you define the Bizagi Server Time Zone, in the business configuration, to be GMT +1. That means that all the date-time attributes are considered to be at 2 pm GMT +1.
If a user has a time zone set at GMT -5, then Bizagi considers the difference between the Bizagi project timezone (GMT +1) and the user timezone (GMT-5). Ass seen by the user in the Work Portal, there is a 6-hour difference.
Organization timezone configuration
Bizagi allows multiple organizations in your project. For each organization, you can define a specific time zone. Organization configuration is set up in the development environment (Bizagi Studio). You can change this configuration in the Organization module, right-clicking the organization. Then you can define the time zone. See creating an organization.
Location timezone configuration
For each organization, you can define locations. For example, you can define the branches of your company globally distributed. You can also define the timezone of each, so users who belong to the location can consider that timezone. See creating locations.
User timezone configuration
Finally, if a user does not need to use the location's or the organization's timezone, you can define the timezone individually for each user. This configuration for each user is set up in the Work Portal of your target environment.