Orchestrator supports internationalization level 1.
Non-ASCII Character Support in Orchestrator
Although Orchestrator is not localized, it can run on a non-English operating system and handle non-English text.
Non-ASCII Character Support in Orchestrator GUI
|
Support for Non-ASCII Characters
|
|---|
| | |
Input and Output Parameters
| |
|---|
|
Action
|
Yes
|
No
|
No
|
No
|
|
Folder
|
Yes
|
Yes
|
-
|
-
|
|
Configuration element
|
Yes
|
Yes
|
-
|
No
|
|
Package
|
Yes
|
Yes
|
-
|
-
|
|
Policy
|
Yes
|
Yes
|
-
|
-
|
|
Policy template
|
Yes
|
Yes
|
-
|
-
|
|
Resource element
|
Yes
|
Yes
|
-
|
-
|
|
Web view
|
Yes
|
Yes
|
-
|
No
|
|
Workflow
|
Yes
|
Yes
|
No
|
No
|
|
Workflow presentation display group and input step
|
Yes
|
Yes
|
-
|
-
|
Non-ASCII Character Support for Oracle Databases
To store characters in the correct format in an Oracle database, set the NLS_CHARACTER_SET parameter to AL32UTF8 before configuring the database connection and building the table structure for Orchestrator. This setting is crucial for an internationalized environment.