Localization enables in Kyvos Reporting allows organizations to meet the language requirements of a particular country or region for users spread users' language and regional formatting needs across geographical locations. By using Through its localization features of Intellicus, you can get information like users can access the portal and view reports in their preferred language, along with localized date, time, and currency in your localized formats; date and time as per your time zones. You can access Intellicus portal and also get report outputs formats.
Key Aspects of Localization
Locale-based Formats: Localization ensures that information such as date, time, and currency is presented appropriately for the selected region.
Language Support: Users can access the portal and reports in a language supported by
...
the selected locale.
Time Zone Configurations: Time zones can be configured for the report server, database, and users, ensuring consistent and accurate time-dependent activities.
Scope of
...
Localization
Kyvos Reporting's localization capabilities include the following tasks:
Specify Specifying Locale to select : Select date and time formats Select Time for reports and portal activities.
Configuring Time Zones: Set time zones for the report server, database, and user
Localize Portal
Localize Report data
Locale selection
...
individual users.
Localizing the Portal: Customize the portal's interface and static content to appear in the selected language.
Localizing Report Data: Display report labels, data values, and outputs in the desired language.
Locale Selection
Locales determine the specific language and geographic region . In Intellicus, locales affect portal settings, impacting:
Portal language (if configured)
...
Figure 1: Localization options on User Preferences page
...
Locale can be set from multiple places in Intellicus. It will be applied in the following order:
...
Sorting of data
Formats for date, time, numbers, and currency
How Locale is Applied:
...
User Preferences
Users can specify their locale under Navigate > Personalization > Preferences.Organization Preferences:
If Default Locale is not set in personal user preferences, then, Default Locale set the default locale for the organization (to which user belongs) configured under Navigate > Administration > Manage Users > Organization) will be applied.Report Server Properties: If Default Locale is not set for the organization, then, locale set on
If no organization-level locale is set, the locale configured under Navigate > Administration > Configure > Server page will be applied.Machine Locale: If Default Locale is set as “Default” under the Server Properties, then locale set on the machine where report server is running will be applied.
Time zones for report server, database and user
Value of ‘Time Zone’ affects all the time dependent activities like report output (data of date type), scheduling and life of repository objects (for example, published reports).
There are three types of time zones:
If the report server locale is set to "Default," the machine's locale where the report server is hosted will be used.
Time Zone Configurations
Time zones influence time-dependent activities such as report output, scheduling, and the lifecycle of repository objects.
Types of Time Zones:
Database Time Zone
Configured under Navigate > Administration > Configure > Databases
...
.
Server
...
Time Zone
Configured under Navigate > Administration > Configure > Server
...
.
User
...
Time Zone
Can be set at multiple
...
levels, applied in the following order:
User Preferences
...
Set under Navigate > Personalization > Preferences
...
.
Organization Preferences
...
Default
...
time zone for the organization
...
, configured under Navigate > Administration > Manage Users > Organization
...
.
Report Server Properties
...
If
...
not set
...
at the organization level,
...
the time zone
...
configured under Navigate > Administration > Configure > Server
...
will be applied.
Machine Locale
...
Portal
Portal components may not just be set to appear in any of the set language, but users can provide inputs on some of the portal pages in respective language. All the static portal text and validation messages appear in respective language.
Figure 2: Portal running in Japanese
...
Users would be able to provide following details in respective language on portal:
Name of Report
Name of Category (Folder)
Name of the Query Object
Field caption (being set at the time of creating a query object)
Dashboard name
Dashboard Widget name
Job name being setup from report list page (Quick job)
Published Report name
Figure 3: Report and Folder name across portal appears in the language they were specified in
...
Report data
Data values as well as labels placed on a report can be made to appear in the selected language. You can choose to receive output of selected reports in selected language and all the reports deployed in a selected category.
During ad hoc-report’s design, user Query Object (Data source) list can have localized entries. Field captions as well as values can also be provided in local language.
...
If the server time zone is set to "Default," the machine's time zone will be used.
Portal Localization
The portal's static text, validation messages, and input fields can be configured to appear in the selected language. Users can also input the following details in their preferred language:
Report names
Category (folder) names
Query object names
Field captions
Dashboard names and widget titles
Job names (for quick jobs)
Published report names
Example:
Static and dynamic content such as report and folder names will appear in the specified language.
Report Data Localization
Localization extends to report labels and data values, allowing users to:
View report data and labels in the selected language.
Receive report outputs in the desired language for specific reports or categories.
During ad-hoc report design, localized entries can appear in the query object list, with field captions and values in the selected language.