Without seeing the actual error log file (VxmlServer/logs/GlobalErrorLogs) or the java code, it's hard to determine exactly what the error is. Please post both the java source code and the error log.
Most likely, it's either that you didn't restart VXMLServer after adding the class files into the VXMLServer/common.
Or the DecisionElement.class isn't written as a valid decision class.
Or that it's folder structure isn't valid (perhaps its missing the package directory structure).
Or doesn't match that used in the app.
1. The programming guide for CVP says that a Standard Decision must look like this. Then in Call Studio, you'd enter the class name: com.mypackage.MyClassName. And the folder com/mypackage/MyClassName.class would be copied either into VXMLServer/common/classes or into the Studio app into appname/deploy/java/application/classes
package com.mypackage;
public class MyClassName extends DecisionElementBase
{
@Override
public String doDecision(String arg0, DecisionElementData decisionApi) throws Exception {
// decisionApi is used to interface to VXMLServer
return "exitStateName"; //Note: return the name of an exit state as String
}
}
And then in Call Studio decision element, you'd enter the class: com.mypackage.MyClassName
And add all the exit state strings (case sensitive).
The actual java class file must maintain its directory structure (com/mypackage/MyClassName.class) and either be copied into VXMLServer/common/classes - and then restart VXMLServer. I suspect you didn't actually restart VXML Server so you didn't load those VXMLServer/common classes into memory.
Alternatively, remove your class file from VXMLServer/common and use my preferred method of copying the class file into the Studio Navigator pane, into the app, under AppName/deploy/java/application/classes so you end up with: AppName/deploy/java/application/classes/com/mypackage/MyClassName.class. Then when you Deploy from Studio and run the deployApp.bat or updateApp.bat - VXMLServer loads those classes into memory.
HTH
