A window declaration specifies a cross-platform, logical name for a GUI object, called the identifier, and maps the identifier to the actual name of the object, which is called the tag or locator. Because your test cases use logical names, if the actual name of the object changes on the current GUI, on another GUI, or in a localized version of the application, you only need to change the tag in the window declarations. You do not need to change any of your scripts.
You can add variables, functions, methods, and properties to the basic window declarations recorded by Silk Test Classic. For example, you can add variables to a dialog box declaration that specify what the tab sequence is, what the initial values are, and so on. You access the values of variables at runtime as you would a field in a record.
After you record window declarations for the GUI objects in your application and insert them into a declarations file, called an include file (*.inc), Silk Test Classic references the declarations in the include file to identify the objects named in your test scripts. You tell Silk Test Classic which include files to reference through the Use Files field in the Runtime Options dialog box.