Changing Existing VO Automation to the DOM Extension
This functionality is supported only if you are using the Classic Agent.
Perform the following steps to port your current VO automation to the DOM extension:
Make sure the DOM extension is on.
Record a new window declaration for the particular objects with which you are having difficulties.
Look for any differences in the identifier names and object hierarchy. Make changes in the include file and scripts where appropriate.
If you decide to use the DOM exclusively, use one of these two approaches after you turn on the DOM extension:
Approach #1
Run your scripts and look for a
"Window '[class] Tagname' was not found" error message. Look for any differences in the identifier names and object hierarchy. Repeat this until all errors are resolved.
Approach #2
Re-record all of your declarations. Look for any differences in the identifier names and object hierarchy. Make changes in the include file and scripts where appropriate. This approach could potentially be more work than is necessary. Exactly how much work depends on how you have structured your automation.