This functionality is supported only if you are using the Classic Agent.
To enable Silk Test Classic to recognize custom controls, you must record classes for these objects.
The process of recording a custom Java class involves querying the objects, retrieving information on methods and properties for these objects, and then translating this information into 4Test-style prototypes that you can use to write test scripts.
We recommend that you store your class definitions in a new include file, for example custobj.inc or in your test frame file. Do not store these definitions in javaex.inc, which is the predefined Java class definition file, because we will upgrade javaex.inc in future versions of our Java support. You will need to load new class include files in Silk Test Classic before testing your application or applet.
If you add, delete, or modify any native methods or parameters for a custom Java class, you need to either re-record the class or modify your class include file to reflect the changes.