This functionality is supported only if you are using the Classic Agent.
While using the Record Window Declarations dialog box, you will on occasion notice that the recorded class is CustomWin, indicating that Silk Test Classic does not recognize the class of the object. The object is interpreted as a custom object. Custom objects often look and act the same as their corresponding known, standard objects and they may correspond to built-in, known classes.
If the object is in fact a custom object, to be able to record and run test cases that interact with the custom object, see Mapping Custom Classes to Standard Classes.
However, if the object is not actually a custom object, but is instead a standard object that your application’s developers have renamed, you can record and run test cases merely by establishing a class map between the renamed class and the standard 4Test class. You can also filter out unneeded custom classes from the class hierarchy.
Class mapping only works for objects that are created with standard API calls but are given non-standard names.