Accepted Solutions
EDIT: I now see what the problem is.
If you have a document parameter, the only way to set it, is with the document selector, which, by default lists every document in your document repository.
There's two problems with it:
1. The UI does not show the full path to the document, thus, the language folder is unclear to the user
2. If a file exists in multiple language folders with the same name, it's only shown once, and the system default language is the "winner" - though, see #1 above, the UI doesn't make this clear
Example:
My en_US and en_GB folders have two files: one uniquely named file, and one generically named file
Now, when I try to set my app param, I see the following screen, where the unique names are shown, but the common name is collapsed into a single entry, hiding it's language parent folder. Though, as your and my testing has proven, the en_US system default language wins. I don't know if it's as simple as that, or if there's some alphabetical sorting going on or what, but it's broken nonetheless, and not a good UX.
If you want to adjust the language in the script to match the trigger, here's what you can do.
Variables
Language contact_language = L[] Document target_document = DOC[]
*Where target_document is an app parameter and set on the web page
Script Steps
/* Read the trigger language setting */ contact_language = Get Contact Info (--Triggering Contact--) /* Override the document language */ Set target_document = target_document @ contact_language
EDIT: I now see what the problem is.
If you have a document parameter, the only way to set it, is with the document selector, which, by default lists every document in your document repository.
There's two problems with it:
1. The UI does not show the full path to the document, thus, the language folder is unclear to the user
2. If a file exists in multiple language folders with the same name, it's only shown once, and the system default language is the "winner" - though, see #1 above, the UI doesn't make this clear
Example:
My en_US and en_GB folders have two files: one uniquely named file, and one generically named file
Now, when I try to set my app param, I see the following screen, where the unique names are shown, but the common name is collapsed into a single entry, hiding it's language parent folder. Though, as your and my testing has proven, the en_US system default language wins. I don't know if it's as simple as that, or if there's some alphabetical sorting going on or what, but it's broken nonetheless, and not a good UX.
If you want to adjust the language in the script to match the trigger, here's what you can do.
Variables
Language contact_language = L[] Document target_document = DOC[]
*Where target_document is an app parameter and set on the web page
Script Steps
/* Read the trigger language setting */ contact_language = Get Contact Info (--Triggering Contact--) /* Override the document language */ Set target_document = target_document @ contact_language
Here's an alternative response:
When using languages in UCCX, there is a system default at the root. You can find this setting for you system in:
System --> Language Information
Shows the default language set for your system:
If you do not specify a change in language from the default, for any script you write, the 'default' directory for Documents and Prompts is the starting search point.
If the script does not find the document or prompt referenced in your script, it will then search the directories set by the system default language (Named). Or, subsequently, for an alternate language if changed for the Contact in the script.
If you are writing a script and you would prefer the application not use the system default language, then you can change the default language for the specific application at the TRIGGER in the application:
1. Click the link for the Trigger in the Application
2. In the pop-up window, click the drop-down arrow
3. Select a new alternate default language for the Application
4. Save
This will change the default language for contacts calling your application. Alternatively, you can set multiple Triggers (with unique extension) for a given application, and set a default language for that specific trigger. You could then reference different languages by dialed number/trigger.
If you are not writing an application script that needs to change between languages (multi language change from [system default] [en_US] English to [es_US] US Spanish, for example) within the script, then this is the simplest way to change language from the system default. The Prompt names should match, in their respective named language directories, for each language referenced...
The system will still look for documents and prompts in the default directory first, but if none is found, it will search the set language--be it system default or application/trigger defined.
Hope this helps.
-Sean
