Not sure if you still need assistance with this... but since it has no responses, I'll post... To use a System Prompt (for example the SP[Welcome.wav]) you must first set your 'Contact Language.'  By default, that is set to "L[en_US]" on my system.  Not sure what yours is built as...  In order to hear a system prompt in Arabic played (or any other language for that matter), you must have the Arabic language pack installed (or any alternate language of preference...) on your system.  (I have three languages installed on my system for example:  L[en_US], L[en_AU], and L[es_MX]).  If this is already done, but Arabic is not the default language, you must then set the "Contact Language" in your script to Arabic (I'm guessing it would be L[ar_AE] --but there are many different dialects and countries for Arabic, so use the drop downs in the expression editor to find the correct setting on your system.   The main steps are as follows: 1.  Set Language variable 2.  Set contact with a language variable 3.  Set prompt with system prompt variable;  the system prompt changes with the assignment of the Contact Language setting. Sample:     Use the expression editor to help locate available languages on your system:   I recommend making the language assignments to pre-named variables.   This pretty much works for any multi-language configured UCCX system. Hope this helps. -Sean ... View more

You are so close.  If you are going to reference the 'subflow Script' named in a different or any other directory or sub directory, you need to treat it like a variable of type String.  Unless representing the path using other variables it would look something like this: ...everything inside the SCRIPT keyword brackets in parenthesis--  SCRIPT["..."]   Alternatively if you want to use named variables, format like this: This example uses named variables as type String that will need to be created in the variable pane below prior to use: Notice, the parenthesis are around the String data in the variable pane and not in the subflow SCRIPT keyword setting for the subflow palette item in the script.  Think, "Syntax of using Strings in subflow settings..."   Lastly, the SCRIPT reference (with sub-directories) can come from the directory itself if you use the editor button, in the subflow editor to drill down to the script you intend to use as your subflow:   Right-click to open the properties of the Subflow palette item and then open the expression editor:   Select Script tab for Script variables:   Select the Browse Scripts button on the Script properties tab/page:   Drill down to the subdirectory where your subflow script is saved:  Script Repository/default/Sample (in my example):   Select 'default' then the 'Open' button (sorry, missed circling this one in red like the ohers):   'Sample' subdirectory :  select your script name and click Paste:   Your SCRIPT properties will now be properly set for you application after you click the 'Okay' button:   Click the 'OK' button to assign this to your Subflow palette item:   Your subflow is now properly set for the subdirectory from which you selected. No quote marks necessary...  (reference second subflow in image below):   One last recommendation, be precise when working with variables of type String--well, any variable type really.  They are spelling and case sensitive. Typos can be a real bugger if you don't type them in perfectly--best practice and recommendation: use the drop-down options to select named variables from lists / in the expression editor after they've been created.   Hope this helps. -Sean ... View more