| Choosing the most appropriate kind of element customization |
| Categories: Audium OpenSDK |
| Article ID: | 8 |
| Last updated: | February 18, 2007 |
| User Opinions |
|
No users have voted.
|
|
Thank you for rating this answer.
|
SUMMARY
Suggestions for what types of customization (i.e. types of custom code) may be appropriate choices when existing functionality does not meet your project's requirements.
SYMPTOMS
An application is being created where new functionality is needed. While Audium provides a comprehensive set of built-in elements with Audium Studio, in a complex application there is usually at least some custom code that will need to be written.
RESOLUTION
First, fully describe the new functionality that is required. Then, see where it falls in the categories below, and consider using the listed type of customization (the types are loosely ordered by complexity):
|
Functionality |
Use |
| A simple decision based on string or number comparisons |
An XML Decision |
| An all-in-one solution that does some work (e.g. a back-end lookup, calculation, etc.), and then modifies an element's settings and/or audio based on the result of that work |
A Dynamic Configuration |
| An element that performs a very specific task or decision that only one application requires |
A Standard Action/Decision Element |
| An element that performs a very specific interaction with the caller that only one application requires |
A Standard Voice Element |
| An element that performs a common task or decision that is not possible with the pre-built elements, and that multiple applications will use (or that one application will use in several different ways) |
A Custom Configurable Action/Decision Element |
| An element that performs a common interaction with the caller that is not possible with the pre-built elements, and that multiple applications will use (or that one application will use in several different ways) |
A Custom Configurable Voice Element |
|
| Visitor Comments |
|
No visitor comments posted. Post a comment
|
| Attachments |
|
No attachments were found.
|