SAP Applications

HierarchyHeaderWidth and ColumnOrder Properties of the SAPTree Class are write only

Other than the automation documentation indicates, the HierarchyHeaderWidth and ColumnOrder properties of the SAPTree class are write only and cannot be read.

Ensure that your scripts use write rather than read with these properties.

GetColumnIndexFromName() of the SapTree Class May Fail with an "unspecified error"

GetColumnIndexFromName() of the SapTree class may fail with an "unspecified error". This is a known issue in SAP automation.

Check the SAP web site to see if the issue has been resolved.

Calling the Select() method of the SAPTree Class on a Context menu item may fail

Calling the Select() method of the SAPTree class on a Context menu item may fail.

Call SelectContextMenuItem on the parent control instead. This problem is a known issue in the SAP automation.

The position property for a horizontal scrollbar always returns 1

The position property for a horizontal scrollbar always returns 1. This is a known issue in SAP automation.

Check the SAP web site to see if the issue has been resolved.

The SAPNetPlan class is not supported

This issue will be resolved in a future release.

Replay error occurs when executing an SAP script

In certain cases, if you record an SAP test and then replay it, the following error might occur: The data necessary to complete this operation is not yet available. This means that Silk Test Workbench is executing the recorded actions too fast.

To solve this issue, you can add sleeps to your test script or you can increase the post replay delay to increase the time that Silk Test Workbench waits after invoking a function or setting a property. For additional information about this option, see Agent Options. You could also change the script to use SAP automation to replay the problematic action instead of using the xBrowser technology domain. For example, you could change the action DomLink.Select to SapHTMLViewer.SapEvent.

The method getCurrentRow returns a wrong value with SAPGUI client 7.30

If you use SAPGUI client 7.30 and you call the method getCurrentRow, the method might falsely return -1 instead of the row number.

The method resizeWorkingPane is not working correctly with SAPGUI client 7.30

If you use SAPGUI client 7.30 and you call the method resizeWorkingPaneEx, the method will not resize the workingPane and calling getSapWindow().getWidth() will return a wrong value for the window width.

Cannot start recording on a virtual machine when Silk Test Workbench is started from eCATT

When you have created an eCATT script from SAPGui, recording actions on a virtual machine by pressing the Record button, while the VB .NET script, visual test, or keyword-driven test is open in the Silk Test Workbench editor, does not work. Recording actions on a physical machine works.

When importing assets to a Silk Test Workbench database from eCATT, no error is displayed when using an eCATT BLOB that was created with a newer version of Silk Test Workbench than the XML of the exported assets

When using a importing assets from eCATT to a Silk Test Workbench database, the importing process fails silently if the version of Silk Test Workbench is lower than the version of the XML, which includes the assets, in the eCATT BLOB.

If the import fails, the next time that you try to edit the blob, the following message displays:

Would you like to save the current BLOB before returning to eCATT?

In this case, do not save the BLOB, because it is empty. Instead, click No to return to eCATT.

Tip: If you are using multiple instances of Silk Test Workbench with eCATT, Micro Focus recommends updating all instances to the same Silk Test Workbench version.