Languages and Localization - Revision history

TeeHiet: TK-63420

2026-06-17T14:01:43Z

TK-63420

← Older revision		Revision as of 14:01, 17 June 2026
Line 45:		Line 45:

	== Content Language ==		== Content Language ==
	Translations for process mining data (e.g. case and event attribute names, event type names, case and event attribute values) can be provided via the ContentTranslations value in the [[PA_Configuration_database_table#Localization_Settings\|configuration table]]. When a valid ContentTranslations value is provided, the translations can be taken into use by selecting the "Content language" in the [[~~User_Settings~~\|User ~~Settings~~ dialog]].		Translations for process mining data (e.g. case and event attribute names, event type names, case and event attribute values) can be provided via the ContentTranslations value in the [[PA_Configuration_database_table#Localization_Settings\|configuration table]]. When a valid ContentTranslations value is provided, the translations can be taken into use by selecting the "Content language" in the [[User_Profile\|User Profile dialog]].
	<br>		<br>
	Some things to note:		Some things to note:

TeeHiet: TK-63311

2026-05-28T12:30:11Z

TK-63311

← Older revision		Revision as of 12:30, 28 May 2026
Line 29:		Line 29:
	== Language Support Details ==		== Language Support Details ==
	Most texts in the UI are translated, but there are the following exceptions:		Most texts in the UI are translated, but there are the following exceptions:
	* Process mining data imported to QPR ProcessAnalyzer (e.g. case and event attribute names, event type names, case and event attribute values) needs to be separately translated. See [[Languages and Localization#~~Content_Translations~~\|~~Content_Translations~~]] section below.		* Process mining data imported to QPR ProcessAnalyzer (e.g. case and event attribute names, event type names, case and event attribute values) needs to be separately translated. See [[Languages and Localization#Content_Language\|Content Language]] section below.
	* Some tooltips that contain longer instructions		* Some tooltips that contain longer instructions
	* Some special error messages related to the expression language errors		* Some special error messages related to the expression language errors

TeeHiet: TK-63311

2026-05-28T12:29:42Z

TK-63311

← Older revision		Revision as of 12:29, 28 May 2026
Line 44:		Line 44:
	New users have these defaults until the user changes to her/his own settings. In case the administrator needs to change the language for many existing users, the change needs to be done directly to the ''PA_USER_ATTRIBUTE'' table in the database.		New users have these defaults until the user changes to her/his own settings. In case the administrator needs to change the language for many existing users, the change needs to be done directly to the ''PA_USER_ATTRIBUTE'' table in the database.

	== Content ~~Translations~~ ==		== Content Language ==
	Translations for process mining data (e.g. case and event attribute names, event type names, case and event attribute values) can be provided via the ContentTranslations value in the [[PA_Configuration_database_table#Localization_Settings\|configuration table]]. When a valid ContentTranslations value is provided, the translations can be taken into use by selecting the "Content language" in the [[User_Settings\|User Settings dialog]].		Translations for process mining data (e.g. case and event attribute names, event type names, case and event attribute values) can be provided via the ContentTranslations value in the [[PA_Configuration_database_table#Localization_Settings\|configuration table]]. When a valid ContentTranslations value is provided, the translations can be taken into use by selecting the "Content language" in the [[User_Settings\|User Settings dialog]].
			<br>
			Some things to note:
			* Search dialogs work only with the original text, not the translated values.
			* The Workspace user interface isn't translated from the content viewpoint, except for datatable content preview, which is translated.

	__NOTOC__		__NOTOC__
	[[Category: QPR ProcessAnalyzer]]		[[Category: QPR ProcessAnalyzer]]

TeeHiet: TK-63311

2026-05-28T12:07:26Z

TK-63311

← Older revision		Revision as of 12:07, 28 May 2026
Line 29:		Line 29:
	== Language Support Details ==		== Language Support Details ==
	Most texts in the UI are translated, but there are the following exceptions:		Most texts in the UI are translated, but there are the following exceptions:
	* Process mining data imported to QPR ProcessAnalyzer (e.g. case and event attribute names, event type names, case and event attribute values)		* Process mining data imported to QPR ProcessAnalyzer (e.g. case and event attribute names, event type names, case and event attribute values) needs to be separately translated. See [[Languages and Localization#Content_Translations\|Content_Translations]] section below.
	* Some tooltips that contain longer instructions		* Some tooltips that contain longer instructions
	* Some special error messages related to the expression language errors		* Some special error messages related to the expression language errors
Line 43:		Line 43:

	New users have these defaults until the user changes to her/his own settings. In case the administrator needs to change the language for many existing users, the change needs to be done directly to the ''PA_USER_ATTRIBUTE'' table in the database.		New users have these defaults until the user changes to her/his own settings. In case the administrator needs to change the language for many existing users, the change needs to be done directly to the ''PA_USER_ATTRIBUTE'' table in the database.

			== Content Translations ==
			Translations for process mining data (e.g. case and event attribute names, event type names, case and event attribute values) can be provided via the ContentTranslations value in the [[PA_Configuration_database_table#Localization_Settings\|configuration table]]. When a valid ContentTranslations value is provided, the translations can be taken into use by selecting the "Content language" in the [[User_Settings\|User Settings dialog]].

	__NOTOC__		__NOTOC__
	[[Category: QPR ProcessAnalyzer]]		[[Category: QPR ProcessAnalyzer]]

TeeHiet: TK-59365

2025-06-17T05:18:16Z

TK-59365

← Older revision		Revision as of 05:18, 17 June 2025
Line 8:		Line 8:
	* Polish		* Polish
	* Portuguese		* Portuguese
			* Ukrainian

	== Changing Language ==		== Changing Language ==

Ollvihe: /* Date Format Settings */

2023-05-17T07:33:06Z

Date Format Settings

← Older revision		Revision as of 07:33, 17 May 2023
Line 20:		Line 20:
	== Date Format Settings ==		== Date Format Settings ==
	In addition to the language, the following date presentation related settings can be set for each user in the [[Navigation_Menu#User%20Settings\|User Settings dialog]]:		In addition to the language, the following date presentation related settings can be set for each user in the [[Navigation_Menu#User%20Settings\|User Settings dialog]]:
	* '''Date format''': Defines how date values ~~appears~~ are presented in the ~~Web UI~~. The format can be e.g. MM/dd/yyyy or d.M.yyyy. Following parts ~~that~~ can be used in the date format: '''d''' (day of month as one or two digits), '''dd''' (day of month as two digits), '''M''' (month as one or two digits), '''MM''' (month as two digits), '''yy''' (year as two digits) and '''yyyy''' (year as four digits).		* '''Date format''': Defines how date values are presented in the user interface. The format can be e.g. MM/dd/yyyy or d.M.yyyy. Following parts can be used in the date format: '''d''' (day of month as one or two digits), '''dd''' (day of month as two digits), '''M''' (month as one or two digits), '''MM''' (month as two digits), '''yy''' (year as two digits) and '''yyyy''' (year as four digits).
	* '''First day of week''': The first day of the week (~~that appears~~ in calendars to pick dates).		* '''First day of week''': The first day of the week (appearsing in calendars to pick dates).
	* '''Use 12-hour clock''': Whether the 24-hour or 12-hour clock is used to present hours.		* '''Use 12-hour clock''': Whether the 24-hour or 12-hour clock is used to present hours.

Ollvihe: /* Localization Settings for New Users */

2023-05-17T07:31:02Z

Localization Settings for New Users

← Older revision		Revision as of 07:31, 17 May 2023
Line 41:		Line 41:
	* DefaultUse12HourClock		* DefaultUse12HourClock

	New users have these defaults ~~in use~~ until user changes to her/his own settings. In case ~~there is desire for~~ the administrator to change the ~~settings~~ for ~~all or several~~ users, the change needs to be done directly to the ''PA_USER_ATTRIBUTE'' table in the database.		New users have these defaults until the user changes to her/his own settings. In case the administrator needs to change the language for many existing users, the change needs to be done directly to the ''PA_USER_ATTRIBUTE'' table in the database.

	__NOTOC__		__NOTOC__
	[[Category: QPR ProcessAnalyzer]]		[[Category: QPR ProcessAnalyzer]]

Ollvihe at 07:29, 17 May 2023

2023-05-17T07:29:10Z

← Older revision		Revision as of 07:29, 17 May 2023
Line 43:		Line 43:
	New users have these defaults in use until user changes to her/his own settings. In case there is desire for the administrator to change the settings for all or several users, the change needs to be done directly to the ''PA_USER_ATTRIBUTE'' table in the database.		New users have these defaults in use until user changes to her/his own settings. In case there is desire for the administrator to change the settings for all or several users, the change needs to be done directly to the ''PA_USER_ATTRIBUTE'' table in the database.

	~~__NOTOC~~		__NOTOC__
	[[Category: QPR ProcessAnalyzer]]		[[Category: QPR ProcessAnalyzer]]

Ollvihe at 07:28, 17 May 2023

2023-05-17T07:28:29Z

← Older revision		Revision as of 07:28, 17 May 2023
Line 34:		Line 34:
	The login page is shown with the system default language, when QPR ProcessAnalyzer is for the first time accessed with a certain device. Language is also stored to the browser's local storage, so the browser remembers the last used language and in the next time shows the login page in that language.		The login page is shown with the system default language, when QPR ProcessAnalyzer is for the first time accessed with a certain device. Language is also stored to the browser's local storage, so the browser remembers the last used language and in the next time shows the login page in that language.

	== ~~Default~~ Localization Settings ==		== Localization Settings for New Users ==
	For system administrators, there are system wide defaults for the localization settings that can be set in the [[PA_Configuration_database_table\|configuration table]]:		For system administrators, there are system wide defaults for the localization settings that can be set in the [[PA_Configuration_database_table\|configuration table]]:
	* DefaultUiLanguage		* DefaultUiLanguage
Line 43:		Line 43:
	New users have these defaults in use until user changes to her/his own settings. In case there is desire for the administrator to change the settings for all or several users, the change needs to be done directly to the ''PA_USER_ATTRIBUTE'' table in the database.		New users have these defaults in use until user changes to her/his own settings. In case there is desire for the administrator to change the settings for all or several users, the change needs to be done directly to the ''PA_USER_ATTRIBUTE'' table in the database.

			__NOTOC
	[[Category: QPR ProcessAnalyzer]]		[[Category: QPR ProcessAnalyzer]]

Ollvihe at 07:27, 17 May 2023

2023-05-17T07:27:53Z

@@ Line 25: / Line 25: @@
 Similar to the language, all these settings are remembered for the user.
 == Default Localization Settings ==
@@ Line 34: / Line 42: @@
 New users have these defaults in use until user changes to her/his own settings. In case there is desire for the administrator to change the settings for all or several users, the change needs to be done directly to the ''PA_USER_ATTRIBUTE'' table in the database.
 [[Category: QPR ProcessAnalyzer]]