Multiple-Language Support

Oracle Fusion Cloud Risk Management can store much of the text users enter in multiple languages.

In general, you can save multiple values, one for each language, for any text attribute that could contain words. Examples include text you might enter in a Name or Description field. Each user would then see values in the language he or she chooses to work in.

There are exceptions. Some attributes store or return only a single value no matter what language a user chooses to work in. They include:

System-generated values, such as IDs.
Values that aren't text, such as numbers.
Values, like codes, that contain letters that don't form words.
Lists of values.
Attachments (URLs or file names).
Names of filters created for transaction models, and the values they search for. If a filter searches for values of an attribute that can be translated, it returns only the value in the "source language." This is the language in which a user worked while creating the model that contains the filter. A Source Language column on the models page identifies the source language for each model.

Here's how to work with languages:

Each user can choose a language, and can change that language at any time. One way to do this is to select a language while signing in to Oracle Fusion Cloud. Another way is to navigate to Settings and Actions > Set Preferences > Language. Then select either a default language or a language to be used in the current session.
A user creates a record. As he enters its text-attribute values, he uses the language he's chosen to work in. Initially, all users with access to the record see the values in the language the creator chose.
Another user, working in another language, edits the record to translate its text-attribute values. Now, users working in this second language see the translated values, but users working in any other language see the values in the original language.
Users working in other languages open the original record and translate its text-attribute values into their languages. Once again, a user working in any of these languages sees the values in that language. But users working in languages for which no translations have been created see values in the original language.

Here's an example:

Fred uses English. As he creates a new risk, he enters "This is my risk's name" in the Name field.
Henri uses French. He changes the name of the risk to "C'est le nom de mon risque." Other French users see the French name, but users of all other languages see the English name.
Fred, still working in English, sees "This is my risk's name." But he changes his language to French, and then sees "C'est le nom de mon risque."
Maria uses Spanish. She opens the risk and sees "This is my risk's name." She changes that value to "Este es el nombre de mi riesgo." All Spanish users see that. All French users continue to see "C'est le nom de mon risque." Users in all other languages still see "This is my risk's name."

Here's a recommendation: If you're responsible for creating a record, prepare or review translations it will need before you make it visible to reviewers, approvers, managers, directors, auditors, and others. To do that, temporarily set your language to each of the translation languages. If you're multilingual you may do this on your own, or you may collaborate with colleagues who are fluent in your translation languages.