CDE Studio Linux Link Edition
Contents
Overview. 2
Requirements/Special
Notes. 4
Registering
CDE Studio. 4
Menu
Commands. 4
File. 4
Edit 5
View. 6
Options. 7
Favorites. 8
Windows. 8
Help. 8
Toolbar 9
Right
Click Menu. 10
Jump
to this State. 10
Play
Prompt File. 10
Edit
Prompt File. 10
View
raw PROMPT.INI file. 11
Insert
Prompt File. 11
Check
Prompts. 11
Search
Prompt Text 11
Toggle
Bookmark. 11
Add
To Do. 11
Search
across files. 11
Insert
Code Template. 11
Copy. 12
Cut 12
Paste. 12
Exploring
a Conversation. 12
List
View. 12
Tree
View. 13
The
To-Do Interface. 14
Using
To-Dos. 15
Adding
New To-Do Items. 16
Editing
To-Dos. 17
Deleting
To-Dos. 17
Managing
And Creating Prompts. 17
Playing
an existing prompt 17
Editing
an existing prompt 18
Inserting
a prompt 19
Creating
a new prompt 20
Compiling
Conversations. 20
The
Compilation Process. 21
Errors. 21
Warnings. 22
Multiple
Language Conversations. 23
Changing
default language. 23
Adding
a new language to an existing conversation. 24
Using
Code Templates. 25
Searching
Across Files. 25
File
Change History Feature. 27
File
Archive Features. 28
Prompt
Check Feature. 30
Obtaining
Updates. 31
Revision
History. 31
CDE Studio Linux Link is a rapid application development
tool for scripted conversations in Unity Connection 2.0(1) and later. It includes typical editor functions as well
as language specific highlighting, script compiler capabilities, conversation
exploration as well as prompt recording and management features that speed the
development of CDE based conversations.

While CDE Studio can
be used to edit any text based file such as JavaScript files, it’s
designed from the ground up as a tool for engineers that need to create, edit,
debug and explore Cisco Unity scripted conversation code. To find out more about the CDE scripted
conversation engine, read the “CDE Script Users Guide” document
which you’ll find under the help menu in CDE Studio. To find out more about the basic text
editing features, review the Menu Commands, Toolbar and Right Click Menu
sections that follow.
CDE Studio will show
a “conversation” as a combination of a single .CDE (conversation
script) and .PS (phrase server) file as a pair. The .CDE file is on the first tab in the
editing section on the right hand side of the form. The phrase server is always the 2nd
tab. A single conversation in Unity
can have numerous languages associated with it, each one as a separate phrase
server file. To keep the interface
manageable, only one phrase server file is shown. To show a different language phrase
server you can use the View | Phrase Languages menu option. See the Multiple Language Conversations
section below for more details on creating, editing and viewing multiple
language phrase server in CDE Studio.
When a conversation
is loaded through the File menu, CDE studio will automatically try to load a
corresponding phrase server file and compile the conversation. If the conversation compiles properly
(i.e. there are no errors in the script code) you will see the conversation
navigation tabs on the left hand side of the form. See the Compiling Conversations section below for
more details on the conversation compilation and error/warning handling
features in CDE Studio. To find out
how to use the navigation tabs, see the Exploring
a Conversation section below.
CDE Studio also
comes with a full compliment of prompt playback, creation and editing tools
built into it. Review the Managing And Creating
Prompts section in this document for details on how to use those features.
This application runs on Windows and connects to a Linux
server running Unity Connection 2.0(0.205) or later. It’s perfectly acceptable for this
to all be one server with Linux running on VMWare.
CDE Studio installs the merge files from Microsoft to
include MSXML 4 and SAPI 5.1 support on the box.
To connect to a remote Connection server properly, CDE
Studio LL needs root access. There
is no exception to this.
Registering CDE Studio
This version of CDE Studio does not need to be registered
– access to the Connection server is highly restricted in the field and
CDE Studio will only run when SSH is active and port 22 is open – which
is not the case for production server installs.
NOTE: All custom options selected in the menu
commands and all editor options enabled are saved when you exit CDE Studio and
will be reapplied the next time you start the application. You can move all these settings to a new
server if you like – see the “Export registry settings” menu
option in the Options section below for more details on
how to do that.
- Open
File. This launches the
open file dialog. It will open
to the directory where the current file being displayed is stored, if any
file is currently loaded. If
no file is loaded, the \commserver\localize\scripts\
directory will be shown. By
default it looks for files with extension that match .CDE, .CDX, .CDH,
.CS, .PS and .PSX, however you can select “all files” in the
file type drop down to see everything. Remember, CDE Studio is designed to
have you open a script file (.CDE) and will open the corresponding phrase
server file for you automatically.
- Save. Saves the currently visible file
– so if you have the .PS file showing, it will save that. NOTE: The save button on the
toolbar will only be active if the currently visible file has been
modified and has pending changes to save.
- Save
As. Allows you to save the
currently visible file with a new file name or path location.
- Save
All. This option will save
both the .CDE and .PS files if they are modified and have pending changes
to be saved.
- Check
script syntax. This option
compiles the current conversation and reports and warnings or errors that
were encountered. See the Compiling Conversations section below
for more details on this process.
- Compile
ABNF files to GRXML. This
option compiles all open ABNF files into their corresponding GRXML format
using the compiler provided by Nuance. The GRXML and ABNF files are
assumed to have the same name (other than the extension) with the
exception of the Common VUI ABNF file which is treated special.
- View
archives for current file.
Selecting this option will bring up a dialog for
reviewing/comparing/restoring archived versions of the currently loaded
file. You can learn more about
this File Archive Features
section.
- View file change history. Selecting this option will bring up
the file change history dialog which lets you see what files have been changed
and allow you to easily select some or all of them to copy locally for
source control purposes. For
more see the File Change History Feature
section.
- Show
raw XML for script. Selecting this option will show the XML
representation of the currently loaded .CDE file. This option only works if the
currently loaded conversation is successfully compiling.
- Export Tree View to File. This takes the current tree layout
on the “Tree” tab and exports it to a text file – all
the nodes expanded will be shown expanded, and all those closed will show
closed.
- Print. This will bring up the standard
Windows print dialog and allow you to print the currently visible
document. If you have the .CDE
file open, that’s what will print. If you have the .PS file visible
then that’s what will print.
- Recent. This shows the recently opened
files you’ve accessed with CDE Studio. Up to 10 files are included in the history,
sorted from most recently accessed at the top to least recently at the
bottom.
- Exit. Closes the CDE Studio
application. If there are
pending changes to any open file, you will be given an opportunity to save
them or abort the exit command.
- Cut. Cuts the currently selected text
and puts it on the Windows clipboard .
- Copy. Copies the currently selected text
and puts it on the Windows clipboard.
- Paste. Takes the text on the Windows
clipboard and inserts it into the open file where the cursor is located.
- Find. Launches the Find dialog seen here:

This is a pretty standard dialog you’ve seen
in other applications, however the “Mark
all” feature may be new. This
option will bookmark every line that has an instance of the desired text in
it. You can then use the bookmark
options (see below) to jump between the marked lines. This can be handy for quickly finding
multiple instances of a string in a file.