Audium Knowledge Base

Knowledgebase Home | Contact Knowledgebase Home | Contact
Search the Knowledgebase Jump to ID Browse by Category
How to debug issues with custom extensions in Studio
Categories: Step-by-step debugging tips
Article ID: 284
Last updated: December 12, 2006
User Opinions
No users have voted.

How would you rate this answer?
Helpful
Not helpful
There are problems with adding or extending elements/components/GUI in Studio
There are problems with setting up source control system or another external resource
Custom element does not show up in Studio

Configuring source control system intergration, such as CVS or ClearCase, is very specific to each environment. Please refer to your internal IT department for the appropriate settings for your company.

Once the source control system is set up, you might want to refer to the following two articles describing interaction with the source control system:

Studio instantiates (loads into memory) all the Java classes for custom elements. If the Java class has errors, then the element will not be loaded and will not be displayed in the Elements pane. Java exceptions will be thrown and logged in the Audium Error Log view.

Note that local elements are loaded each time the application is opened in the CallFlow Editor and global elements are loaded upon Studio startup.

The following articles might help debugging issues related to problems with custom elements:

Visitor Comments
No visitor comments posted. Post a comment
Related Questions
No related questions were found.
Attachments
No attachments were found.

Copyright (c) 2005 Audium Corporation. All rights reserved.
Audium Home | Audium Support Center Home | Audium Customer Care Home