Open topic with navigation
The following attributes of the Identification Property element in the test object configuration file specify information that can be modified in UFT (using the Object Identification dialog box): AssistivePropertyValue, ForAssistive, ForBaseSmartID, ForDescription, ForOptionalSmartID, and OptionalSmartIDPropertyValue. These attributes determine the lists of identification properties used for different purposes in UFT. For more information, see the UFT Test Object Schema Help.
Therefore, by default, UFT reads the values of these attributes from the XML file only once, to prevent overwriting any changes a user makes using the Object Identification dialog box. In this way, UFT provides persistence for the user defined property lists.
If the user clicks the Reset Test Object button in the Object Identification dialog box, the attributes' values are reloaded from the XML.
If the XML changed since the last time it was loaded (based on the file's modification date in the system), UFT reads the attributes from the XML. UFT adds identification properties to the relevant lists (and adjusts their order if necessary) according to the values of these attributes, but does not remove any existing identification properties from the lists.
To instruct UFT to completely refresh the identification property lists according to the attributes defined in the XML each time UFT is opened, set the DevelopmentMode attribute of the TypeInformation element in this test object configuration file to
If you modify attributes of Identification Property elements in the test object configuration file, keep the DevelopmentMode attribute of the TypeInformation element set to true during the design stages of the custom toolkit support. This ensures that UFT uses all of the changes you make to the file.
Before you deploy the toolkit support set for regular use, be sure to remove the DevelopmentMode attribute of the TypeInformation element (or set it to false). Otherwise, every time UFT opens it will refresh the property lists based on the definitions in the test object configuration file. If UFT users change the property lists using the Object Identification dialog box, their changes will be lost when they reopen UFT.
Though UFT does not remove existing properties from the property lists when reading a modified test object configuration file (unless the DevelopmentMode attribute is set to true), it does add properties and adjust the order of the lists based on the definitions in the file. If UFT users removed properties from the lists or modified their order using the Object Identification dialog box, those changes will be lost when a modified file is loaded.
If you provide the custom toolkit support set to a third party, and you deliver an upgrade that includes a modified test object configuration file, consider informing the UFT users about such potential changes to their identification property lists.
When defining a new control, you should define the ForDescription attribute as part of the test object schema. Leaving out this attribute causes your object not to be recognized during test runs (although it can be recorded).